Hi,

I've upgraded to 3.0.3  from 3.0.2 a while ago and I'm facing serious problems 
with bacula-dir stability. 

Just after its start,  Director is able to perform any request I have (perform 
a backup, restore, reload etc.). But once I've got the task done, Director 
stops listening me - the second job is not starting when requested. Then 
bconsole stops, I have to exit ctrl+c, but reissuing bconsle and here typing 
status dir gives that the backup is running. 

The problem is that the backup is not running. Director keeps it almost fully 
silent. When I try to reload through bconsole, I'm experiencing Director going 
like zombie - cannot connect. Debugging gives only this:

atom-dir: bnet.c:670-0 who=client host=192.168.1.150 port=36131

What's interesting, when I leave the Director alone it works OK, it schedules 
backups and performs them. I had previously suspected that something is wrong 
with scheduler as on before this troubleshooting I couldn't even get the 
Director scheduling, but since few days it goes right.

This is the same issue as the guy here, but he hasn't found a clue:

http://www.mail-archive.com/bacula-users AT lists.sourceforge DOT 
net/msg38279.html

I've just moved backups and database, recompiled Bacula, recreated the 
database and started backups  but the same history goes. What this could be, 
anyone?

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users