Hello, On 01/04/2016 05:49 AM, Daniel Bareiro wrote: > Hi all and Happy New Year!! [snip] >> Dec 26 11:31:04 baculatest bacula-dir[3045]: Starting Bacula Director: >> bacula-dir >> ---------------------------------------------------------------------- >> >> But I do not see the running processes: >> >> ---------------------------------------------------------------------- >> root@baculatest:~# ps ax | grep bacula >> 3055 pts/1 S+ 0:00 grep bacula >> ---------------------------------------------------------------------- >> >> Have you had a problem like this and found the cause of it? > > I would appreciate any comments about this.
Your lock and subsys directories might not exist or be of the right permission or your config file might have a syntax error in it. To debug this, try running the director like this: # bacula-dir -t If it comes back with a 0 return value, then your config file is of a good syntax. Then try: # bacula-dir -v -f -d100 This runs it verbosely in the foreground and should likely explain why your daemon didn't want to start up. If it starts properly, then CTRL-C to quit it. I noticed that, at least under Debian 8, I needed to add the Linux Standards Base information to all of the startup scripts and ensure (the director's) dependencies included postres so it would start in the right order. Otherwise the update-rc.d program would insist upon starting them in S01 and it would just fail to start since postgres was in S02. I also noticed that, since I used my own locations for the subsys directory and pidfile, that those directories I chose in /var/run and /var/run/lock MUST be created by the startup scripts (since they were deleted by the system upon shutdown). So I also had to add that code to the startup scripts as well. Thank you! -pete ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
