Hallo Stefan, what about the following log line?
10-Nov 22:08 bareos-dir JobId 51: Fatal error: Network error with FD during
Backup: ERR=Keine Route zum Zielrechner
The notebook loose the network connection to the bareos director. Probably
power saving?
Regards
Stefan
Am 10.11.2017 um 22:36 schrieb Stefan Harbich:
> Am Freitag, 10. November 2017 21:41:06 UTC+1 schrieb Stefan Harbich:
>> Hello my dears,
>> everything works fine after updating to version 17.2.
> Hello my dears,
> the script works but the job stops after 15 minutes. I have included the
> script in the file "/etc/bareos/bareos-dir.d/job/backup-nmanwme01-fd.conf" as
> follows:
>
> Hello my dears,
> the script works but the job stops after 15 minutes. I have included the
> script in the file "/etc/bareos/bareos-dir.d/job/backup-nmanwme01-fd.conf" as
> follows:
>
> Job {
> Name = "backup-nmanwme01-fd"
> JobDefs = "backup-nmanwme01"
> Client = "nmanwme01-fd"
>
> RunScript {
> RunsWhen = Before
> RunsOnClient = no
> Fail Job On Error = yes
> Command = "/usr/local/bin/triggerjob.py -d --password
> ........mQMZshcuQg........ttpGikVi84........ bareos.intern.harnet.de"
> }
> }
>
> But it stops with the following error message:
>
> ...
> 10-Nov 21:53 bareos-dir JobId 51: BeforeJob: DEBUG lowlevel.recv_submsg:
> submsg len: 218
> 10-Nov 21:53 bareos-dir JobId 51: BeforeJob: DEBUG lowlevel.__get_header:
> remaining header len: 4
> 10-Nov 21:53 bareos-dir JobId 51: BeforeJob: DEBUG lowlevel.__set_status:
> Server ready and waiting (-18)
> 10-Nov 21:53 bareos-dir JobId 51: BeforeJob: backup-nmanwme01-fd: skipped,
> recent backups available (2017-11-10 21:53:09: jobid=51, level=I, status=R)
> 10-Nov 21:53 bareos-dir JobId 51: Start Backup JobId 51,
> Job=backup-nmanwme01-fd.2017-11-10_21.53.07_43
> 10-Nov 21:53 bareos-dir JobId 51: Using Device "FileStorage" to write.
> 10-Nov 21:53 bareos-dir JobId 51: Using Client Initiated Connection
> (nmanwme01-fd).
> 10-Nov 22:08 bareos-dir JobId 51: Fatal error: FD gave bad response to JobId
> command: Keine Route zum Zielrechner
> 10-Nov 22:08 bareos-dir JobId 51: Fatal error: Network error with FD during
> Backup: ERR=Keine Route zum Zielrechner
> 10-Nov 22:08 bareos-dir JobId 51: Fatal error: No Job status returned from FD.
> 10-Nov 22:08 bareos-dir JobId 51: Error: Bareos bareos-dir 17.2.3 (14Aug17):
> Build OS: x86_64-pc-linux-gnu debian Debian GNU/Linux 8.0
> (jessie)
> JobId: 51
> Job: backup-nmanwme01-fd.2017-11-10_21.53.07_43
> Backup Level: Incremental, since=2017-11-10 21:49:11
> Client: "nmanwme01-fd" 16.2.4 (01Jul16)
> x86_64-pc-linux-gnu,ubuntu,Ubuntu 16.04 LTS,xUbuntu_16.04,x86_64
> FileSet: "LinuxAll" 2017-11-04 04:00:00
> Pool: "Incremental" (From command line)
> Catalog: "MyCatalog" (From Client resource)
> Storage: "File" (From Job resource)
> Scheduled time: 10-Nov-2017 21:53:07
> ...
>
> Do you have an idea what I can do that the job does not break off? My
> notebook is not always connected to the LAN.
>
> Greetings from Stefan Harbich
>
--
*CaC, Computer and Communication*
Inhaber Stefan Klatt
End-2-End Senior Network Consultant
Triftstrasse 9
60528 Frankfurt
Germany
USt-IdNr.: DE260461592
Tel.: +49-(0)172-6807809
Tel.: +49-(0)69-67808-900
Fax: +49-(0)69-67808-837
Email: [email protected]
Profil: http://www.cac-netzwerk.de/profil
--
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 [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
