Testing with an old library, got anomalous results after deleting all the volumes in bconsole and then doing a "label barcodes": the director simply exited after loading the first tape. (I did turn "Check Labels = yes" on since I last ran this, that may be the cause, don't know yet.)
The intermingled output is because I ran "bareos-sd -f -v -d99 &" at the same tty prior to starting bconsole. [...] Do you want to label these Volumes? (yes|no): yes Automatically selected Pool: Full Connecting to Storage daemon Tape at amanda1:9103 ... amanda1-sd (50): cram-md5.c:68-0 send: auth cram-md5 <1881227670.1444429922@amanda1-sd> ssl=0 amanda1-sd (99): cram-md5.c:143-0 sending resp to challenge: C7/03Wc289R9IQBnGW+oaB amanda1-sd (90): dir_cmd.c:256-0 Message channel init completed. Sending label command for Volume "000001L3" Slot 1 ... amanda1-sd (20): dir_cmd.c:831-0 Found changer device tapedrive-0 amanda1-sd (90): dir_cmd.c:668-0 try_autoload_device - looking for volume_info 3301 Issuing autochanger "loaded? drive 0" command. 3302 Autochanger "loaded? drive 0", result: nothing loaded. 3304 Issuing autochanger "load slot 1, drive 0" command. 3305 Autochanger "load slot 1, drive 0", status is OK. [root@amanda1 bareos]# [root@amanda1 bareos]# bconsole Connecting to Director amanda1:9101 ^C [root@amanda1 bareos]# [root@amanda1 bareos]# ps ax|grep dir [root@amanda1 bareos]# I see a nice email: <<__EOF__ From [email protected] Fri Oct 9 17:33:27 2015 Return-Path: <[email protected]> X-Original-To: root@localhost Delivered-To: [email protected] From: [email protected] Subject: Bareos GDB traceback of bareos-dir on amanda1.ad.avant.ca Sender: [email protected] To: [email protected] Date: Fri, 09 Oct 2015 17:33:26 -0500 (CDT) Status: R Created /var/lib/bareos/bareos-dir.core.30510 for doing postmortem debugging [New Thread 30512] [New Thread 30514] [New Thread 30515] [New Thread 30516] [New Thread 31201] [New Thread 31325] [New Thread 30510] [Thread debugging using libthread_db enabled] Core was generated by `/usr/sbin/bareos-dir -g bareos -c /etc/bareos/bareos-dir.conf'. #0 0x00007f360e915fbd in nanosleep () from /lib64/libpthread.so.0 $1 = 1851878753 $2 = 31572072 $3 = 31572136 /usr/lib/bareos/scripts/btraceback.gdb:4: Error in sourced command file: No symbol table is loaded. Use the "file" command. Running "gdb /usr/sbin/bareos-dir /var/lib/bareos/bareos-dir.core.30510" lets me get a rather useless stack trace, and I'm installing the -debug RPMs but on this DSL line that will take quite a while. Posting preemptively in case someone else has seen this. -Adam Thompson -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
