[Xymon] xymon 4.3.10 not working for HP-UX 11.31 !
Andersson Tomas
tomas.andersson at sca.com
Thu Aug 30 13:00:50 CEST 2012
Hi Henrik !
Thanks for reply !
I tried what you suggested but it didn't work I did not get anything but the following:
xymon at hpivm010:/opt/xymon # xymoncmd xymond_channel --channel=status cat
2012-08-30 12:45:10 Using default environment file /opt/xymon/server/etc/xymonserver.cfg
2012-08-30 12:45:43 Peer not up, flushing message queue
2012-08-30 12:46:38 Peer not up, flushing message queue
2012-08-30 12:48:37 Peer not up, flushing message queue
2012-08-30 12:48:37 Peer not up, flushing message queue
2012-08-30 12:48:37 Peer not up, flushing message queue
2012-08-30 12:48:37 Peer not up, flushing message queue
If you look at the top command then you see the process xymond_channel is consuming huge amount of cpu:
System: hpivm010 Thu Aug 30 12:54:02 2012
Load averages: 0.31, 0.39, 1.03
179 processes: 123 sleeping, 56 running
Cpu states:
CPU LOAD USER NICE SYS IDLE BLOCK SWAIT INTR SSYS
0 0.53 63.4% 0.0% 36.6% 0.0% 0.0% 0.0% 0.0% 0.0%
1 0.08 0.0% 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%
--- ---- ----- ----- ----- ----- ----- ----- ----- -----
avg 0.31 32.0% 0.0% 18.0% 50.0% 0.0% 0.0% 0.0% 0.0%
System Page Size: 4Kbytes
Memory: 376932K (187064K) real, 830024K (428180K) virtual, 3418312K free Page# 1/4
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
0 pts/0 26422 xymon 223 20 15376K 588K run 0:15 65.76 48.71 xymond_channel
1 ? 2153 root 168 20 15568K 1120K sleep 12:30 0.36 0.36 utild
1 ? 25829 root 154 20 24352K 2008K sleep 0:00 0.06 0.06 sshd:
0 ? 920 root 127 20 12976K 844K sleep 0:46 0.04 0.04 netfmt
0 ? 77 root 152 20 216K 192K run 3:01 0.04 0.04 pm_schedcpu
1 ? 63 root -32 20 72K 64K sleep 0:18 0.03 0.03 progressdaemon
0 ? 75 root 152 20 2160K 1920K run 1:35 0.03 0.03 vxfsd
0 ? 1493 root 154 20 11116K 1168K sleep 2:40 0.02 0.02 sendmail:
0 ? 1565 root 154 20 6876K 668K sleep 0:51 0.02 0.02 ipv6agt
0 ? 25578 xymon 154 20 42192K 1084K sleep 0:00 0.01 0.01 xymond
0 ? 0 root 127 20 72K 64K sleep 0:25 0.00 0.00 swapper
0 ? 1 root 152 20 2480K 656K run 0:00 0.00 0.00 init
1 ? 2 root 128 20 72K 64K sleep 0:03 0.00 0.00 vhand
1 ? 3 root 152 20 72K 64K sleep 0:28 0.00 0.00 statdaemon
This is what you get when doing a tusc of the process
semop(24592, 0x7fffd5a8, 1) .................................................................................. ERR#11 EAGAIN
sigprocmask(SIG_BLOCK, 0x7fffd500, 0x7fffd520) ............................................................... = 0
sigprocmask(SIG_SETMASK, 0x7fffd540, 0x7fffd560) ............................................................. = 0
sigprocmask(SIG_BLOCK, 0x7fffd4f0, 0x7fffd510) ............................................................... = 0
sigprocmask(SIG_SETMASK, 0x7fffd530, 0x7fffd550) ............................................................. = 0
semop(24592, 0x7fffd5a8, 1) .................................................................................. ERR#11 EAGAIN
sigprocmask(SIG_BLOCK, 0x7fffd500, 0x7fffd520) ............................................................... = 0
sigprocmask(SIG_SETMASK, 0x7fffd540, 0x7fffd560) ............................................................. = 0
sigprocmask(SIG_BLOCK, 0x7fffd4f0, 0x7fffd510) ............................................................... = 0
sigprocmask(SIG_SETMASK, 0x7fffd530, 0x7fffd550) ............................................................. = 0
semop(24592, 0x7fffd5a8, 1) .................................................................................. ERR#11 EAGAIN
sigprocmask(SIG_BLOCK, 0x7fffd500, 0x7fffd520) ............................................................... = 0
sigprocmask(SIG_SETMASK, 0x7fffd540, 0x7fffd560) ............................................................. = 0
sigprocmask(SIG_BLOCK, 0x7fffd4f0, 0x7fffd510) ............................................................... = 0
sigprocmask(SIG_SETMASK, 0x7fffd530, 0x7fffd550) ............................................................. = 0
semop(24592, 0x7fffd5a8, 1) .................................................................................. ERR#11 EAGAIN
sigprocmask(SIG_BLOCK, 0x7fffd500, 0x7fffd520) ............................................................... = 0
sigprocmask(SIG_SETMASK, 0x7fffd540, 0x7fffd560) ............................................................. = 0
sigprocmask(SIG_BLOCK, 0x7fffd4f0, 0x7fffd510) ............................................................... = 0
sigprocmask(SIG_SETMASK, 0x7fffd530, 0x7fffd550) ............................................................. = 0
semop(24592, 0x7fffd5a8, 1) .................................................................................. ERR#11 EAGAIN
seems like the process is hanging ...
any ideas ?
Best Regards,
/Tomas Andersson
Unix System Admin/Tech/Dev
SCA IT Services
Tel. +46 31 7460313
Mob. +46 703 610313
-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner
Sent: den 30 augusti 2012 11:16
To: xymon at xymon.com
Subject: Re: [Xymon] xymon 4.3.10 not working for HP-UX 11.31 !
On 30-08-2012 10:50, Andersson Tomas wrote:
> Hi there!
>
> I have still no Luck with the xymon v 4.3.10 to function on my systems that is:
> HP-UX hpivm006 B.11.31 U ia64 1185740114 unlimited-user license
> ia64 hp server Integrity Virtual Machine
>
> The folloving logfiles only contain rows of: " Peer not up, flushing message queue"
>
> alert.log
> clientdata.log
> history.log
> hostdata.log
> rrd-data.log
> rrd-status.log
The only reason I can think of is that the various xymond_* modules won't run for some reason.
See if you can run them by hand. You can disable all of the
xymond_channel+xymond_* tasks in tasks.cfg to avoid the system spinning out of control, then start Xymon. You should only have xymonlaunch and xymond running (xymonnet and the client will also run, once every 5 minutes).
Then - as the user xymond runs as! - run "xymoncmd xymond_channel --channel=status cat". This should result in all incoming status-messages being dumped on your screen. If that works, then try "xymoncmd xymond_channel --channel=client xymond_client --debug" - this should start the client data handler, so you should start getting status updates from your clients (cpu, disk, memory etc).
Regards,
Henrik
_______________________________________________
Xymon mailing list
Xymon at xymon.com<mailto:Xymon at xymon.com>
http://lists.xymon.com/mailman/listinfo/xymon
________________________________
This message may contain confidential, proprietary or legally
privileged information and is intended for the addressee's use
only. Any usage, disclosure, distribution, print or copying of
any part of this message is prohibited unless you are the
intended recipient. If you receive this message in error,
please delete it from any computer and notify the sender. If
you suspect that this message may have been altered, please
notify the sender. SCA has taken every reasonable precaution
to ensure that this e-mail and any attachments to this e-mail
has been scanned for viruses. However, SCA does not accept
liability for any damage caused by software viruses brought to
you by this mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20120830/1302c171/attachment.html>
More information about the Xymon
mailing list