FW: [hobbit] tooltips, current snapshot 15-Jan-08
Still hoping this could be fixed soon? Having to scroll the bb2 page for hosts with long descriptions like contact and vendor info is a pain. I still do not really understand why this is only a problem on the bb2 page.
~David
From: Gore, David W (David) [mailto:david.gore at verizonbusiness.com] Sent: Thursday, November 15, 2007 14:20 To: hobbit at hswn.dk Subject: RE: [hobbit] tooltips
In regards to the hobbit snapshot:
They say a picture is worth a thousand words. If the list server allows it, I have attached an image of my bb2.html page. bb2 is our primary view and, as you can see from the image, tooltips pushes all the hobbit columns out of the view to the right.
Tooltips are the text you see when you hover over items like the smiley's in hobbit? I suppose it has always worked well for the little smiley gif icons, just not so well for the bb2 host links where it seems to add the tooltip to the hostname rather than create floating text.
~David
From: Johann Eggers [mailto:Johann.Eggers at teleatlas.com] Sent: Thursday, November 15, 2007 13:11 To: hobbit at hswn.dk Subject: [hobbit] tooltips
Re: the tooltips issue:
Isn't it useful to make this an option whether they should be displayed on the bb2 page or not?
I really like the tooltips but I agree with David that they will clutter your bb2 page so that this page is not longer usable.
Johann
From: Gore, David W (David) [mailto:david.gore at verizonbusiness.com] Sent: Donnerstag, 15. November 2007 13:47 To: hobbit at hswn.dk Subject: RE: [hobbit] stale alerts
I am running 4.2.0 with the allinone patch. I do have a suspicion that external server side scripts could contribute to the stale alerts. In my case, specifically a script that ssh's to a remote host and executes a shell script on the remote host. It may also happen in conjunction with these errors in the logs, which someone else recently reported:
page.log.1:2007-11-05 16:20:53 hobbitd_alert: Got message 14425, expected 14424
As soon as the issue with tooltips is resolved, I will be moving our primary hobbit to the snapshot release.
The snapshot, seems much better, but with tooltips and host descriptions pushing our display to the far right of the screen we cannot use it right now.
~David
On Tue, Jan 15, 2008 at 10:52:37PM +0000, David Gore wrote:
Still hoping this could be fixed soon? Having to scroll the bb2 page for hosts with long descriptions like contact and vendor info is a pain. I still do not really understand why this is only a problem on the bb2 page.
Sorry this has taken much too long. The attached patch will make "--tooltips=always" (or =never, if you so prefer) work on the BB2 page also.
Goes on top of any recent snapshot.
Regards, Henrik
Henrik Stoerner wrote:
Sorry this has taken much too long. The attached patch will make "--tooltips=always" (or =never, if you so prefer) work on the BB2 page also.
Goes on top of any recent snapshot.
I applied this patch and use '--tooltips=never', but the issue still remains. Anyone else have success? We are using snapshot 4.3.0-0.20080103, which is older and might be the cause for the failure.
Tom
On Thu, Mar 27, 2008 at 08:59:41AM -0400, Tom Georgoulias wrote:
Henrik Stoerner wrote:
Sorry this has taken much too long. The attached patch will make "--tooltips=always" (or =never, if you so prefer) work on the BB2 page also. Goes on top of any recent snapshot.
I applied this patch and use '--tooltips=never', but the issue still remains. Anyone else have success? We are using snapshot 4.3.0-0.20080103, which is older and might be the cause for the failure.
Ok, then please refresh my memory: What commandline options do you use for bbgen, what pages end up having tooltips (i.e. the COMMENT text only shows up in a tooltip), and what pages end up having the COMMENT text next to the hostname ?
Regards, Henrik
Henrik Stoerner wrote:
On Thu, Mar 27, 2008 at 08:59:41AM -0400, Tom Georgoulias wrote:
Henrik Stoerner wrote:
Sorry this has taken much too long. The attached patch will make "--tooltips=always" (or =never, if you so prefer) work on the BB2 page also. Goes on top of any recent snapshot. I applied this patch and use '--tooltips=never', but the issue still remains. Anyone else have success? We are using snapshot 4.3.0-0.20080103, which is older and might be the cause for the failure.
Ok, then please refresh my memory: What commandline options do you use for bbgen, what pages end up having tooltips (i.e. the COMMENT text only shows up in a tooltip), and what pages end up having the COMMENT text next to the hostname ?
Here is my command line (others may have something different):
[bbdisplay] <snip> CMD bbgen $BBGENOPTS --report --tooltips=never --rss --rsslimit=red --nopropyellow=dbmaint
The info column page has the tooltips displayed the way I would expect them to.
The DESCR and COMMENT info is displayed next to the hostname on bb2.html.
If needed, I can send you a screenshot to help visualize.
Thanks, Tom
On Thu, Mar 27, 2008 at 11:37:53AM -0400, Tom Georgoulias wrote:
Here is my command line (others may have something different):
[bbdisplay] <snip> CMD bbgen $BBGENOPTS --report --tooltips=never --rss --rsslimit=red --nopropyellow=dbmaint
The info column page has the tooltips displayed the way I would expect them to.
The DESCR and COMMENT info is displayed next to the hostname on bb2.html.
If needed, I can send you a screenshot to help visualize.
Please do, I cannot figure out what you're seeing versus what you're expecting.
Regards, Henrik
Hi,
Henrik Stoerner wrote:
Sorry this has taken much too long. The attached patch will make "--tooltips=always" (or =never, if you so prefer) work on the BB2 page also.
I just applied the patch to the latest snapshot. The problem has been resolved. I start bbgen with "--tooltips=never" and they really disappered.
But, unfortunately, the problem with wrong msgs, ports, and files still persists. When I klick on the msgs icon of host ynode8, for example, I get the following output:
No entries in /var/log/messages
No entries in /var/log/messages
Full log /var/log/messages Mar 27 16:16:13 ynode6 kernel: ... Mar 27 16:20:02 ynode6 ... Mar 27 16:30:02 ynode6 ...
Full log /var/log/messages Cannot open logfile /var/log/messages : Permission denied
Full log /var/adm/messages
Full log /var/adm/messages Mar 27 16:18:03 ossun1 sshd... Mar 27 16:23:03 ossun1 sshd...
As you can see, the output is totally messed and contains messages from other hosts. Hobbit also suddenly complains that no port checks were defined, although the host never checked for ports.
-- Regards,
Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
On Thu, Mar 27, 2008 at 04:57:19PM +0100, Dirk Kastens wrote:
But, unfortunately, the problem with wrong msgs, ports, and files still persists. [...] the output is totally messed and contains messages from other hosts. Hobbit also suddenly complains that no port checks were defined, although the host never checked for ports.
I seem to recall that your first report mentioned that this started happening when you started using the BBWin client in centralized mode ?
A quick test for this would be to simply delete line 1920 of hobbitd/hobbitd_client.c (in the current snapshot) - the one that calls the bbwin parser:
handle_win32_bbwin_client(hostname, clientclass, ......If rebuilding hobbitd_client without that function makes the issue disappear, then that is where I should look.
Another thing you could try for me, please: Run the hobbitd_client module through the Valgrind memory checker - this is only possible if your Hobbit server is Intel-based, though. Some linux distros include the "valgrind" package, but if not then you can download it from valgrind.org
With valgrind installed, change hobbitlaunch.cfg (the [clientdata]
section), so the CMD setting becomes
CMD hobbitd_channel --channel=client --log=$BBSERVERLOGS/clientdata.log
valgrind --log-file=/tmp/hclient.log hobbitd_client
i.e. insert the "valgrind --log-file..." stuff right before
hobbitd_client.
When hobbitd_client now runs, valgrind will log memory access problems to a /tmp/hclient.log.PID file. It would be interesting to see if it catches anything.
Regards, Henrik
Hendrik,
I seem to recall that your first report mentioned that this started happening when you started using the BBWin client in centralized mode ?
That wasn't me. It started with one of the snapshots from February. I went back to a snapshot from last year and the problem disappeared.
When hobbitd_client now runs, valgrind will log memory access problems to a /tmp/hclient.log.PID file. It would be interesting to see if it catches anything.
The valgrind package is installed. Let's wait for some output...
-- Regards,
Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
Hi Dirk,
seems I have this problem also, which should make it easier to debug. I have an idea where the problem is - stay tuned ...
Henrik
On Fri, Mar 28, 2008 at 09:09:46AM +0100, Dirk Kastens wrote:
Hendrik,
I seem to recall that your first report mentioned that this started happening when you started using the BBWin client in centralized mode ?
That wasn't me. It started with one of the snapshots from February. I went back to a snapshot from last year and the problem disappeared.
When hobbitd_client now runs, valgrind will log memory access problems to a /tmp/hclient.log.PID file. It would be interesting to see if it catches anything.
The valgrind package is installed. Let's wait for some output...
On Thu, Mar 27, 2008 at 04:57:19PM +0100, Dirk Kastens wrote:
But, unfortunately, the problem with wrong msgs, ports, and files still persists. [...] As you can see, the output is totally messed and contains messages from other hosts.
I just committed a patch that should fix this, it is in the snapshot available now at http://www.hswn.dk/beta/
Let me know if it is still a problem.
Regards, Henrik
Henrik,
That looks fantastic! I had actually spent way too much time on this and had reduced my bb-hosts from 1800 lines to a dozen lines hoping to isolate the problem, in addition to turning down all the checks in hobbit-clients.cfg and client-local.cfg.
If you were wondering, the msgs, ports, and files problems were what were causing those repeated (two at a time) cores of hobbitd_client, and why we saw the valgrind output all over the place. There have not been any cores since I started using the current snapshot. Although, I only have a fraction of my hosts running, there have been no cores for more than 8 hours.
I am going to start turning up the full load of hosts.
David Gore (v965-3670) Network Management Systems (NMS) IMPACT Transport Team Lead - SCSA, SCNA Page: 1-800-PAG-eMCI pin 1406090 Vnet: 965-3676
-----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Saturday, March 29, 2008 07:15 To: hobbit at hswn.dk Subject: Re: FW: [hobbit] tooltips, current snapshot 15-Jan-08
On Thu, Mar 27, 2008 at 04:57:19PM +0100, Dirk Kastens wrote:
But, unfortunately, the problem with wrong msgs, ports, and files still persists. [...] As you can see, the output is totally messed and contains messages from other hosts.
I just committed a patch that should fix this, it is in the snapshot available now at http://www.hswn.dk/beta/
Let me know if it is still a problem.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Hi Henrik,
I just committed a patch that should fix this, it is in the snapshot available now at http://www.hswn.dk/beta/
Let me know if it is still a problem.
Just installed the latest snapshot. The problem disappeared :-) Thanks very much for the support.
-- Regards,
Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
participants (4)
-
david.gore＠verizonbusiness.com
-
Dirk.Kastens＠uni-osnabrueck.de
-
henrik＠hswn.dk
-
tomg＠mcclatchyinteractive.com