FileDaemon on opensuse will not start

[Sven Gehr]

Hi@all,

until three days ago everything worked normal. My bareos-director is install on a ubuntu-server (12.04.01 LTS 64Bit) and I install th file-deamon on a lot of clients:

- windows7 64
- CentOS 64.
- OpenSuSE 12.3 64Bit

until three days I get the error from my director:

12-Jun 23:05 vmhost21-dir JobId 215: Start Backup JobId 215, Job=tux20.2013-06-12_23.05.00_36
12-Jun 23:05 vmhost21-dir JobId 215: Using Device "FileStorage" to write.
12-Jun 23:05 vmhost21-dir JobId 215: Warning: bsock.c:126 Could not connect to Client: tux20-fd on tux20.local.lan:9102. ERR=Connection refused
Retrying ...
12-Jun 23:08 vmhost21-dir JobId 215: Fatal error: bsock.c:132 Unable to connect to Client: tux20-fd on tux20.local.lan:9102. ERR=Connection refused
12-Jun 23:08 vmhost21-dir JobId 215: Fatal error: No Job status returned from FD.
12-Jun 23:08 vmhost21-dir JobId 215: Error: Bareos vmhost21-dir 12.4.3 (15Apr13):
Build OS: x86_64-pc-linux-gnu ubuntu Ubuntu 12.04 LTS
JobId: 215
Job: tux20.2013-06-12_23.05.00_36
Backup Level: Incremental, since=2013-06-06 23:05:34
Client: "tux20-fd" 12.4.3 (15Apr13) x86_64-suse-linux-gnu,suse,openSUSE 12.3 (x86_64)
FileSet: "tux20 Set" 2013-04-29 17:32:02
Pool: "Incr" (From Job IncPool override)
Catalog: "MyCatalog" (From Pool resource)
Storage: "File" (From Job resource)
Scheduled time: 12-Jun-2013 23:05:00
Start time: 12-Jun-2013 23:05:28
End time: 12-Jun-2013 23:08:28
Elapsed time: 3 mins
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0 (0 B)
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 26
Volume Session Time: 1370579282
Last Volume Bytes: 763,689,713 (763.6 MB)
Non-fatal FD errors: 1
SD Errors: 0
FD termination status: Error
SD termination status: Waiting on FD
Termination: *** Backup Error ***

Whe I try to (re)start the service on the client I get the error:

tux20:/usr/sbin # /etc/init.d/bareos-fd restart
redirecting to systemctl restart bareos-fd
Job for bareos-fd.service failed. See 'systemctl status bareos-fd.service' and 'journalctl -n' for details.

.....

- Logs begin at Thu, 2013-06-13 06:42:52 CEST, end at Thu, 2013-06-13 07:06:40 CEST. --
Jun 13 06:57:32 tux20.local.lan systemd[1]: Unit bareos-fd.service entered failed state
Jun 13 06:57:50 tux20.local.lan systemd[1]: Starting Cleanup of Temporary Directories...
Jun 13 06:57:51 tux20.local.lan systemd[1]: Started Cleanup of Temporary Directories.
Jun 13 07:00:01 tux20.local.lan /usr/sbin/cron[1474]: pam_unix(crond:session): session opened for user root by (uid=0)
Jun 13 07:00:01 tux20.local.lan /USR/SBIN/CRON[1474]: pam_unix(crond:session): session closed for user root
Jun 13 07:04:35 tux20.local.lan slapd[1041]: conn=1009 op=1 do_bind: invalid dn (NTLM)
Jun 13 07:06:40 tux20.local.lan systemd[1]: Starting Bareos File Daemon service...
Jun 13 07:06:40 tux20.local.lan systemd[1]: bareos-fd.service never wrote its PID file. Failing.
Jun 13 07:06:40 tux20.local.lan systemd[1]: Failed to start Bareos File Daemon service.
Jun 13 07:06:40 tux20.local.lan systemd[1]: Unit bareos-fd.service entered failed state

I remove the package, restart the machine and reinstall the bareos-file-daemon but that does not help.

