Hello Kern,
I just upgraded one of our bacula installations from 7.0.6 to 7.2.0.
Until now i used bacula user for bacula-sd and bacula-dir, only
bacula-fd is running as root and worked fine until 7.2.0.
Now bacula-sd and bacula-dir failed to start because the pid file
cannot be created because auf permission problem.
The default piddir is /var/run which is owned by root:root and
has permission 0755 on RedHat or CentOS machines, i think that is
not different from other Linux variants.
Looking at
git diff ce5634e327b6faa90fcc947179ff55963823ba79 src/stored/stored.c
if found that the daemon start code has moved up before the pid
file is created. This means the bacula-sd user (bacula in my case)
needs permission to create/write files in pid directory /var/run.
- if (!foreground) {
- daemon_start(); /* become daemon */
- init_stack_dump(); /* pick up new pid */
- }
Has this change done by intention ?
Do we need now /var/run/bacula pid directory which is owned
by bacula ?
Best regards
Ulrich
On Fri, 2015-08-14 at 14:23 +0200, Kern Sibbald wrote:
> Hello,
> > Our Bacula Systems gnome gurus have been working hard in the Swiss
> mountains, and their work is now released as Bacula version 7.2.0.
> You
> can find the source code at Source Forge as usual.
> > This version has quite a number of difficult and important bug fixes
> over version 7.0.5 as well as a good number of new features. I won't
> attempt to list all the new features here, but suggest that you look
> at
> the New Features chapter of the manual. Please note that there may
> be a
> few new features documented in the 7.2. section of the manual that
> were
> actually in 7.0.5 -- I just ran out of time at the end, so rather
> than
> miss a feature, I took the risk to include some already released.
> > This version has not been tested in production yet, so please test it
> carefully. That said, it is largely based on Bacula Enterprise
> version
> 8.2, which is extremely stable and it also has a number of fixes and
> features from the next, yet unreleased, Enterprise version as well as
> *all* the Enterprise bug fixes.
> > For certain of the new features, and a couple more yet to come, this
> version has a new catalog layout, which means that you must do a
> catalog
> upgrade (it is relatively simple). As always, please backup your
> database prior to applying the upgrade procedure.
> > Previously we supplied an update script for only one version. To
> avoid
> the proliferation of upgrade scripts in the future, we have settled
> on a
> single script (update_bacula_tables), which will upgrade from version
> 3.0.x to version 5.2.x (same as 7.0.x) and to the new 7.2.0 format.
> So
> the procedure much simpler.
> As soon as we can update the bacula.org web site to have a sort of
> more
> automated download area, we will move our source release to the
> bacula.org web site and begin furnishing binaries.
> > Many thanks to Bacula Systems for providing the bug fixes and new
> features. Since the development process in Bacula Systems is going
> faster (more programmers), we can expect even more features in future
> versions.
> > You may notice a few license/copyright changes, but these are all
> very
> positive for the community version and its future. I will go into it
> in
> more detail on this point in a Status Report that will follow this
> announcement in a few days.
> > Thanks for using Bacula.
> > Best regards,
> Kern
> > ---------------------------------------------------------------------
> ---------
> _______________________________________________
> Bacula-devel mailing list
> Bacula-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-devel
------------------------------------------------------------------------------
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
