Op 20120307 om 21:36 schreef Kern Sibbald: > On 03/07/2012 06:54 PM, Martin Simmons wrote: > >>>>>> On Wed, 07 Mar 2012 09:58:48 -0500, Phil Stracchino said:
> >> > >> > >> 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 > > > > Hello, > ~ In looking at the output above, I have a similar comment to Martin > about bat and bconsole. First, you should understand that currently > the Director only has a concept of a *single* console. When you > run with bat, it puts the console in gui mode, and so if you are running > any bconsoles at the same time and you just happen to get some output, > you will probably get stuff destined for bat, which will completely confuse > bconsole. > > Moral of the story. Don't run multiple bconsoles if possible because you > probably will get output mixed between them, and above all don't run > bconsole at the same time as bat or they both will probably get confused > particularly bconsole. bconsole won't have any idea how to handle "signals" > destined for bat. Oops. I have default a bconsole open in my screen[1] session. And now I know that it might grab / get data from another bconsole ... If I recall correct, I keep the bconsole session open to capture messages. Otherwise I get loads of job messages on opening a bconsole. That is with version 2.4.4 >From another posting: } Someone (not me) added Maximum Console Connections, which defaults } to 20, but I am not 100% sure how it interacts with Maximum Concurrent } Jobs. Before Maximum Console Connections, everything was lumped int } Maximum Concurrent Jobs. What does that mean? Is it saying: "Multiple console connections is work in progress" ? Cheers Geert Stappers Footnote: [1] Terminal multiplexer, http://en.wikipedia.org/wiki/GNU_Screen ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
