[Bug 212282] sysutils/bareos-server: director fails to start on reboot with /var/run on tmpfs

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212282

            Bug ID: 212282
           Summary: sysutils/bareos-server: director fails to start on
                    reboot with /var/run on tmpfs
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: acm at FreeBSD.org
          Reporter: ohartman at zedat.fu-berlin.de
          Assignee: acm at FreeBSD.org
             Flags: maintainer-feedback?(acm at FreeBSD.org)

We use /var/run bound as tmpfs, so the pidfile required by this incarnation of
the bareos-server doesn't work properly:

service bareos-dir start/restart

fails silently on systems that have been rebooted after the installation of the
port due to the missing folder

/var/run/bareos/

where the script files/bareos-dir.in (later residing in
/usr/local/etc/rc.d/bareos-dir) expects the pidfile.

Checking the rc-script, I do not find any checks for the existence of
/var/run/bareos or suitable tests for traversal.

This issue has already been dealt with by FreeBSD a long time ago since tmpfs
is a possible filesystem (memory backed) even for /var/run for some security
issues.

Either a proper check for the existence of the folder /var/run/bareos/ needs to
be applied or the pidfile simply should be dropped into folder /var/run/ which
very existence is guaranteed by FreeBSD itself.

Or I have misunderstood something.

Quick and dirty workaround:

Change /var/run/bareos/ into /var/run or explicitely set 

 bareos_dir_pidfile="/var/run/bareos-dir.9101.pid"

in /etc/rc.conf or /etc/rc.conf.local

-- 
You are receiving this mail because:
You are the assignee for the bug.