Xymon Mailing List Archive search

upgrading proxy/server to 4.3.4 from 4.2.3

3 messages in this thread

list Paul Root · Thu, 18 Aug 2011 11:29:32 -0500 ·
I have a proxy server on a private network, which forwards to the main server, a devel server, and itself (server on port 1985).

I ran the bbcmd .../build/Xymon-430.sh script then did a make install.

It was having trouble with the client, but I found that the xymonclient.cfg had put in port 1985, and only its own ip address. I fixed that, and the primary and devel servers are pretty much happy with it.

However, the server on the proxy will not update its web pages. I did update the httpd config file, that's not the issue.

I found in /var/log/Xymon/bb-display.log, the following:

2011-08-18 11:01:19 xymond status-board not available, code 0
2011-08-18 11:01:19 Failed to load current Xymon status, aborting page-update

And I can't find anything to explain it. Can someone help?

The particulars are CentOS 5.6 inside VMWare. It worked flawlessly in 4.2.3.  Do you need the tasks.cfg file?

$ ps -ef |grep xymon
xymon    10048     1  0 11:01 ?        00:00:00 /usr/lib64/xymon/server/bin/xymonlaunch --config=/usr/lib64/xymon/server/etc/tasks.cfg --env=/usr/lib64/xymon/server/etc/xymonserver.cfg --log=/var/log/xymon/xymonlaunch.log --pidfile=/var/log/xymon/xymonlaunch.pid
xymon    10049 10048  0 11:01 ?        00:00:01 hobbitd --listen=0.0.0.0:1985 --pidfile=/var/log/xymon/hobbitd.pid --restart=/usr/lib64/xymon/server/tmp/hobbitd.chk --checkpoint-file=/usr/lib64/xymon/server/tmp/hobbitd.chk --checkpoint-interval=600 --log=/var/log/xymon/hobbitd.log --admin-senders=127.0.0.1 204.155.141.230 --store-clientlogs=!msgs
xymon    10050 10048  0 11:01 ?        00:00:01 /usr/lib64/xymon/server/bin/bbproxy --hobbitd --bbdisplay=127.0.0.1:1985,207.225.133.169,204.155.141.212 --listen=0.0.0.0 1984 --report=stnxymproxy.bbproxy --no-daemon --pidfile=/var/log/xymon/bbproxy.pid
xymon    10145 10048  0 11:01 ?        00:00:00 hobbitd_channel --channel=stachg --log=/var/log/xymon/history.log hobbitd_history
xymon    10146 10048  0 11:01 ?        00:00:00 hobbitd_channel --channel=page --log=/var/log/xymon/page.log hobbitd_alert --checkpoint-file=/usr/lib64/xymon/server/tmp/alert.chk --checkpoint-interval=600
xymon    10147 10048  0 11:01 ?        00:00:00 hobbitd_channel --channel=client --log=/var/log/xymon/clientdata.log hobbitd_client
xymon    10148 10048 42 11:01 ?        00:10:25 hobbitd_channel --channel=status --log=/var/log/xymon/rrd-status.log hobbitd_rrd --rrddir=/var/lib/xymon/rrd
xymon    10149 10048 42 11:01 ?        00:10:22 hobbitd_channel --channel=data --log=/var/log/xymon/rrd-data.log hobbitd_rrd --rrddir=/var/lib/xymon/rrd
xymon    10150 10048  0 11:01 ?        00:00:00 hobbitd_channel --channel=clichg --log=/var/log/xymon/hostdata.log hobbitd_hostdata
xymon    10153 10145  0 11:01 ?        00:00:00 hobbitd_history
xymon    10163 10147  0 11:01 ?        00:00:00 hobbitd_client
xymon    10404 10146  0 11:06 ?        00:00:00 hobbitd_alert --checkpoint-file=/usr/lib64/xymon/server/tmp/alert.chk --checkpoint-interval=600
xymon    10408 10150  0 11:06 ?        00:00:00 hobbitd_hostdata
xymon    11473     1  0 11:21 ?        00:00:00 sh -c vmstat 300 2 1>/usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy.11389 2>&1; mv /usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy.11389 /usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy
xymon    11474 11473  0 11:21 ?        00:00:00 vmstat 300 2
root     11696  7499  0 11:26 pts/2    00:00:00 grep xymon


Paul Root    - Engineer III  - Qwest is now CenturyLink


This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
list Paul Root · Fri, 19 Aug 2011 16:02:37 -0500 ·
No one has any ideas why the upgrade script failed?


Paul Root    - Engineer III  - Qwest is now CenturyLink

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On
Behalf Of Root, Paul
Sent: Thursday, August 18, 2011 11:30 AM
To: 'xymon at xymon.com'
Subject: [Xymon] upgrading proxy/server to 4.3.4 from 4.2.3
quoted from Paul Root

I have a proxy server on a private network, which forwards to the main
server, a devel server, and itself (server on port 1985).

I ran the bbcmd .../build/Xymon-430.sh script then did a make install.

