Hi Bruno,

now I have the second bareos server which can't start my "noabckup" 
script in front of the backup:

25-Sep 04:32 galaxy-dir JobId 224: Start Backup JobId 224, 
Job=Week2_Backup_galaxy-fd.2016-09-25_04.01.00_07
25-Sep 04:33 galaxy-dir JobId 224: Using Device "USBStorage_hd2_data" to write.
25-Sep 04:33 galaxy-fd JobId 224: Fatal error: Error running program: 
/usr/local/sbin/bareos-nobackup /srv/samba. status=1: ERR=Child exited with 
code 1
25-Sep 04:34 galaxy-fd JobId 224: Fatal error: Failed to authenticate Storage 
daemon.
25-Sep 04:34 galaxy-dir JobId 224: Fatal error: Bad response to Storage 
command: wanted 2000 OK storage
, got 2902 Bad storage

25-Sep 04:34 galaxy-sd JobId 224: Fatal error: Authorization key rejected by 
File daemon .
Please see 
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#AuthorizationErrors
 for help.
25-Sep 04:34 galaxy-sd JobId 224: Fatal error: authenticate.c:175 Authorization 
problem: Two way security handshake failed with File daemon at client
25-Sep 04:34 galaxy-sd JobId 224: Fatal error: Unable to authenticate File 
daemon

Regards

Stefan

Am 24.09.2016 um 15:45 schrieb Bruno Friedmann:
> On samedi, 24 septembre 2016 13.39:45 h CEST Stefan Klatt wrote:
>> Hi,
>>
>> I have a little problem with bareos 16.3.1 (01Jul16).
>> File "/usr/local/sbin/bareos-nobackup" exists, has the appropriate
>> rights (750 and for testing 755) and worked till a few days without any
>> problem. After I updated to the actual version the problem persists.
>>
>> I got the following messages:
>>
>> **********************************************************
>>
>> 2016-09-24 01:27:03 ntsrv02-dir JobId 114: Start Backup JobId 114,
>> Job=Week1_Backup_ntsrv02-fd.2016-09-24_01.27.01_10
>>
>> 2016-09-24 01:27:28 ntsrv02-dir JobId 114: Using Device
>> "USBStorage_hd1_data" to write.
>>
>> 2016-09-24 01:27:58 ntsrv02-dir JobId 114: Warning: Unexpected Client
>> Job message: 2999 Authentication failed.
>>
>> 2016-09-24 01:27:58 ntsrv02-dir JobId 114: Error: getmsg.c:212 Malformed
>> message: Authorization key rejected by Director ntsrv02-dir.
>> Please see
>> http://doc.bareos.org/master/html/bareos-manual-main-reference.html#Authoriz
>> ationErrors for help.
>>
>> 2016-09-24 01:27:58 ntsrv02-dir JobId 114: Fatal error: Unable to
>> authenticate with File daemon at
>> "ntsrv02.steuerbuero-emmerich.intern:9102". Possible causes:
>> Passwords or names not the same or
>> TLS negotiation failed or
>> Maximum Concurrent Jobs exceeded on the FD or
>> FD networking messed up (restart daemon).
>> Please see
>> http://doc.bareos.org/master/html/bareos-manual-main-reference.html#Authoriz
>> ationErrors for help.
>>
>> 2016-09-24 01:27:58 ntsrv02-dir JobId 114: Fatal error: Authorization
>> key rejected by File Daemon ntsrv02-fd.
>> Please see
>> http://doc.bareos.org/master/html/bareos-manual-main-reference.html#Authoriz
>> ationErrors for help.
>>
>> **********************************************************
>>
>> If I remove the script "bareos-nobackup" from the fileset it works (I
>> don't know why).
>>
>> Why I get errors from the storage daemon if the file daemon has an error?
>>
>> Regards
>>
>> Stefan
> Did you kept dir and sd with same version.
> It is still mandatory that those components have the same version.
> I believe you got error from the storage because this one doesn't recognize 
> the client cookies that is transmitted by the director
>

-- 
*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.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to