Sound like something to do with the port forwarding to me. From shell on
client1 or client2 can you telnet to client3 on port 9103? If not
something screwey is going on with your port forwarding. You could alwas
turn on strace.... 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Johan
van Vliet
Sent: 30 October 2007 15:00
To: bacula-users@lists.sourceforge.net
Subject: [Bacula-users] Hanging after starting job and executing status


Hi,

I run a small site with 3 clients. Client 3 also trippled as director
and storage. Like this:

[CLIENT1]--+
           +--[INTERNET]--[CLIENT3/DIR/STORAGE]
[CLIENT2]--+


Client 1 and client 2 are Slackware Linux and client 3 is FreeBSD.

Because I ren out of diskspace I moved the storage to another (4th
machine; also FreeBSD). I also (stupid I know) upgraded from 2.2.4 to
2.2.5: 

[CLIENT1]--+
           +--[INTERNET]--[CLIENT3/DIR]--[STORAGE]
[CLIENT2]--+

Bacause I've only one public IP address I also installed portfwd on
client 3 to forward 9103 from client 3 to storage.

Sofar so good.

As a first test I backup'd client 3. This worked.! Then I tried to
backup client 1 and it stopped half way on /dev/cciss/c0...something....
Second attempt it stopped one another file. etc. 

So I tried the client 2. Same result. 

Long story short; I can reproduce the hanging when I run a backup of the
remote clients (1 or 2) and then type "status storage" in bconsole. Like
this:
*run
A job name must be specified.
The defined Job resources are:
     1: client1-job
     2: client2-job
     3: client3-job
     4: BackupCatalog
     5: RestoreFiles
Select Job resource (1-5): 3
Run Backup job
JobName:  client2-job
Level:    Incremental
Client:   client2-fd
FileSet:  client2 Set
Pool:     Default (From Job resource)
Storage:  File (From Job resource)
When:     2007-10-30 13:24:01
Priority: 15
OK to run? (yes/mod/no): yes
Job queued. JobId=16

Note the "messages" here show me that the backup is starting. Also I can
see it status running in te jobs list; as soon as I type:

*status storage
Automatically selected Storage: File
Connecting to Storage daemon File at client3:9103

it hangs and and doesn't return to the * prompt.

The "bacula-fd -f -d100 -c <config>" and "bacula-sd -f -d100 -c
<config>" 
show output until the "status restore".

The only way to get the prompt back is by killing the bacula-sd.

Any insights are welcome about what can cause this.

J.

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to