It was having trouble with the client, but I found that the
xymonclient.cfg had put in port 1985, and only its own ip address. I
fixed that, and the primary and devel servers are pretty much happy
with it.

However, the server on the proxy will not update its web pages. I did
update the httpd config file, that's not the issue.

I found in /var/log/Xymon/bb-display.log, the following:

2011-08-18 11:01:19 xymond status-board not available, code 0

2011-08-18 11:01:19 Failed to load current Xymon status, aborting page-
update
quoted from Paul Root

And I can't find anything to explain it. Can someone help?

The particulars are CentOS 5.6 inside VMWare. It worked flawlessly in
4.2.3.  Do you need the tasks.cfg file?

$ ps -ef |grep xymon
xymon    10048     1  0 11:01 ?        00:00:00
/usr/lib64/xymon/server/bin/xymonlaunch --
config=/usr/lib64/xymon/server/etc/tasks.cfg --
env=/usr/lib64/xymon/server/etc/xymonserver.cfg --
log=/var/log/xymon/xymonlaunch.log --
pidfile=/var/log/xymon/xymonlaunch.pid
xymon    10049 10048  0 11:01 ?        00:00:01 hobbitd --
listen=0.0.0.0:1985 --pidfile=/var/log/xymon/hobbitd.pid --

restart=/usr/lib64/xymon/server/tmp/hobbitd.chk --checkpoint-
file=/usr/lib64/xymon/server/tmp/hobbitd.chk --checkpoint-interval=600
quoted from Paul Root
--log=/var/log/xymon/hobbitd.log --admin-senders=127.0.0.1
204.155.141.230 --store-clientlogs=!msgs
xymon    10050 10048  0 11:01 ?        00:00:01
/usr/lib64/xymon/server/bin/bbproxy --hobbitd --
bbdisplay=127.0.0.1:1985,207.225.133.169,204.155.141.212 --
listen=0.0.0.0 1984 --report=stnxymproxy.bbproxy --no-daemon --
pidfile=/var/log/xymon/bbproxy.pid
xymon    10145 10048  0 11:01 ?        00:00:00 hobbitd_channel --
channel=stachg --log=/var/log/xymon/history.log hobbitd_history
xymon    10146 10048  0 11:01 ?        00:00:00 hobbitd_channel --

channel=page --log=/var/log/xymon/page.log hobbitd_alert --checkpoint-
file=/usr/lib64/xymon/server/tmp/alert.chk --checkpoint-interval=600
quoted from Paul Root
xymon    10147 10048  0 11:01 ?        00:00:00 hobbitd_channel --
channel=client --log=/var/log/xymon/clientdata.log hobbitd_client
xymon    10148 10048 42 11:01 ?        00:10:25 hobbitd_channel --
channel=status --log=/var/log/xymon/rrd-status.log hobbitd_rrd --
rrddir=/var/lib/xymon/rrd
xymon    10149 10048 42 11:01 ?        00:10:22 hobbitd_channel --
channel=data --log=/var/log/xymon/rrd-data.log hobbitd_rrd --
rrddir=/var/lib/xymon/rrd
xymon    10150 10048  0 11:01 ?        00:00:00 hobbitd_channel --
channel=clichg --log=/var/log/xymon/hostdata.log hobbitd_hostdata
xymon    10153 10145  0 11:01 ?        00:00:00 hobbitd_history
xymon    10163 10147  0 11:01 ?        00:00:00 hobbitd_client
xymon    10404 10146  0 11:06 ?        00:00:00 hobbitd_alert --

checkpoint-file=/usr/lib64/xymon/server/tmp/alert.chk --checkpoint-
interval=600
quoted from Paul Root
xymon    10408 10150  0 11:06 ?        00:00:00 hobbitd_hostdata
xymon    11473     1  0 11:21 ?        00:00:00 sh -c vmstat 300 2
1>/usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy.11389 2>&1; mv
/usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy.11389
/usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy
xymon    11474 11473  0 11:21 ?        00:00:00 vmstat 300 2
root     11696  7499  0 11:26 pts/2    00:00:00 grep xymon


Paul Root    - Engineer III  - Qwest is now CenturyLink


This communication is the property of CenturyLink and may contain
confidential or privileged information. Unauthorized use of this
communication is strictly
prohibited and may be unlawful.  If you have received this
communication
in error, please immediately notify the sender by reply e-mail and
destroy
all copies of the communication and any attachments.
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
list Paul Root · Mon, 22 Aug 2011 15:10:27 -0500 ·
Xymonserver.cfg   ->  XYMONDPORT=1985
quoted from Paul Root

Paul Root    - Engineer III  - Qwest is now CenturyLink

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On
Behalf Of Root, Paul

Sent: Friday, August 19, 2011 4:03 PM
To: 'xymon at xymon.com'
Subject: Re: [Xymon] upgrading proxy/server to 4.3.4 from 4.2.3
quoted from Paul Root

No one has any ideas why the upgrade script failed?


