On Friday 17 July 2009 05:14:46 Dirk Bartley wrote: > I have an autochanger my machine at home > > from bat > > status slots > Automatically selected Storage: DDS4 > Connecting to Storage daemon DDS4 at workplay:9103 ... > Connecting to Storage daemon DDS4 at workplay:9103 ... > 3306 Issuing autochanger "slots" command. > Device "DDS4-Changer" has 8 slots. > Connecting to Storage daemon DDS4 at workplay:9103 ... > 3306 Issuing autochanger "list" command. > > 1*| | ? | ? | ? | > 2*| | ? | ? | ? | > 3*| | ? | ? | ? | > 4*| | ? | ? | ? | > 5*| | ? | ? | ? | > 6||||| > 7*| | ? | ? | ? | > 8*| | ? | ? | ? | > > > my guess is that's less than optimal?? > > I get about the same result in bat with none of the undesired behavior. > > I have a thought, would your situation require a window because of more > than one storage with an autochanger?? oops, looking below, I guess > not, automatically select LTO-Changer. Hrmmm Hrmmm.
Yes, in your case, there was no PROMPT message sent (get_cmd() in the core code). I suspect that if you add "Autochanger = yes" to your Storage resource in the editor, that it will then prompt you for the drive. > > does the autochanger have more than one drive?? Yes, but I don't think that the Director knows that. > Is bacula asking for > which drive and bat needs to list the drives in that autochanger? Well, what I said above was not quite true. Bacula does indeed ask the autochanger how many drives it has, and in my case, it gets the answer 2. To simulate it, you might temporarily add a second drive to your bacula-sd.conf Autochanger resource. As far as I know this command does not actually access the drive -- in any case, I always enter 0. I'll see if I can find some other cases of the use of PROMPT that might be more simple to test in your normal setup ... Thanks for looking at this. Best regards, Kern > > On Thu, 2009-07-16 at 22:10 +0200, Kern Sibbald wrote: > > Hello Dirk, > > > > As I mentioned some time ago, when I do a "status slots" in the bat > > command line and my storage device is defined to be an autochanger, in > > the ensuing communications between the director and bat, the director > > issues a: > > > > Enter autochanger drive[0]: > > > > and at that point, bat gets totally confused. Instead of doing a prompt, > > it starts up a new connection to the Director, which is useless, and all > > the rest of the output from the command is lost. > > > > The full debug output is: > > > > bat: bcomm/dircomm.cpp:246 conn 1 send: status slots > > bat: console/console.cpp:597 DisplaytoPrompt roxie-dir > > bat: bcomm/dircomm.cpp:321 conn 1 CMD BEGIN > > bat: bcomm/dircomm.cpp:292 conn 1 got: Automatically selected Storage: > > LTO-changer > > > > bat: bcomm/dircomm.cpp:292 conn 1 got: Enter autochanger drive[0]: > > bat: bcomm/dircomm.cpp:335 conn 1 PROMPT > > bat: console/console.cpp:609 endDisplaytoPrompt=-1 roxie-dir > > bat: mainwin.cpp:322 Exiting Wait State > > bat: bcomm/dircomm.cpp:446 m_notifier Enabling notifier: 1 roxie-dir > > bat: console/console.cpp:814 DirComm 2 About to Create and Connect > > roxie-dir bat: bcomm/dircomm.cpp:246 conn 2 send: .api 1 > > bat: console/console.cpp:597 DisplaytoPrompt roxie-dir > > bat: bcomm/dircomm.cpp:310 conn 2 CMD OK > > bat: bcomm/dircomm.cpp:329 conn 2 MAIN PROMPT > > bat: console/console.cpp:609 endDisplaytoPrompt=-1 roxie-dir > > bat: bcomm/dircomm.cpp:246 conn 2 send: . > > bat: bcomm/dircomm.cpp:321 conn 2 CMD BEGIN > > bat: bcomm/dircomm.cpp:310 conn 2 CMD OK > > bat: bcomm/dircomm.cpp:329 conn 2 MAIN PROMPT > > It had fixed occurances like the next line when I would incorrectly use > functions that did not require the use of the specific connection > already in use to communicate with the director. It looks like that is > happening again, but not being able to reproduce yet, I have not found > it. > > > bat: bcomm/dircomm.cpp:212 Returning TRUE from DirComm->connect_dir : 2 > > roxie-dir > > I wish I knew what the stack was right here on this line above. Can you > turn on connection debugging?? Looks like you probably already do. > There's to, commDebug and connDebug. > > > bat: console/console.cpp:820 DirComm 2 Connected roxie-dir > > bat: bcomm/dircomm.cpp:69 DirComm 0 terminating connections roxie-dir > > bat: bcomm/dircomm.cpp:69 DirComm 1 terminating connections roxie-dir > > bat: bcomm/dircomm.cpp:69 DirComm 2 terminating connections roxie-dir > > > > Notice, how just after the PROMPT it starts a second connection. > > > > We are about to release Bacula version 3.0.2, and I would really like to > > have this fixed. I believe that the same thing happens if there are > > multiple Storage devices defined and the user must select among them. > > I tried a "status storage" on a director that had multiple storages and > it came up with the dialog box just fine for me. Hrmm Hrmmmm. > > Unfortunately, not found yet. > > > Can you help point out to me what needs to be fixed to keep bat from > > opening a second connection? > > It's always an occurrence where I use a console overloaded function > without "int conn" where I should be using that overload. If I could > figure out how to reproduce, I'd be able to solve it rapidly. > > Will keep trying tomorrow. > > Dirk > > > Best regards, > > > > Kern ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
