I'm installing bareos and have it working with a variety of Linux and FreeBSD machines.However, installation for Windows has been very frustrating.
Here is a sample of the message: 13-Dec 06:35 bareos-dir JobId 0: Fatal error: Authorization key rejected by File Daemon tesla-fd. Please see http://doc.bareos.org/master/html/bareos-manual-main-reference.html#AuthorizationErrors for help. 13-Dec 06:35 bareos-dir JobId 0: Fatal error: Unable to authenticate with File daemon at "tesla.home.rcousins.com: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#AuthorizationErrors for help. I've tried using the GUI on install. I've tried using the create command in the console. I've tried a variety of passwords with no change in output. I can connect to the windows daemon from the director's machine using telnet to 9102. I've been editing the conf files on windows, then restarting the service. (Is this the proper way to make the Windows FD notice the config files have changed?) (It seems to me that the error message should indicate the point of failure in greater detail. Failure to connect via TCP/IP and authentication errors seem to give the same message.) I recall that there was an issue with newer windows clients on Bacula. Does it apply here? Anyway, I'd love it if someone could provide a systematic way for me to debug what I'm doing wrong. -- 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.
