From: <bac...@li...> - 2006-04-23 08:27:01
|
A BUGNOTE has been added to this bug. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000482 ====================================================================== Reported By: ArnoL Assigned To: ====================================================================== Project: bacula Bug ID: 482 Category: wx-console Reproducibility: always Severity: tweak Priority: normal Status: new ====================================================================== Date Submitted: 11-18-2005 12:35 PST Last Modified: 04-23-2006 01:26 PDT ====================================================================== Summary: wx-console (win32) status line / command help defective Description: Still /again I find that the command completion help in wx-console doesn't work an more. wx-console under windows, version 1.38.1 (6. Nov. 2005), doesn't show the possible commands, but rather some sort of raw director output. Usually, I see ": Termination: Admin OK". See attached image file (png format, 1.6kB) with a screenshot detail. ====================================================================== ---------------------------------------------------------------------- nboichat - 11-19-2005 05:10 PST ---------------------------------------------------------------------- Really strange.. I thought I had fixed it. Could you please copy the console content just after wx-console succefully connects to the director ? (From "Welcome to bacula wx-console ...!" to the end) ---------------------------------------------------------------------- ArnoL - 11-19-2005 12:24 PST ---------------------------------------------------------------------- I have the output attached as a text file. Note that you will see todays job reports with some interesting errors :-) but these shouldn't matter. You seem to be on the right track, though - your note inspired me to disconnect wx-console, quit the program, and start a new instance. This time without initial messages queued from the DIR, and the status line works as expected. I add that output as well. It's shorter, too, obviously. ---------------------------------------------------------------------- shadrack - 04-20-2006 00:19 PDT ---------------------------------------------------------------------- This appears to have been fixed some time prior to 1.38.4. It works for me anyway... ---------------------------------------------------------------------- ArnoL - 04-20-2006 00:54 PDT ---------------------------------------------------------------------- It doesn't here... I have the following running now: goblin-dir Version: 1.38.6 (28 March 2006) bacula wx-console 1.38.6 (28 March 2006) The line that is shown when I start a command is probably the last job status report line from the last job finished. I get the following at the end of the messages after starting wx-console: **** Pasted from wx-console **** The last job that was finished reports this: 20-Apr 09:03 goblin-dir: Bacula 1.38.6 (28Mar06): 20-Apr-2006 09:03:38 JobId: 5804 Job: BeowulfStd.2006-04-20_08.20.01 Backup Level: Incremental, since=2006-04-19 08:20:05 Client: "beowulf-fd" Windows XP,MVS,NT 5.1.2600 FileSet: "WindowsXP-C" 2005-01-12 10:49:17 Pool: "Incr" Storage: "HPDAT" Scheduled time: 20-Apr-2006 08:20:01 Start time: 20-Apr-2006 08:20:03 End time: 20-Apr-2006 09:03:38 Elapsed time: 43 mins 35 secs Priority: 10 FD Files Written: 738 SD Files Written: 738 FD Bytes Written: 770,138,393 (770.1 MB) SD Bytes Written: 770,285,623 (770.2 MB) Rate: 294.5 KB/s Software Compression: None Volume name(s): DAT-120-0025 Volume Session Id: 1 Volume Session Time: 1145511138 Last Volume Bytes: 5,393,525,617 (5.393 GB) Non-fatal FD errors: 2 SD Errors: 0 FD termination status: OK SD termination status: OK Termination: Backup OK -- with warnings **** This might be the text that goes into the status line **** The following text is also in the messages buffer. 20-Apr 09:03 goblin-dir: Begin pruning Jobs. 20-Apr 09:03 goblin-dir: No Jobs found to prune. 20-Apr 09:03 goblin-dir: Begin pruning Files. 20-Apr 09:03 goblin-dir: No Files found to prune. 20-Apr 09:03 goblin-dir: End auto prune. 20-Apr 09:10 goblin-dir: RunBefore: ping: unknown host drache 20-Apr 09:10 goblin-dir: RunBefore: Host drache is DOWN! 20-Apr 09:10 goblin-dir: DracheStd.2006-04-20_08.20.00 Fatal error: RunBeforeJob error: ERR=Child exited with code 1 20-Apr 09:10 goblin-dir: Rescheduled Job DracheStd.2006-04-20_08.20.00 at 20-Apr-2006 09:10 to re-run in 600 seconds. 20-Apr 09:10 goblin-dir: Job DracheStd.2006-04-20_08.20.00 waiting 600 seconds for scheduled start time. 20-Apr 09:20 goblin-dir: RunBefore: ping: unknown host drache 20-Apr 09:20 goblin-dir: RunBefore: Host drache is DOWN! 20-Apr 09:20 goblin-dir: DracheStd.2006-04-20_08.20.00 Fatal error: RunBeforeJob error: ERR=Child exited with code 1 20-Apr 09:20 goblin-dir: Rescheduled Job DracheStd.2006-04-20_08.20.00 at 20-Apr-2006 09:20 to re-run in 600 seconds. 20-Apr 09:20 goblin-dir: Job DracheStd.2006-04-20_08.20.00 waiting 600 seconds for scheduled start time. 20-Apr 09:30 goblin-dir: RunBefore: ping: unknown host drache 20-Apr 09:30 goblin-dir: RunBefore: Host drache is DOWN! 20-Apr 09:30 goblin-dir: DracheStd.2006-04-20_08.20.00 Fatal error: RunBeforeJob error: ERR=Child exited with code 1 20-Apr 09:30 goblin-dir: Rescheduled Job DracheStd.2006-04-20_08.20.00 at 20-Apr-2006 09:30 to re-run in 600 seconds. 20-Apr 09:30 goblin-dir: Job DracheStd.2006-04-20_08.20.00 waiting 600 seconds for scheduled start time. 20-Apr 09:40 goblin-sd: Please mount Volume "QIC-525-0007" on Storage Device "Wangtek 6525" (/dev/nst0) for Job BackupMail.2006-04-20_08.30.00 20-Apr 09:40 goblin-dir: RunBefore: Host drache is up. 20-Apr 09:40 goblin-dir: Start Backup JobId 5803, Job=DracheStd.2006-04-20_08.20.00 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Setting power save mode. 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Power save settings are now: 20-Apr 09:40 drache-fd: ClientRunBeforeJob: 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Feldbeschreibung Wert 20-Apr 09:40 drache-fd: ClientRunBeforeJob: ---------------- ----- 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Name Dauerbetrieb 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Numerischer Kennzeichner 3 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Monitor ausschalten (Netzbetrieb) Nach 20 Minute(n) 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Monitor ausschalten (Batteriebetrieb) Nach 15 Minute(n) 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Festplatten ausschalten (Netzbetrieb) Nie 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Festplatten ausschalten (Batteriebetrieb) Nach 30 Minute(n) 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Systemstandby (Netzbetrieb) Nie 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Systemstandby (Batteriebetrieb) Nie 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Systemruhezustand (Netzbetrieb) Nie 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Systemruhezustand (Batteriebetrieb) Nie 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Prozessordrosselung (Netzbetrieb) NONE 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Prozessordrosselung (Batteriebetrieb) NONE 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Saving registry... 20-Apr 09:40 drache-fd: ClientRunBeforeJob: Registry done. Now saving systemstate according to ntbackup **** This is the end of the queued messages and the end of the **** message output after startup of wx-console. I will upload a scrren shot fragment of the behaviour of wx-console right after startup when I pressed the kex "s". ---------------------------------------------------------------------- ArnoL - 04-20-2006 00:57 PDT ---------------------------------------------------------------------- The screenshot with the current output is attached. Again, after shutting down wx-console and starting it again, without messages queued, the command completion suggestions work as expected. ---------------------------------------------------------------------- shadrack - 04-21-2006 19:02 PDT ---------------------------------------------------------------------- I stand corrected. I see the same behavior provided there are console messages waiting when wx-console starts. I suspect this has something to do with bacula displaying messages immediately after connecting rather then waiting for the user to issue the 'messages' command as it did before. You'll notice the first thing wx-console does is issue the '.help' command. I suspect it's parsing the response into an internal command table from which it generates the command hints, and the console messages the director is sending out unprompted are confusing the code that's expecting only the response to the .help command. ---------------------------------------------------------------------- kern - 04-23-2006 01:26 PDT ---------------------------------------------------------------------- Yes, I get the same thing if any pending messages are printed when you login. If there are no messages it works. I'm not spending any time on this yet, because I am hoping that it will be corrected by moving from wxWidgets 2.4 to wxWidgets 2.6. We are currently using 2.4 on Win32 and 2.6 on Linux, where there is no problem. I *plan* to move to 2.6 before the next major release providing there are no major difficulties doing so. Bug History Date Modified Username Field Change ====================================================================== 11-18-05 12:35 ArnoL New Bug 11-18-05 12:35 ArnoL File Added: wx-console-win32-statusline.PNG 11-19-05 05:10 nboichat Bugnote Added: 0001305 11-19-05 12:23 ArnoL File Added: wx-console-win32-log1.txt 11-19-05 12:24 ArnoL Bugnote Added: 0001306 11-19-05 12:24 ArnoL File Added: wx-console-win32-log2.txt 04-20-06 00:19 shadrack Bugnote Added: 0001642 04-20-06 00:54 ArnoL Bugnote Added: 0001643 04-20-06 00:55 ArnoL File Added: bacula-wx-console-statusline-2.PNG 04-20-06 00:57 ArnoL Bugnote Added: 0001644 04-21-06 19:02 shadrack Bugnote Added: 0001656 04-23-06 01:26 kern Bugnote Added: 0001658 ====================================================================== |