Discussion:
[bareos-users] Client backup failing - server connecting to bareos-fd fine.
j***@gmail.com
2018-06-13 20:23:26 UTC
Permalink
Hi All,

Any assistance greatly appreciated as new to BareOS.

Set up client, fileset, jobdef, job, and the client connects fine to the server. The backup fails, however, right at the beginning. I have added firewalld rules and iptables rules on the client and disabled both to test which did not help with the problem.

Connecting to Client osdev-ctrl1.cloud.csd.uwo.ca at 'redacted':9102

osdev-ctrl1-fd Version: 17.2.4 (21 Sep 2017) x86_64-redhat-linux-gnu redhat CentOS Linux release 7.4.1708 (Core)
Daemon started 13-Jun-18 15:40. Jobs: run=0 running=0.
Heap: heap=135,168 smbytes=35,949 max_bytes=38,762 bufs=68 max_bufs=97
Sizeof: boffset_t=8 size_t=8 debug=0 trace=0 bwlimit=0kB/s

Running Jobs:
bareos-dir (director) connected at: 13-Jun-18 16:02
No Jobs running.
====

Terminated Jobs:

Also does not seem to be a DNS issue - connected fine.

Connecting to Client testhost at *:9102
*

Job output -

Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 2
Volume Session Time: 1528918799
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Fatal Error
SD termination status: Waiting on FD
Termination: *** Backup Error ***

Many thanks, Joe
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jörg Steffens
2018-06-19 06:14:15 UTC
Permalink
The clients need to connect to the storage daemon, as defined in the
director. It could be related to this.

What does "list jobs" and "list joblog jobid=<jobid_of_a_failed_job>"
where reveal?
Post by j***@gmail.com
Hi All,
Any assistance greatly appreciated as new to BareOS.
Set up client, fileset, jobdef, job, and the client connects fine to the server. The backup fails, however, right at the beginning. I have added firewalld rules and iptables rules on the client and disabled both to test which did not help with the problem.
Connecting to Client osdev-ctrl1.cloud.csd.uwo.ca at 'redacted':9102
osdev-ctrl1-fd Version: 17.2.4 (21 Sep 2017) x86_64-redhat-linux-gnu redhat CentOS Linux release 7.4.1708 (Core)
Daemon started 13-Jun-18 15:40. Jobs: run=0 running=0.
Heap: heap=135,168 smbytes=35,949 max_bytes=38,762 bufs=68 max_bufs=97
Sizeof: boffset_t=8 size_t=8 debug=0 trace=0 bwlimit=0kB/s
bareos-dir (director) connected at: 13-Jun-18 16:02
No Jobs running.
====
Also does not seem to be a DNS issue - connected fine.
Connecting to Client testhost at *:9102
*
Job output -
Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume Session Id: 2
Volume Session Time: 1528918799
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Fatal Error
SD termination status: Waiting on FD
Termination: *** Backup Error ***
Many thanks, Joe
--
Jörg Steffens ***@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 630693-91
http://www.bareos.com Fax: +49 221 630693-10

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örg Steffens, P. Storz
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...