[Bacula-users] Connection problems after moving director to another server
2008-05-28 09:53:29
Hi
I moved my bacula setup with all files needed from one server to
another (Suse 10.2 to Suse 10.3).
Now when I try to run a job from bconsole to backup data from a remote
machine I get authorization erroes:
The status for my components are
Storage daemon:
Backup Job SoloProdBackup.2008-05-28_15.36.27 waiting for Client connection.
Writing: Incremental Backup job SoloProdBackup JobId=2536 Volume=""
pool="SoloProd" device=""Directory_soloprod" (/mnt/filestorage/soloprod)"
Files=0 Bytes=0 Bytes/sec=0
FDSocket closed
Client:
JobId 2536 Job SoloProdBackup.2008-05-28_15.36.27 is running.
Unknown Type Job started: 28-May-08 15:36
Files=0 Bytes=0 Bytes/sec=0
Files Examined=0
SDReadSeqNo=1 fd=5
Finally it give up with a message:
28-May 15:32 soloprod-fd: SoloProdBackup.2008-05-28_15.22.31 Fatal
error: Authorization key rejected by Storage daemon.
Please see http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors
for help.
28-May 15:32 soloprod-fd: SoloProdBackup.2008-05-28_15.22.31 Fatal
error: Failed to authenticate Storage daemon.
28-May 15:32 file-server-dir: SoloProdBackup.2008-05-28_15.22.31 Fatal
error: Socket error on Storage command: ERR=No data available
28-May 15:32 file-server-dir: SoloProdBackup.2008-05-28_15.22.31
Error: Bacula 1.38.11 (28Jun06): 28-May-2008 15:32:44
What can be the reason for this FD - SD connection problem?
All the binaries, configuration files and libraries have been copied
from one machine to another.
ToMasz
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Bacula-users] Connection problems after moving director to another server,
Tomasz Moczadłowski <=
|
|
|