Re: [bareos-users] Still Problems with crashed SD on 16.2.4
Hi, looks good! Thank you. Regards, Oliver > Hi Stephan, > > thanks a lot! That option was indeed switched on for some reason. As well as > Collect Device Statistics which I left activated. > > I'll report back later whether that helped. > > Regards, > > Oliver > > > > Hi, > > > > that looks like a problem in job statistics collection. > > > > If you have > > Collect Job Statistics = yes > > in your bareos-sd configuration, please set it to > > Collect Job Statistics = no > > > > Then restart bareos-sd and check if it still crashes. > > > > Regards, > > > > Stephan > > > > On 01/09/2017 03:14 PM, Oliver Hoffmann wrote: > > > Hi list, > > > > > > I have an output of gdb now. Lots and lots of entries like that > > > > > > [New Thread 0x7fffe700 (LWP 18030)] > > > [Thread 0x7fffe700 (LWP 18030) exited] > > > > > > then > > > > > > New Thread 0x7fffe700 (LWP 18117)] > > > [New Thread 0x7fffee7fc700 (LWP 18122)] > > > [New Thread 0x7fffedffb700 (LWP 18135)] > > > [New Thread 0x7fffed7fa700 (LWP 18139)] > > > [New Thread 0x7fffecff9700 (LWP 18140)] > > > [New Thread 0x7fffc700 (LWP 18141)] > > > [New Thread 0x7fffcf7fe700 (LWP 18142)] > > > [New Thread 0x7fffceffd700 (LWP 18143)] > > > [New Thread 0x7fffce7fc700 (LWP 18144)] > > > [New Thread 0x7fffcdffb700 (LWP 18145)] > > > [New Thread 0x7fffcd7fa700 (LWP 18146)] > > > [New Thread 0x7fffccff9700 (LWP 18147)] > > > [Thread 0x7fffe700 (LWP 18117) exited] > > > [New Thread 0x7fffe700 (LWP 18148)] > > > > > > and eventually > > > > > > Program received signal SIGSEGV, Segmentation fault. > > > [Switching to Thread 0x7fffeeffd700 (LWP 14721)] > > > 0x004179fb in update_job_statistics (jcr=0x7fffdc001078, > > > now=1483746304) at sd_stats.c:296 > > > 296 sd_stats.c: No such file or directory. > > > > > > Any ideas? > > > > > > Regards, > > > > > > Oliver > > > > > > > > > -- > > Stephan Dühr stephan.du...@bareos.com > > Bareos GmbH & Co. KG Phone: +49 221-630693-90 > > http://www.bareos.com > > > > 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. Steffens, Philipp Storz -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Still Problems with crashed SD on 16.2.4
Hi Stephan, thanks a lot! That option was indeed switched on for some reason. As well as Collect Device Statistics which I left activated. I'll report back later whether that helped. Regards, Oliver > Hi, > > that looks like a problem in job statistics collection. > > If you have > Collect Job Statistics = yes > in your bareos-sd configuration, please set it to > Collect Job Statistics = no > > Then restart bareos-sd and check if it still crashes. > > Regards, > > Stephan > > On 01/09/2017 03:14 PM, Oliver Hoffmann wrote: > > Hi list, > > > > I have an output of gdb now. Lots and lots of entries like that > > > > [New Thread 0x7fffe700 (LWP 18030)] > > [Thread 0x7fffe700 (LWP 18030) exited] > > > > then > > > > New Thread 0x7fffe700 (LWP 18117)] > > [New Thread 0x7fffee7fc700 (LWP 18122)] > > [New Thread 0x7fffedffb700 (LWP 18135)] > > [New Thread 0x7fffed7fa700 (LWP 18139)] > > [New Thread 0x7fffecff9700 (LWP 18140)] > > [New Thread 0x7fffc700 (LWP 18141)] > > [New Thread 0x7fffcf7fe700 (LWP 18142)] > > [New Thread 0x7fffceffd700 (LWP 18143)] > > [New Thread 0x7fffce7fc700 (LWP 18144)] > > [New Thread 0x7fffcdffb700 (LWP 18145)] > > [New Thread 0x7fffcd7fa700 (LWP 18146)] > > [New Thread 0x7fffccff9700 (LWP 18147)] > > [Thread 0x7fffe700 (LWP 18117) exited] > > [New Thread 0x7fffe700 (LWP 18148)] > > > > and eventually > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 0x7fffeeffd700 (LWP 14721)] > > 0x004179fb in update_job_statistics (jcr=0x7fffdc001078, > > now=1483746304) at sd_stats.c:296 > > 296 sd_stats.c: No such file or directory. > > > > Any ideas? > > > > Regards, > > > > Oliver > > > > > -- > Stephan Dühr stephan.du...@bareos.com > Bareos GmbH & Co. KG Phone: +49 221-630693-90 > http://www.bareos.com > > 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. Steffens, Philipp Storz -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Still Problems with crashed SD on 16.2.4
Hi, that looks like a problem in job statistics collection. If you have Collect Job Statistics = yes in your bareos-sd configuration, please set it to Collect Job Statistics = no Then restart bareos-sd and check if it still crashes. Regards, Stephan On 01/09/2017 03:14 PM, Oliver Hoffmann wrote: > Hi list, > > I have an output of gdb now. Lots and lots of entries like that > > [New Thread 0x7fffe700 (LWP 18030)] > [Thread 0x7fffe700 (LWP 18030) exited] > > then > > New Thread 0x7fffe700 (LWP 18117)] > [New Thread 0x7fffee7fc700 (LWP 18122)] > [New Thread 0x7fffedffb700 (LWP 18135)] > [New Thread 0x7fffed7fa700 (LWP 18139)] > [New Thread 0x7fffecff9700 (LWP 18140)] > [New Thread 0x7fffc700 (LWP 18141)] > [New Thread 0x7fffcf7fe700 (LWP 18142)] > [New Thread 0x7fffceffd700 (LWP 18143)] > [New Thread 0x7fffce7fc700 (LWP 18144)] > [New Thread 0x7fffcdffb700 (LWP 18145)] > [New Thread 0x7fffcd7fa700 (LWP 18146)] > [New Thread 0x7fffccff9700 (LWP 18147)] > [Thread 0x7fffe700 (LWP 18117) exited] > [New Thread 0x7fffe700 (LWP 18148)] > > and eventually > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fffeeffd700 (LWP 14721)] > 0x004179fb in update_job_statistics (jcr=0x7fffdc001078, > now=1483746304) at sd_stats.c:296 > 296 sd_stats.c: No such file or directory. > > Any ideas? > > Regards, > > Oliver > -- Stephan Dühr stephan.du...@bareos.com Bareos GmbH & Co. KG Phone: +49 221-630693-90 http://www.bareos.com 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. Steffens, Philipp Storz -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Still Problems with crashed SD on 16.2.4
Hi list, I have an output of gdb now. Lots and lots of entries like that [New Thread 0x7fffe700 (LWP 18030)] [Thread 0x7fffe700 (LWP 18030) exited] then New Thread 0x7fffe700 (LWP 18117)] [New Thread 0x7fffee7fc700 (LWP 18122)] [New Thread 0x7fffedffb700 (LWP 18135)] [New Thread 0x7fffed7fa700 (LWP 18139)] [New Thread 0x7fffecff9700 (LWP 18140)] [New Thread 0x7fffc700 (LWP 18141)] [New Thread 0x7fffcf7fe700 (LWP 18142)] [New Thread 0x7fffceffd700 (LWP 18143)] [New Thread 0x7fffce7fc700 (LWP 18144)] [New Thread 0x7fffcdffb700 (LWP 18145)] [New Thread 0x7fffcd7fa700 (LWP 18146)] [New Thread 0x7fffccff9700 (LWP 18147)] [Thread 0x7fffe700 (LWP 18117) exited] [New Thread 0x7fffe700 (LWP 18148)] and eventually Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffeeffd700 (LWP 14721)] 0x004179fb in update_job_statistics (jcr=0x7fffdc001078, now=1483746304) at sd_stats.c:296 296 sd_stats.c: No such file or directory. Any ideas? Regards, Oliver -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Still Problems with crashed SD on 16.2.4
I installed those packages but maybe that 1970 issue is a clue already? Regards, Oliver -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Still Problems with crashed SD on 16.2.4
I witched off apparmor. Let's see. IP is just a replacement for official IPv4 ones. Thus no v6 here. I had a look in the btrace files and found something odd. threadid=0x7f63de24c700 JobId=1305 JobStatus=R jcr=0x7f63cc013798 name=mail-diff.2016-12-02_01.00.01_41 threadid=0x7f63de24c700 killable=0 JobId=1305 JobStatus=R jcr=0x7f63cc013798 name=mail-diff.2016-12-02_01.00.01_41 use_count=1 JobType=B JobLevel=D sched_time=02-Dec-2016 01:00 start_time=02-Dec-2016 01:00 end_time=01-Jan-1970 01:00 wait_time=01-Jan-1970 01:00 db=(nil) db_batch=(nil) batch_started=0 end_time and wait_time are 1970?? And then even start_time: sched_time=02-Dec-2016 01:00 start_time=01-Jan-1970 01:00 So in the beginning start_time is like expected and then the clients get a start time in 1970. Weird. Thank you! -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Still Problems with crashed SD on 16.2.4
Hello, Please install the debug packages and gdb and have a look at the tracebacks of the sd. They should tell you and us where the sd crashed. On 01.12.2016 17:22, Oliver Hoffmann wrote: > Hi list, > > I do one Volume file per Job. Means I have a Pool, Storage and folder with > full and diff Volumes for each client. Labeling and so on works now. I had > lots of issues in the past with that. Due to configuration and possibly bugs > in older Bareos versions. > > Problem now is that almost every time the SD crashes when all the Jobs start > (nine clients). I let monit restart the service and usually the rechedule > works though. > > Director/SD > Bareos 16.2.4 on Ubuntu 14.04 LTS with mysql 5.5.53-0ubuntu0.14.04.1 > > Subsequently I see something like this: > > Bareos daemon message > Warning: bsock_tcp.c:128 Could not connect to Storage daemon on IP:9103. > ERR=Connection refused > Retrying ... > > Bareos: Backup Unknown term code of win-client > Error: lib/bsock_tcp.c:422 Write error sending 12832 bytes to client:IP:9102: > ERR=Input/output error > Error: Director's comm line to SD dropped. > > Any ideas? > > Regards, > > Oliver > -- Mit freundlichen Grüßen Philipp Storz philipp.st...@bareos.com Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92 http://www.bareos.com Fax: +49 221 63 06 93-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Still Problems with crashed SD on 16.2.4
On jeudi, 1 décembre 2016 08.22:49 h CET Oliver Hoffmann wrote: > Hi list, > > I do one Volume file per Job. Means I have a Pool, Storage and folder with > full and diff Volumes for each client. Labeling and so on works now. I had > lots of issues in the past with that. Due to configuration and possibly > bugs in older Bareos versions. > > Problem now is that almost every time the SD crashes when all the Jobs start > (nine clients). I let monit restart the service and usually the rechedule > works though. > > Director/SD > Bareos 16.2.4 on Ubuntu 14.04 LTS with mysql 5.5.53-0ubuntu0.14.04.1 > > Subsequently I see something like this: > > Bareos daemon message > Warning: bsock_tcp.c:128 Could not connect to Storage daemon on IP:9103. > ERR=Connection refused Retrying ... > > Bareos: Backup Unknown term code of win-client > Error: lib/bsock_tcp.c:422 Write error sending 12832 bytes to > client:IP:9102: ERR=Input/output error Error: Director's comm line to SD > dropped. > > Any ideas? > > Regards, > > Oliver If you have apparmor on check what the limits are The other advise would be to run bareos-sd in debug mode to check if there's problem there. you used IP but are they ipv4 or ipv6 or the network has dual stack ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot openSUSE Tumbleweed Linux 4.8.10-1-default x86_64 GNU/Linux, nvidia: 375.20 Qt: 5.7.0, KDE Frameworks: 5.28.0, Plasma: 5.8.4, kmail2 5.3.3 (QtWebEngine) -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
