On 01/04/2016 09:45 AM, Daniel Bareiro wrote: > I think LSB lines are correct: > > ---------------------------------------------------------------- > ### BEGIN INIT INFO > # Provides: bacula-dir > # Required-Start: $network > # Should-Start: bacula-fd postgresql mysql
Shouldn't postgresql and mysql be on the Required-Start line? And, for me, it was postgres > # Required-Stop: $network > # Default-Start: 2 3 4 5 > # Default-Stop: 0 1 6 > # Short-Description: Start Bacula Director daemon at boot time > # Description: Enable Bacula Director. > ### END INIT INFO Mine looks like this: ### BEGIN INIT INFO # Provides: bacula-ctl-dir # Required-Start: $local_fs $remote_fs $syslog $network $time postgresql # Required-Stop: $local_fs $remote_fs $syslog $network $time postgresql # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Bacula Directory Daemon # Description: Bacula Directory Daemon Service ### END INIT INFO > But unfortunately, even with these changes, the processes was not able > to starts up: Ah, in this case, here is what I did to debug further: I believe /etc/init.d/bacula-dir is the script you are running, so: # sh -x /etc/init.d/bacula-dir Then you'll be presented with the command line that is actually executed when the startup script executes bacula-dir. Run that as root and add the -v -f -d100 arguments. Those extra arguments may shake out the problem. [ASIDE: I used the bacula-ctl-* scripts in the bacula distribution, are you?] I found it took quite a while to get the startup scripts working properly since they were missing the LSB stuff and the creation of the pidfile directory and subsys directory. I found that they would work when tested by hand, but not during actual reboots until I had made code changes and fixed the behavior. Thank you! -pete ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users