Posted 17 March, 2017
While working with bareos backups, I got this error :
Fatal error: Bad response to Storage command: wanted 2000 OK storage , got 2902 Bad storage
I thought it would be related to the underlying filesystem but a bit further in the error message log a hidden tip was to be found :
client-123 JobId 63: Error: bsock_tcp.c:187 bnet_host2ipaddrs() for host "bareoshead" failed: ERR=Name or service not known
However since this happened first, I would expect bareos to stop there. It doesn’t. What’s happening ? Well bareos could connect to the client it knows but the server “bareoshead” is not known to the client. That is why it fails in this particular case. After fixing
/etc/hosts , I added this :
Next job ran successfully.
If you enjoyed this article, please consider buying me a Dr Pepper.
Fuel the beast!
Buy me a Dr Pepper