Will McDonald <[EMAIL PROTECTED]> > > I've switched to 1.38.5-4 in the hopes of resolving the volume > management problems I've been having. [snip]
> I built these RPMs on a CentOS 4 system with... > > rpmbuild --rebuild --define "build_centos4 1" --define "build_mysql 1" > --define "build_mysql4 1" /home/wmcdonald/bacula-1.38.5-4.src.rpm [snip] > [EMAIL PROTECTED] bacula]# /etc/bacula/bacula status > bacula-sd (pid 19307) is running... > bacula-fd (pid 19312) is running... > bacula-dir dead but pid file exists When I did the upgrade from 1.38.2 to 1.38.5-2 on my RHEL4.2 system via rpmbuild, there were a few gotchas that stopped the director from starting. One was that /etc/sysconfig/bacula needed these lines: DIR_USER="bacula" DIR_GROUP="disk" The others were file permissions on /etc/bacula and it's contents, /var/bacula and it's contents, and I think the directory where those pid files above were stored. This is all due to the well-documented change of default behavior some place between 1.38.2 and 1.38.5, where the RPM's are installed running as non-root users by default instead of running as root in the past. Don't have a clue if this is your problem or not, but figured that it's be a good place to start... -Arthur P.S. Make sure to also check your bacula-sd's permissions to write to disk, if you're using that option. It'll happily start up, and then complain about not being able to find a volume when the first backup runs if the permissions are wrong. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
