But I can say, using the webpage default method produces the same error
messages "Cookie not found" -- so I didn't think it would be my method of
acknowledging
--
Sean Clark
Sr. Engineer, Software
ATG Network Operations & Planning Integrated Regional OSS
<http://www.twcable.com/DepartmentOverview/AdvancedTechnologyGroup/ATG/NOP/
OSS/Network.aspx>
user-2db5fbcae9a7@xymon.invalid <mailto:user-2db5fbcae9a7@xymon.invalid> devaudio
<aim://devaudio> <mailto:user-2db5fbcae9a7@xymon.invalid>
Office: (XXX) XXX-XXXX cell: (XXX) XXX-XXXX
On 4/7/11 9:43 AM, "Clark, Sean" <user-2db5fbcae9a7@xymon.invalid> wrote:
$BB $BBPAGE \"xymondack $NUMBER $DELAY $MESSAGE\"";
From a script
Where $BB is
/sw/libexec/hobbit/client/bin]./bb --version Hobbit version 4.2.0
BBPAGE is my xymond display running 4.2.3
$NUMBER is the cookie, obtained by using that same hobbit client to run
"hobbitdboard
fields=hostname,testname,color,acktime,disabletime,cookie,ackmsg,dismsg,la
s
tchange"
$DELAY is typically 120, but setable
$MESSAGE is just text
--
Sean Clark
Sr. Engineer, Software
ATG Network Operations & Planning Integrated Regional OSS
<http://www.twcable.com/DepartmentOverview/AdvancedTechnologyGroup/ATG/NOP
/
OSS/Network.aspx>
user-2db5fbcae9a7@xymon.invalid <mailto:user-2db5fbcae9a7@xymon.invalid> devaudio
<aim://devaudio> <mailto:user-2db5fbcae9a7@xymon.invalid>
Office: (XXX) XXX-XXXX cell: (XXX) XXX-XXXX
On 4/7/11 9:36 AM, "user-ce4a2c883f75@xymon.invalid" <user-ce4a2c883f75@xymon.invalid> wrote:
On Thu, 7 Apr 2011 09:16:01 -0400, "Clark, Sean" <user-2db5fbcae9a7@xymon.invalid>
wrote:
I'm not expecting some sort of magic patch to fix this tomorrow, I am
just
looking for some direction to take
So far, I haven't even had an acknowledgement that anyone's read this,
other than people who have the same problem as me, whose prescribed
options are "fix the problem you can't ack faster."
I've seen your messages, but haven't had a chance to dig into the code to
see where the problem is.
I'll list things that I have changed from the stock xymon settings in
the
hopes that Henrik or someone else can say "if you change that, you need
to
change this or you will most likely have your shm and chk files
corrupted"
I don't see any config changes you've done that would explain this.
Every 4 days, almost exactly, I start losing the ability to acknowledge
some alerts.
As time progresses, it gets worse and worse at first it's random,
some
can be acknowledged, some can't
Then, more and more can not be acknowledged
2011-04-05 05:23:09 Cookie 115771 not found, dropping ack
2011-04-05 05:23:09 Cookie 54483 not found, dropping ack
How do you ack an event ? Are you using the "Acknowledge alert" webpage
with the "--no-pin" option (default), or is it ack via email or ... ?
Regards,
Henrik
This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject to
copyright belonging to Time Warner Cable. This E-mail is intended solely
for the use of the individual or entity to which it is addressed. If you
are not the intended recipient of this E-mail, you are hereby notified
that any dissemination, distribution, copying, or action taken in
relation to the contents of and attachments to this E-mail is strictly
prohibited and may be unlawful. If you have received this E-mail in
error, please notify the sender immediately and permanently delete the
original and any copy of this E-mail and any printout.
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.