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.
