Re: SD won't start after upgrade
"D." <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Message-ID | <[email protected]> |
Thank you, Bill. It appears that bacula-sd (via systemd) is no longer content with the permissions on its config file '/opt/bacula/etc/bacula-sd.conf' which has never changed. The permissions were: -rw-rw----. 1 root disk 9894 Nov 5 2023 bacula-sd.conf and that worked fine for years, but now it doesn't since the packages upgrade. I changed the group to 'bacuala' and now the service starts and runs. Does that seem like an acceptable work-around to you? --- On 11/20/2024 12:16 PM, Bill Arlofski via Bacula-users wrote: > On 11/20/24 9:59 AM, D. wrote: >> I upgraded from 13.0.4 to 15.0.2 on two Oracle Linux 8.10 servers. In >> both cases, the bacula-sd.service daemon won't start after the upgrade. >> The DIR and FD daemons start just fine. The DIR seems to interact with >> the upgraded database just fine. >> >> The lack of logging has me stumped as to how I should further >> troubleshoot this problem. >> >> Any thoughts? >> >> I thought about compiling it myself and seeing if my compiled SD starts, >> but I don't have the knowledge to compile myself. Hmph... > > Hello, > > You can star the SD in foreground mode with debug enabled. The reason > for the failure to start will usually be pretty clear - usually a > permissions issue cause by the service being started manually as the > root user at some point. > > # sudo -u bacula /opt/bacula/bin/bacula-sd -f -d100 > > Make sure to start the SD using sudo like this - and not starting as > root user using -u and -g command line options - so that there is no chan > ce of the daemon starting as root, being able to read files that the > bacula user may not have access to, and then dropping privileges to > become the bacula user. Basic permission issues can be missed this way. :) > > Typically, the *.pid file might be owned `root:root` which will prevent > systemd, or the sudo command above from allowing the SD to start - and > systemd does not tell you why it didn't start, but the above command > will reveal the issue. > > > Hope this helps, > Bill > > > > _______________________________________________ > Bacula-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bacula-users _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users