I hope I posted this in the correct forum; when I did a forum search for "bacula", many of the posts were in this (Web & Network Services) forum. My apologies if I posted in the wrong forum.
I have 3 FreeBSD systems that I backup using 2 other FreeBSD systems running Bacula. My backups have been running successfully for several months now. Last night, instead of receiving my normal 6 (3 systems x 2 backup systems) email messages of cron output from my Bacula jobs, I instead received an error message emailed to me from each Bacula host:
When I attempted to connect to my Bacula servers using the Bacula console, I could not connect and I discovered that the Bacula director daemons on each Bacula system weren't running. After starting the Bacula director on each Bacula system with [cmd=]/usr/local/etc/rc.d/bacula-dir start[/cmd], I verified that it was running with [cmd=]ps ax | grep bacula[/cmd], however the director daemon would not be running after about 10 seconds or so.
The only significant, recent change to my 2 Bacula systems is that I did a portupgrade of MySQL from 5.0.91 to 5.0.92 yesterday morning. And since I did this upgrade after the last successful backup, before the problems occurred and the fact that Bacula uses MySQL for it's catalog, I believe that this is suspect.
I did a lot of Googling on the error messages, but could not find anything that helped me enough to solve the problem. I admit I don't really know how to interpret the error message above. I'm also wondering if either the MySQL folks or the Bacula folks might soon have a package upgrade that will fix my problem? Sometimes that has been the case with some ports packages problems in the past.
- Gavin
I have 3 FreeBSD systems that I backup using 2 other FreeBSD systems running Bacula. My backups have been running successfully for several months now. Last night, instead of receiving my normal 6 (3 systems x 2 backup systems) email messages of cron output from my Bacula jobs, I instead received an error message emailed to me from each Bacula host:
Code:
(no debugging symbols found)...ptrace: Operation not permitted.
/var/db/bacula/31553: No such file or directory.
$1 = 0
/usr/local/share/bacula/btraceback.gdb:2: Error in sourced command file:
No symbol table is loaded. Use the "file" command
When I attempted to connect to my Bacula servers using the Bacula console, I could not connect and I discovered that the Bacula director daemons on each Bacula system weren't running. After starting the Bacula director on each Bacula system with [cmd=]/usr/local/etc/rc.d/bacula-dir start[/cmd], I verified that it was running with [cmd=]ps ax | grep bacula[/cmd], however the director daemon would not be running after about 10 seconds or so.
The only significant, recent change to my 2 Bacula systems is that I did a portupgrade of MySQL from 5.0.91 to 5.0.92 yesterday morning. And since I did this upgrade after the last successful backup, before the problems occurred and the fact that Bacula uses MySQL for it's catalog, I believe that this is suspect.
I did a lot of Googling on the error messages, but could not find anything that helped me enough to solve the problem. I admit I don't really know how to interpret the error message above. I'm also wondering if either the MySQL folks or the Bacula folks might soon have a package upgrade that will fix my problem? Sometimes that has been the case with some ports packages problems in the past.
- Gavin