bareos-dir does not start at system boot

[cocolocko]

hi @ all,

i am running CentOS v6.6 with Bareos 13.2.2.
I have the problem that "bareos-dir" does not come up at system start. ( only bareos-fd and bareos-sd processes are running!)
But if i start it manually, it works! I can also connect to "bconsole" and run jobs. /var/log/bareos/bareos.log gave me this error:

11-Jun 15:23 bareos-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bareos".
11-Jun 15:23 bareos-dir JobId 0: Fatal error: postgresql.c:238 Unable to connect to PostgreSQL server. Database=bareos User=bareos
Possible causes: SQL server not running; password incorrect; max_connections exceeded.
11-Jun 15:23 bareos-dir ERROR TERMINATION
Please correct configuration file: /etc/bareos/bareos-dir.conf

But i am wondering, i can manually connect to that database with "psql" and also list tables.
Some hints for me?
Thanks a lot!

Greetings

[Bruno Friedmann]

Have a check first of /usr/systemd/system/bareos-dir.service
It ask systemd to start after postgresql service
After=nss-lookup.target network.target remote-fs.target time-sync.target postgresql.service mysql.service

Now as you perhaps still have the old sysV init you will have to check if the /etc/init.d/bareos-dir
has a dependency on after postgresql so it let a chance to the dir to find postgresql up and ready
during boot sequence.

I'm surprise if the init script doesn't already contain it. Did you have a personal copy or something like that ?

--

Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Board, fsfe fellowship
GPG KEY : D5C9B751C4653227
irc: tigerfoot

[cocolocko]

hmm, CentOS 6 has sysV init. (CentOS 7 has SystemD)
and no,/etc/init.d/bareos-dir does not have a dependency, or what did you mean exactly? What personal copy do you mean? The copy of /etc/init.d/bareos-dir?

Greetings

[Bruno Friedmann]

On Friday 12 June 2015 03.13:34 cocolocko wrote:
> hmm, CentOS 6 has sysV init. (CentOS 7 has SystemD)
> and no,/etc/init.d/bareos-dir does not have a dependency, or what did you mean exactly? What personal copy do you mean? The copy of /etc/init.d/bareos-dir?
>
> Greetings
>

A quick look at github sources reveal the following

in platform/suse we have the full deps clearly stated
in bareos-dir

### BEGIN INIT INFO
# Provides: bareos-dir
# Required-Start: $local_fs $remote_fs $network $time $syslog
# Should-Start: postgresql mysql bareos-sd bareos-fd
# Required-Stop: $local_fs $remote_fs $network
# Should-Stop: postgresql mysql bareos-sd bareos-fd
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: bareos director
# Description: Bareos network backup system director daemon
### END INIT INFO

Those header are missing in the redhat one.
Now I'm not an expert in redhat platform


Compare https://github.com/bareos/bareos/blob/master/platforms/suse/bareos-dir.in
to
https://github.com/bareos/bareos/blob/master/platforms/redhat/bareos-dir.in

If you successfully adapt the suse to redhat platforms I encourage you to open a bug report
and insert the line you've added to make the script working on Centos/Redhat sysV system.

[Stephan Duehr]

That is correct, the init-script templates for RHEL6/CentOS6 come from
https://github.com/bareos/bareos/tree/master/platforms/redhat
and dont't have LSB INIT INFO blocks, although RHEL/CentOS supports them
since Version 5 as far as I know.

I've never seen this causing problems before.

How does "ls -la /etc/rc3.d/" look like in your case?

RHEL6/CentOS6 uses upstart, but no parellelization is used for
normal SysV init scripts. So they are run sequentially in the
order determined by the links in the runlevel directory.

If you manually add a LSB INIT BLOCK, remember to do
chkconfig --del bareos-dir
chkconfig --add bareos-dir
to update the runlevel links.

It's indeed appreciated if you report this at https://bugs.bareos.org
and suggest a fix.

Regards

Stephan

>
>
>
> >
> > Am Freitag, 12. Juni 2015 08:59:51 UTC+2 schrieb Bruno Friedmann:
> > > On Thursday 11 June 2015 09.20:21 cocolocko wrote:
> > > > hi @ all,
> > > >
> > > > i am running CentOS v6.6 with Bareos 13.2.2.
> > > > I have the problem that "bareos-dir" does not come up at system start. ( only bareos-fd and bareos-sd processes are running!)
> > > > But if i start it manually, it works! I can also connect to "bconsole" and run jobs. /var/log/bareos/bareos.log gave me this error:
> > > >
> > > > 11-Jun 15:23 bareos-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bareos".
> > > > 11-Jun 15:23 bareos-dir JobId 0: Fatal error: postgresql.c:238 Unable to connect to PostgreSQL server. Database=bareos User=bareos
> > > > Possible causes: SQL server not running; password incorrect; max_connections exceeded.
> > > > 11-Jun 15:23 bareos-dir ERROR TERMINATION
> > > > Please correct configuration file: /etc/bareos/bareos-dir.conf
> > > >
> > > > But i am wondering, i can manually connect to that database with "psql" and also list tables.
> > > > Some hints for me?
> > > > Thanks a lot!
> > > >
> > > > Greetings
> > > >
> > > >
> > > >
> > > Have a check first of /usr/systemd/system/bareos-dir.service
> > > It ask systemd to start after postgresql service
> > > After=nss-lookup.target network.target remote-fs.target time-sync.target postgresql.service mysql.service
> > >
> > > Now as you perhaps still have the old sysV init you will have to check if the /etc/init.d/bareos-dir
> > > has a dependency on after postgresql so it let a chance to the dir to find postgresql up and ready
> > > during boot sequence.
> > >
> > > I'm surprise if the init script doesn't already contain it. Did you have a personal copy or something like that ?
> > >
> >
> >
>



--

Stephan Dühr stepha...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221-630693-90
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: S. Dühr, M. Außendorf,
J. Steffens, Philipp Storz, M. v. Wieringen