Bareos-dir won't start anymore: Job for bareos-director.service failed because a fatal signal was delivered causing the control process to dump core.

[M-D-F]

I have an issue which reads a bit similiar to this one:

https://groups.google.com/forum/#!topic/bareos-users/3FmivVjH0a4

It's bareos-dir Version: 17.2.4 (21 Sep 2017) x86_64-pc-linux-gnu ubuntu Ubuntu 16.04 LTS

The installation is working since several months, I only stopped it to make a minor change in one of the job files. Afterwards it refused to start:

/usr/sbin/bareos-dir -t -d 500 -u bareos -g bareos 

gives 

BAREOS interrupted by signal 11: Segmentation violation

Speicherzugriffsfehler (Speicherabzug geschrieben)

and the file attached. 

I can't see any apparent errors so far? 

I'm using mysql as catalog backend. The DB is quite big meanwhile, having around 16041909 Rows in the "File" Table.

Interestingly Bareos starts up if I do 

/usr/sbin/bareos-dir -d 500 -u bareos -g bareos 

So then I'm also able to connect bconsole and Webui and all Jobs went through fine until I stopped the director. Didn't do further testing and will do a full backup of the machine in question before fiddling around any further.

Sadly I did "testwise" rm all /var/lib/ files connected to the dir, maybe one of those files did contain some messages of interest which would have flooded bconsole after opening.

I also compared the result to another bareos installation of similiar age which is still working and the debug output looks very similiar, especially the DB-Part ... so actually I don't have the faintest idea.

Can anybody take a look and give a hint?

Thanks to all and regards,

M. Finke

 

[M-D-F]

Meanwhile I'm able to acknowledge: a recovered version of the machine just from the night before shows exactly the same issue. So it basically broke without any intervention.

My uneducated guess still is with the catalog but then I don't have a ****ing clue but it seems I'm not the only one :-).

As Bareos was more or less in testing mode for the "big" fileservers I will simply move on I guess and start over for the small needs with some linux machines (which worked fine so far since years). If I really need some recovery from the "broken" installation i'm positive I can do it by starting the director manually.