[Xymon] Acknowledge issue continues with xymon 4.3.2

[Clark, Sean]

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'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"

In xymonserver.cfg

MAXMSG_STATUS="1036118"
MAXMSG_CLIENT="1036118"
MAXMSG_DATA="1036118"
MAXMSG_NOTES="1036118"

MAXLINE="1036118"


In tasks.cfg:

History disabled
Xymongen disabled

[all others are in their 'default' state, I.e. Proxy disabled, xymond
enabled]


I have 78 rules in alerts.cfg spread across 8,565 hosts.
I've added 14 graphing items in graphs.cfg


It's compile for i386 Linux

Previously the binaries were stripped because I installed them via the
spec file from the developer's list.

I built the binaries and did a make install instead so they are no longer
stripped


I do not get a core file for failing to acknowledge. Eventually no events
can be acknowledged at all, and if it gets to that point, the only way to
restart xymon is to remove the .chk files [it seems to tolerate 6-20 items
corrupted, but hundreds it will fail to start]




I am just looking for guidance, or some thing to try - please let me know











On 4/5/11 9:00 AM, "Clark, Sean" <sean.clark at twcable.com> wrote:

>
>
>I have xymon 4.3.2 installed now
>
>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
>
>New alerts, Existing alerts that were already acknowledged, it doesn't
>matter
>
>This is a fairly impacting issue, and others on the list have said they
>have this same problem
>
>
>All I have is that find_cookie in lib/rbt.c is not finding the cookie,
>despite it being visible in the hobbitdboard
>
>
>2011-04-05 05:23:09 Cookie 115771 not found, dropping ack
>2011-04-05 05:23:09 Cookie 54483 not found, dropping ack
>2011-04-05 05:23:09 Cookie 47469 not found, dropping ack
>2011-04-05 06:38:55 Cookie 86204 not found, dropping ack
>2011-04-05 06:41:37 Cookie 86204 not found, dropping ack
>
>
>This is what my logs start filling up with.
>
>
>Can anyone on this list point me to at least some starting point to try
>and solve this? It's seriously impacting my xymon implementation
>
>--
>
>
>________________________________
>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.
>_______________________________________________
>Xymon mailing list
>Xymon at xymon.com
>http://lists.xymon.com/mailman/listinfo/xymon


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.