If you're seeing a crash alert ("Signal received", etc) and it's purple, it was just the one-time note that something internal to xymon crashed. (That, of course, isn't supposed to happen, but... :/ )

xymond_rrd normally doesn't send in a test about itself (none of the processors launched via xymond_channel do by default, only the xymonlaunch-ed daemons and run-once commands), so it won't clear even if the system is running fine now.

Also, I'd have to check, but I believe re-enabling of disables doesn't take effect right away -- there's a part that may not update until the next status message is received for it.

In either case, just drop the now-spurious "xymond_rrd" test using something like:

./xymon 0.0.0.0 "drop xymonems xymond_rrd"

HTH,

-jc

On Tue, October 21, 2014 6:57 am, Neal, Jonathan W wrote:

Anyone got any ideas about this? The test does not show as disabled on the enable/disable page, but is still blue and doesn’t seem to update at all. No xymond_rrd files are being created in /export/home/xymon/data/* anywhere. If I do a ./xymon 0.0.0.0 "enable xymonems.xymond_rrd" it doesn’t change it at all. It is like the status is stuck somewhere, but I am not sure how or where.

From: Neal, Jonathan W [mailto:wes.neal at verizon.com] Sent: Monday, October 20, 2014 12:52 PM To: Jeremy Laidman Cc: xymon at xymon.com Subject: RE: [Xymon] Multiple Issues with 4.3.17 install

No core file on the system.  I think there is something else odd going on.  I removed all the data that belongs to the xymonems host from /data/* .  I restarted the system and xymond_rrd is still blue, even though it isn’t even disabled any longer.  It’s like it can’t or doesn’t know how to update the status for it.  I watched the xymond status for from yellow to green after the restarted, but xymond_rrd never changed.

From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] Sent: Sunday, October 19, 2014 4:08 PM To: Neal, Jonathan W Subject: Re: [Xymon] Multiple Issues with 4.3.17 install

Look for a core file, then use gdb to get a backtrace. This will tell us what it is doing when it crashes. J On 18/10/2014 7:31 AM, "Neal, Jonathan W via Xymon" <xymon at xymon.com> wrote:

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

---------- Forwarded message ---------- From: "Neal, Jonathan W" <wes.neal at verizon.com> To: "xymon at xymon.com" <xymon at xymon.com> Cc:  Date: Fri, 17 Oct 2014 16:31:06 -0400 Subject: RE: [Xymon] Multiple Issues with 4.3.17 install I am unsure why it is even showing purple, but it definitely is and it keeps alerting on it.  If I drill down into a system I see data being graphed that is valid.  If I look at the processes on the system I see:

xymonems:xymon > ps -ef |grep xymond_rrd    xymon 18720 18714   0 02:45:03 ?           0:00 xymond_channel --channel=data --log=/var/log/xymon/rrd-data.log xymond_rrd --rr    xymon 18806 18720   0 02:45:12 ?           0:02 xymond_rrd --rrddir=/export/home/xymon/data/rrd    xymon 18761 18719   0 02:45:04 ?           0:51 xymond_rrd --rrddir=/export/home/xymon/data/rrd    xymon 18719 18714   0 02:45:03 ?           0:14 xymond_channel --channel=status --log=/var/log/xymon/rrd-status.log xymond_rrd

So to me it seems as if it is running.  What am I missing here?

Wes

---------- Forwarded message ---------- From: "Neal, Jonathan W" <wes.neal at verizon.com> To: "xymon at xymon.com" <xymon at xymon.com> Cc:  Date: Thu, 16 Oct 2014 18:40:46 -0400 Subject: Multiple Issues with 4.3.17 install I am coming from an early 4.2 install.  I merged my bb-hosts, hobbit-alerts.cfg and hobbit-clients.cfg files into the proper files in the new 4.3.17 install.  I also copied over the entire histlogs directory from data.   Currently xymon_rrd keeps dying and going purple with a Fatal signal error.   rrd-status log has this in it going back most of the day:   2014-10-16 19:23:00 Peer at 0.0.0.0:0 failed: Broken pipe 2014-10-16 19:23:00 Peer not up, flushing message queue 2014-10-16 19:24:43 Shutting down, flushing cached updates to disk 2014-10-16 19:28:39 Peer not up, flushing message queue 2014-10-16 20:00:35 Shutting down, flushing cached updates to disk 2014-10-16 20:00:36 Cache flush completed 2014-10-16 21:58:19 Peer not up, flushing message queue 2014-10-16 22:30:58 Shutting down, flushing cached updates to disk 2014-10-16 22:30:59 Cache flush completed 2014-10-16 22:31:14 Peer not up, flushing message queue   Xymond is also constantly going yellow and I again see that 0.0.0.0:1984 that is mentioned above:   Statistics for Xymon daemon Version: 4.3.17 Up since 16-Oct-2014 22:31:09 (0 days, 00:04:59)   Incoming messages      :        937

• status               :        885
• combo                :          1
• extcombo             :         22
• page                 :          0
• summary              :          0
• data                 :          6
• client               :          2
• notes                :          0
• enable               :          0
• disable              :          0
• ack                  :          0
• config               :          4
• query                :          0
• xymondboard          :          6
• xymondlog            :          5
• drop                 :          0
• rename               :          0
• dummy                :          1
• ping                 :          0
• notify               :          0
• schedule             :          0
• download             :          0
• Bogus/Timeouts       :          5 Incoming messages/sec  :          3 (average last 300 seconds)   status channel messages:        885 (1 readers) stachg channel messages:        877 (1 readers) page   channel messages:         37 (1 readers) data   channel messages:          6 (1 readers) notes  channel messages:          0 (0 readers) enadis channel messages:          0 (0 readers) client channel messages:          2 (1 readers) clichg channel messages:          0 (1 readers) user   channel messages:          0 (0 readers) backfeed messages      :          0     Latest error messages: Loading hostnames Loading saved state Setting up network listener on 0.0.0.0:1984 Setting up signal handlers Setting up xymond channels Setting up logfiles Setup complete   Can anyone tell me what might be going on? Thanks in advance!