Spurious error during authorization

[Aidan Furlan]

Binary package hint: bacula

I recently changed my bacula setup and got the following after running a job:

01-Jul 22:10 simba-fd JobId 76: Fatal error: Authorization key rejected by Storage daemon.
Please see http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors for help.
01-Jul 22:10 simba-fd JobId 76: Fatal error: Failed to authenticate Storage daemon.

I read the FAQ and checked and re-checked all the passwords in all conf files and could not find the issue. I then discovered it was not a password issue at all but a firewall issue - the File Daemon couldn't send data to the Storage Daemon which was being interpreted as a authorization key rejection. When I opened port 9103 to the Storage Daemon, it immediately started working.

[Chuck Short (zulcss)]

I dont think this is a bug per say, its an setup issue on your end.

chuck

[Aidan Furlan (aidan-epochlabs)]

I understand that port 9103 being blocked is a setup issue. What I'm suggesting as a bug is the error message "Authorization key rejected by Storage daemon" when no data is transmitted between the File Daemon and the Storage Daemon. This message was misleading in this case because the authorization key was not actually being rejected.

[Aidan Furlan (aidan-epochlabs)]

Here is another user who experienced the same issue:

http://<email address hidden>/msg17051.html

Like me this user found that passwords were not the problem, it was a misconfiguration at the networking level causing this error.

The simple fix would be to update the error message to reflect the fact that networking issues as well as wrong passwords can throw this error. Alternatively, testing for a connection between the SD and FD in authenticate.c prior to the cram_md5 tests would allow a distinction between the two.