Hi All Bacula Gurus :-)
I'm in need of your help.
I'm running Bacula server 2.0.3 on FreeBSD 6.1 p0. Have serveral nodes
(servers & clients) that are backed up via my Bacula server.
But now when I add new nodes to backup I get some very wired problems.
I have installed Bacula Client 2.0.3 on FreeBSD 6.3 p10 and I've used
bacula-fd.conf from already up and running nodes.
Added the new node in bacula-dir.conf on the Bacula server (have dubble
verified syntax and settings towards already running nodes) and get
following error messages when trying to run a backup.....
- - - - - >8 - - - - -
01-Feb 10:14 blues-dir: Start Backup JobId 9917,
Job=chilli.verkstad.net.2008-02-01_10.14.55
01-Feb 10:19 blues-fd JobId 9917: Warning: bsock.c:123 Could not connect
to Storage daemon on blues.verkstad.net:9103. ERR=Operation timed out
Retrying ...
01-Feb 10:24 blues-dir: chilli.verkstad.net.2008-02-01_10.14.55 Error:
bnet.c:270 Read error from Storage daemon:blues.verkstad.net:9103:
ERR=Broken pipe
01-Feb 10:26 blues-fd JobId 9917: Fatal error: Failed to connect to
Storage daemon: blues.verkstad.net:9103
01-Feb 10:24 blues-dir: chilli.verkstad.net.2008-02-01_10.14.55 Fatal
error: Socket error on Storage command: ERR=Broken pipe
01-Feb 10:24 blues-dir: Bacula 2.0.3 (06Mar07): 01-Feb-2008 10:24:44
- - - - - >8 - - - - -
There's no problem to cancel this job (9917) and run jobs for the
already configured nodes.
I did install bacula client 2.2.5 first (same problem with that vesion
as now) but downgraded to 2.0.3 as I run on all the working nodes.
Please, what have I missed...... ?
Many thanks in advance.
Patrik Usher
-------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
