Re: [Bacula-users] [Bacula-devel] Mysterious Director console connection failures

[Martin S. <ma...@li...>]

>>>>> On Wed, 07 Mar 2012 09:58:48 -0500, Phil Stracchino said:
> 
> OK, this is getting more and more peculiar as I study it more.  Adding
> bacula-devel list.
> 
> To briefly recap the initial statement of the problem, I've been
> experiencing a problem in which, after a number of successful
> connections, console->Director connection authentication begins
> repeatedly failing.  Everything else seems to continue to work normally.
>  The typical behavior is that after manually starting two or three jobs
> using BAT, I can no longer connect to the Director either with BAT or
> with bconsole, but everything else continues to function normally and
> the scheduled jobs run normally.  After the pending manually-scheduled
> jobs complete, I can connect again.
> 
> 
> 
> On the theory that network bandwidth may be somehow involved, I tried
> scheduling several jobs 15 minutes ahead of time, to see if I could get
> more jobs running if I scheduled them all before any started.
> 
> Starting at about 0915, schedule job 1 for 0925.  No problem.
> Schedule Job 2 for 0925.  No problem.
> Schedule job 3 for 0925.  No problem.
> At about 0918, try to schedule job 4 for 0925.  None of the new jobs has
> yet started.  No go; neither bat nor bconsole can connect.
> 
> 
> This is what the trace logged as I tried to connect with bconsole:
> 
> babylon4-dir: bnet.c:708-0 who=client host=10.24.32.10 port=36131
> babylon4-dir: job.c:1331-0 wstorage=babylon5-sd
> babylon4-dir: job.c:1340-0 wstore=babylon5-sd where=Pool resource
> babylon4-dir: job.c:1031-0 JobId=0 created
> Job=-Console-.2012-03-07_09.19.16_37
> babylon4-dir: cram-md5.c:72-0 send: auth cram-md5
> <1723850907.1331129956@babylon4-dir> ssl=0
> babylon4-dir: cram-md5.c:131-0 cram-get received: auth cram-md5
> <85736557.1331129966@bat> ssl=0
> babylon4-dir: cram-md5.c:150-0 sending resp to challenge:
> 25Q2B+IdJ/UKI/+p6++vkC
> babylon4-dir: ua_dotcmds.c:164-0 Cmd: .api 1
> babylon4-dir: ua_dotcmds.c:164-0 Cmd: .levels Backup
> babylon4-dir: bnet.c:708-0 who=client host=10.24.32.10 port=36131
> babylon4-dir: bnet.c:708-0 who=client host=10.24.32.14 port=36131

That looks like bat, not bconsole, so I think you got the wrong output.

Also, next time it starts failing, run bconsole -d 100 while the Director is
running with setdebug, so the outputs of both sides can be compared.

__Martin