Hello all, Apologies if I've broken any ettiquete with my first post! In response to a security incident yesterday (unrelated to patching and bareos), I went through and applied all updates and upgraded several bareos clients to Debian 9 (from Debian 8).
The director is was already running Debian 9 and is now running bareos 18 (both director and FD - installed via apt from downloads.bareos.org/release/latest) and everything has continued working perfectly except one other client which I also updated to Debian 9... I've tried upgrading this suddenly-problematic client to bareos 18, and tried taking it back down to 17, and it behaves the same. No config file changes, I've checked everything I can think of (but may be overlooking the obvious) - the client was working and suddenly doesn't work - and as far as I can tell, the cause was upgrading from Debian 8 to 9... Am I going mad? I can only think (speculatively) that an OpenSSL package or something is broken. Output from a debug execution showing the issue on the FD side below. Director reports that the authorization key was rejected. Any help/suggestions would be greately appreciated! (Log below is after downgrading to bareos 17, which was the FD version which was working on Debian 8 - and continues to work on all other clients. Config is very simple - sanitised copy included below. Just to be thorough, I've included "dpkg -l" too.) --- (Actually - the logs are quite big. I've shared them here: https://ssl.plfc.org.uk/privatebin/?47c8fe9833b74c7c#RoTb+razdjxKOliCwPxjxCrYz8NvYxMDJbUchltnQ1o= ) -- 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/b52041b7-1bd8-4dec-bf81-62e83d139ea7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