Paul Root    - Engineer III  - Qwest is now CenturyLink

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On
Behalf Of Root, Paul
Sent: Thursday, August 18, 2011 11:30 AM
To: 'xymon at xymon.com'
Subject: [Xymon] upgrading proxy/server to 4.3.4 from 4.2.3

I have a proxy server on a private network, which forwards to the
main
server, a devel server, and itself (server on port 1985).

I ran the bbcmd .../build/Xymon-430.sh script then did a make
install.

It was having trouble with the client, but I found that the
xymonclient.cfg had put in port 1985, and only its own ip address. I
fixed that, and the primary and devel servers are pretty much happy
with it.

However, the server on the proxy will not update its web pages. I did
update the httpd config file, that's not the issue.

I found in /var/log/Xymon/bb-display.log, the following:

2011-08-18 11:01:19 xymond status-board not available, code 0
2011-08-18 11:01:19 Failed to load current Xymon status, aborting
page-
update

And I can't find anything to explain it. Can someone help?

The particulars are CentOS 5.6 inside VMWare. It worked flawlessly in
4.2.3.  Do you need the tasks.cfg file?

$ ps -ef |grep xymon
xymon    10048     1  0 11:01 ?        00:00:00
/usr/lib64/xymon/server/bin/xymonlaunch --
config=/usr/lib64/xymon/server/etc/tasks.cfg --
env=/usr/lib64/xymon/server/etc/xymonserver.cfg --
log=/var/log/xymon/xymonlaunch.log --
pidfile=/var/log/xymon/xymonlaunch.pid
xymon    10049 10048  0 11:01 ?        00:00:01 hobbitd --
listen=0.0.0.0:1985 --pidfile=/var/log/xymon/hobbitd.pid --
restart=/usr/lib64/xymon/server/tmp/hobbitd.chk --checkpoint-

file=/usr/lib64/xymon/server/tmp/hobbitd.chk --checkpoint-
interval=600
quoted from Paul Root
--log=/var/log/xymon/hobbitd.log --admin-senders=127.0.0.1
204.155.141.230 --store-clientlogs=!msgs
xymon    10050 10048  0 11:01 ?        00:00:01
/usr/lib64/xymon/server/bin/bbproxy --hobbitd --
bbdisplay=127.0.0.1:1985,207.225.133.169,204.155.141.212 --
listen=0.0.0.0 1984 --report=stnxymproxy.bbproxy --no-daemon --
pidfile=/var/log/xymon/bbproxy.pid
xymon    10145 10048  0 11:01 ?        00:00:00 hobbitd_channel --
channel=stachg --log=/var/log/xymon/history.log hobbitd_history
xymon    10146 10048  0 11:01 ?        00:00:00 hobbitd_channel --
channel=page --log=/var/log/xymon/page.log hobbitd_alert --
checkpoint-
file=/usr/lib64/xymon/server/tmp/alert.chk --checkpoint-interval=600
xymon    10147 10048  0 11:01 ?        00:00:00 hobbitd_channel --
channel=client --log=/var/log/xymon/clientdata.log hobbitd_client
xymon    10148 10048 42 11:01 ?        00:10:25 hobbitd_channel --
channel=status --log=/var/log/xymon/rrd-status.log hobbitd_rrd --
rrddir=/var/lib/xymon/rrd
xymon    10149 10048 42 11:01 ?        00:10:22 hobbitd_channel --
channel=data --log=/var/log/xymon/rrd-data.log hobbitd_rrd --
rrddir=/var/lib/xymon/rrd
xymon    10150 10048  0 11:01 ?        00:00:00 hobbitd_channel --
channel=clichg --log=/var/log/xymon/hostdata.log hobbitd_hostdata
xymon    10153 10145  0 11:01 ?        00:00:00 hobbitd_history
xymon    10163 10147  0 11:01 ?        00:00:00 hobbitd_client
xymon    10404 10146  0 11:06 ?        00:00:00 hobbitd_alert --
checkpoint-file=/usr/lib64/xymon/server/tmp/alert.chk --checkpoint-
interval=600
xymon    10408 10150  0 11:06 ?        00:00:00 hobbitd_hostdata
xymon    11473     1  0 11:21 ?        00:00:00 sh -c vmstat 300 2
1>/usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy.11389 2>&1; mv
/usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy.11389
/usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy
xymon    11474 11473  0 11:21 ?        00:00:00 vmstat 300 2
root     11696  7499  0 11:26 pts/2    00:00:00 grep xymon


Paul Root    - Engineer III  - Qwest is now CenturyLink


This communication is the property of CenturyLink and may contain
confidential or privileged information. Unauthorized use of this
communication is strictly
prohibited and may be unlawful.  If you have received this
communication
in error, please immediately notify the sender by reply e-mail and
destroy
all copies of the communication and any attachments.
This communication is the property of CenturyLink and may contain
confidential or privileged information. Unauthorized use of this
communication is strictly
prohibited and may be unlawful.  If you have received this
communication
in error, please immediately notify the sender by reply e-mail and
destroy
all copies of the communication and any attachments.
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.