My conf's:

<director>

[...]
Client {
Name = tux20-fd
Address = tux20.local.lan
Catalog = MyCatalog
Password = "$#edv_bareos
AutoPrune = no
}
[...]

<file-daemon>

Director {
Name = vmhost21-dir
Password = "$#edv_bareos"
}

Director {
Name = tux20-mon
Password = "$#edv_bareos"
Monitor = yes
}

FileDaemon {
Name = tux20-fd
Maximum Concurrent Jobs = 20
# remove comment in next line to load plugins from specified directory
# Plugin Directory = /usr/lib64/bareos/plugins
}

Messages {
Name = Standard
director = vmhost21-dir = all, !skipped, !restored
}

any idea?

with best regards
sven

[Marco van Wieringen]

Sven Gehr <sven.gehr <at> gmail.com> writes:

>
> Hi <at> all,
>
...

> Whe I try to (re)start the service on the client I get the error:
>
> tux20:/usr/sbin # /etc/init.d/bareos-fd restart
> redirecting to systemctl restart bareos-fd
> Job for bareos-fd.service failed. See 'systemctl status bareos-fd.service'
and 'journalctl -n' for details.
>

That is the normal output on that platform as init scripts
are no longer used and everything is started from systemd.

> .....

>
> Jun 13 07:06:40 tux20.local.lan systemd[1]: Starting Bareos File Daemon
service...
> Jun 13 07:06:40 tux20.local.lan systemd[1]: bareos-fd.service never wrote
its PID file. Failing.
> Jun 13 07:06:40 tux20.local.lan systemd[1]: Failed to start Bareos File
Daemon service.
> Jun 13 07:06:40 tux20.local.lan systemd[1]: Unit bareos-fd.service entered
failed state
>
>

> any idea?
>
I think its time to run the basic tests you should always do:

bareos-fd -t

e.g. test your config. That should return without any error.
And then bareos-fd in debug mode e.g.

bareos-fd -f -d 100

That should reveal at least some more information why the daemon
exits before writing its pidfile.

I guess you normally run your file daemon under root so run these
tests while being either logged in a root or su-ed or sudo-ed to root.

--
Marco van Wieringen marco.van...@bareos.com
Bareos GmbH & Co. KG Phone: +49-221-63069389
http://www.bareos.com

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

[Sven Gehr]

Am Donnerstag, 13. Juni 2013 10:08:44 UTC+2 schrieb Marco van Wieringen:
> Sven Gehr <sven.gehr <at> gmail.com> writes:

> ...
> > Whe I try to (re)start the service on the client I get the error:
> > tux20:/usr/sbin # /etc/init.d/bareos-fd restart
> > redirecting to systemctl restart bareos-fd
> > Job for bareos-fd.service failed. See 'systemctl status bareos-fd.service'

> and 'journalctl -n' for details.

> That is the normal output on that platform as init scripts
> are no longer used and everything is started from systemd.

ok

> I think its time to run the basic tests you should always do:
> bareos-fd -t

No error reported

> e.g. test your config. That should return without any error.
> And then bareos-fd in debug mode e.g.
> bareos-fd -f -d 100

report this:

tux20:~ # bareos-fd -t -d 100
bareos-fd: filed_conf.c:472-0 Inserting director res: vmhost21-mon

[Marco van Wieringen]

It seems it only parses your config but doesn't do anything else.

I normally get this as output for a debug 100

mercury-fd: jcr.c:130-0 read_last_jobs seek to 192
mercury-fd: jcr.c:137-0 Read num_items=10
mercury-fd: filed.c:260-0 filed: listening on port 9102
mercury-fd: bnet_server.c:161-0 Addresses host[ipv4:0.0.0.0:9102]

So for whatever reason your fd never gets to the moment it starts
listening for a connection.

You could look with strace to see what its up to. Maybe a problem
with name resolution ? Does getent hosts <hostname> work ?

[Sven Gehr]

my configuration was not the problem. Bareos was the problem. After update the last update without change the config it works ....... mixed feelings!