-----Original Message-----
From: Gore, David W Sent: Monday, January 05, 2009 16:03
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] bb-ack
-----Original Message-----
From: Henrik Størner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: Monday, January 05, 2009 11:52
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] bb-ack
In
<user-8933222b8ee8@xymon.invalid
m> "Gore, David W" <user-3e5761c68b56@xymon.invalid> writes:
-----Original Message-----
From: Henrik St=C3=B8rner [mailto:user-ce4a2c883f75@xymon.invalid]=20
Sent: Tuesday, December 30, 2008 22:14
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] bb-ack
=20
In=20
<user-ad6711ad8037@xymon.invalid
m> "Gore, David W" <user-3e5761c68b56@xymon.invalid> writes:
=20
I am running Red Hat release 4 and the latest snapshot. I am > >> >also=20 running Apache 2.0.52. When I try to acknowledge an > >> >alert=20
it shows me=20
ALL the services that are alarming not just the alert I was=20
interested=20
in. Any idea what I can do to debug?
=20
That would usually mean that the cookie used by the
bb-ack=20 CGI to
determine what page or host you were looking at is=20
missing. Maybe
you have cookies disabled in your browser policy ?
=20
The cookies are not disabled. Viewing the cookies in
firefox I can see
= that the host cookie does NOT contain the hostname. It
does contain
the = hostname on a working server. =20
So I installed the last test release from xymon.com web
page. It also
= exhibits the same problem. I would guess that it is a
permission =
problem since I have to correct numerous files to get the
server and =
client to work properly.
Quite unlikely, the cookie is exchanged directly between the Xymon > server and your browser.
On the webpage where you view the status (just before going to the > ack- page), try doing a "View Source" (ctrl-U in Firefox). Near the > top you should see two lines like these:
<META HTTP-EQUIV="Set-Cookie" CONTENT="pagepath=mypage; path=/">
<META HTTP-EQUIV="Set-Cookie" CONTENT="host=; path=/"> (either the > 'pagepath' or the 'host' cookie should be set, not both).
Are these correct ?
No they are not correct. They match what I am seeing in the cookies:
<META HTTP-EQUIV="REFRESH" CONTENT="60"> <META HTTP-EQUIV="EXPIRES" CONTENT="Sat, 01 Jan 2001 00:00:00 GMT"> <META HTTP-EQUIV="Set-Cookie" CONTENT="pagepath=; path=/"> <META HTTP-EQUIV="Set-Cookie" CONTENT="host=; path=/"> <TITLE>yellow : Xymon - Status @ Mon Jan 05 15:44:42 2009</TITLE>
The EXPIRES date is sort of odd isn't it? Is that set by Xymon, you can see the Xymon Status date. We set our Xymon servers to GMT.
I did try to install 4.2.2 over top our test version but I get the same headers as above.
~David
There shouldn't be any file-permission issues with the final
4.2.2 release.
Regards,
Henrik