Am Mittwoch, 10. Juli 2019 01:17:36 UTC+2 schrieb Stefan Klatt:
> Hi Cookie,
> 
>     
> 
>     
> Am 09.07.2019 um 21:37 schrieb
>       Cookiefamily:
> 
>     
>     
>       Hello,
> I am getting weird issues with two of my clients. The TLS connection does 
> start up and it backups the client, but after the backup finished, the TLS 
> connection doesn't close properly and the backup aborts. 
> The director output can be found here: 
> https://gist.github.com/MiningPickaxe/5a501f4a01785f5f0fab9727c2a7d395 
> 
> I can't really figure out why the initiation of the connection works, but the 
> closing breaks?
> Could someone give me a guiding hand here?
> 
> 
> 
>     
>     What about this error?
> 
>     
> 
>     09-Jul 19:23 test01-fd JobId 132: Error: Runscript: ClientAfterJob
>     returned non-zero status=208. ERR=No such file or directory
> 
>     
> 
>     Probably you need only to remark the ClientAfterJob definition at
>     your configuration to test this?
> 
>     
> 
>     Regards,
> 
>     
> 
>     Stefan
> 
>     
> 
>     
> -- 
> 
>       CaC, Computer and Communication
> 
>       Inhaber Stefan Klatt
> 
>       End-2-End Senior Security Consultant
> 
>       CISSP / CEH / CISM / ISO27001 Lead Implementer / TOGAF9 /
> 
>       VdS-anerkannter Berater für Cyber-Security
> 
>       Badges: https://www.youracclaim.com/users/stefan-klatt
> 
>       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

Thank you for the answer, this also happened on a machine that didn't have the 
script enabled. So that shouldn't be the issue... But without touching any of 
the configs or restarting the dir/fd it magically did the backup the next day 
without issues.
I did have this issue on a different VM before as well, but I completly wiped 
that machine as a troubleshooting measure and that solved the issue.

But only seems to happen with relativly new clients, the first few backups 
work, then I get the TLS error and after a while magic happens and everything 
goes back to working as intended.

So I guess this topic could be considered closed now, I'll see if I can 
reproduce that error when I add the next client in a few days.

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/09757421-a059-469e-8bd5-cb7bebfe33aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to