bconsole exits without error messages (bareos 18.2.5)

22 views
Skip to first unread message

Kai Zimmer

unread,
Jan 7, 2020, 4:25:40 AM1/7/20
to bareos-users
Hi,

after upgrading bareos from 15.2.2.-37.1 to 18.2.5-147.2 (including
postgres database) i'm doing some tests:

- restore of (old) backup data works successfully from bconsole

- doing new backups works successfully from bconsole

- when restoring new backups  with bconsole, bconsole exits without
error message, after

"Building directory tree for JobId(s) 10,51,65,74 ..."

I tried 'setdebug level=200 trace=1 all' in bconsole, according to the
trace file it looks like bareos found all relevant backup files in the
index (took some hours), but also there i don't find any hint why
bconsole exits:

...

kira-dir (150): dird/ua_tree.cc:229-0 Path=/home/ FI=258333 JobId=74
kira-dir (150): dird/ua_tree.cc:248-0 node=0x7f533d494050 JobId=74
FileIndex=258333 Delta=0 node.delta=-1 LinkFI=0, fhinfo=0, fhnode=0
kira-dir (200): dird/scheduler.cc:331-0 enter find_runs()
kira-dir (200): dird/scheduler.cc:347-0 now = 5e14425c: h=9 m=0 md=6
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:367-0 nh = 5e14506c: h=10 m=0 md=6
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:450-0 Leave find_runs()
kira-dir (200): dird/scheduler.cc:331-0 enter find_runs()
kira-dir (200): dird/scheduler.cc:347-0 now = 5e144298: h=9 m=0 md=6
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:367-0 nh = 5e1450a8: h=10 m=0 md=6
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:450-0 Leave find_runs()
kira-dir (200): dird/stats.cc:149-0 statistics_thread: Doing work at
1578386073
kira-dir (200): dird/stats.cc:153-0 statistics_thread: do nothing as no
jobs are running
Pool   Maxsize  Maxused  Inuse
NoPool      256        2      0
NAME       9910       23     19
FNAME      3328      170    169
MSG       19818       82     80
EMSG       2299       22     18
BareosSocket      9910       10      9
RECORD      128        0      0

kira-dir (100): cats/sql_query.cc:140-0 called: bool
BareosDb::SqlQuery(const char*, int (*)(void*, int, char**), void*) with
query SELECT SUM(PurgedFiles) FROM Job WHERE JobId IN (10,51,65,74)
kira-dir (200): dird/scheduler.cc:331-0 enter find_runs()
kira-dir (200): dird/scheduler.cc:347-0 now = 5e1442d4: h=9 m=0 md=6
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:367-0 nh = 5e1450e4: h=10 m=0 md=6
wd=2 wom=0 woy=2 yday=6
kira-dir (200): dird/scheduler.cc:450-0 Leave find_runs()

Any hints? What else could i check?

Best,

Kai

Kai Zimmer

unread,
Jan 13, 2020, 3:53:00 AM1/13/20
to bareos-users
Hi again,

sorry for the wrong terminology. In fact bconsole doesn't 'exit', but it
crashes. Any way to get more information about that?

Best,
Kai

Jörg Steffens

unread,
Jan 13, 2020, 9:20:01 AM1/13/20
to bareos...@googlegroups.com
On 13.01.20 at 09:52 wrote Kai Zimmer:
> Hi again,
>
> sorry for the wrong terminology. In fact bconsole doesn't 'exit', but it
> crashes. Any way to get more information about that?

Are you sure, the bconsole crashes? Or does the Director crash and
therefore the bconsole connection gets closed?

The setdebug command you use sets the Director into debug mode.
Therefore Director messages (kira-dir) are shown.
If the want to debug the bconsole, you should start it with parameter:
"bconsole -d 200"

Regards,
Jörg
--
Jörg Steffens joerg.s...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 630693-91
http://www.bareos.com Fax: +49 221 630693-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer:
S. Dühr, M. Außendorf, Jörg Steffens, P. Storz

Reply all
Reply to author
Forward
0 new messages