Good day
I please need guidance to configure xymon on Ubuntu 24.04
I installed xymon from the default apt repository. It's a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure. Also changed the repo to the default mirrors.kernel.org and installed xymon from there.
apt-cache policy xymon
xymon: Installed: 4.3.30-2build3 Candidate: 4.3.30-2build3 Version table: *** 4.3.30-2build3 500 500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status
Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs Confirm port 1984 is listening
I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638 I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating. **** snip **** 2024-09-13 14:50:52.967847 Peer not up, flushing message queue *** buffer overflow detected ***: terminated 2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6 2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0 failed: Broken pipe **** snip ****
This is a fresh install and the only change I made in xymonserver.cfg are: XYMONSERVERIP="server ip"
Firewall disabled Apparmor disabled
Thank you.
ChrisP
Hi Chris,
You may need to change some memory limits in xymonserver.cfg MAXMSG_CLIENT MAXMSG_STATUS MAXMSG_DATA
If you have plenty of memory I would multiply them all by 8.
HTH Jeremy
------ Original Message ------ From: "Chris Pretorius via Xymon" <xymon@xymon.com> To: "Xymon Mailing List" <xymon@xymon.com> Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za> Sent: 13/09/2024 14:22:38 Subject: [Xymon] Xymon on Ubuntu 24.04
Good day
I please need guidance to configure xymon on Ubuntu 24.04
I installed xymon from the default apt repository.
It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure.
Also changed the repo to the default mirrors.kernel.org and installed xymon from there.
apt-cache policy xymon
xymon:
Installed: 4.3.30-2build3
Candidate: 4.3.30-2build3
Version table:
*** 4.3.30-2build3 500
500 https://mirrors.kernel.org/ubuntu noble/universe amd64Packages
100 /var/lib/dpkg/statusXymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs
Confirm port 1984 is listening
I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638 <https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638>
I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating.
**** snip ****
2024-09-13 14:50:52.967847 Peer not up, flushing message queue
*** buffer overflow detected ***: terminated
2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6
2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0 failed: Broken pipe
**** snip ****
This is a fresh install and the only change I made in xymonserver.cfg are:
XYMONSERVERIP=”server ip”
Firewall disabled
Apparmor disabled
Thank you.
ChrisP
Thanx Jeremy
Increased the limit and restarted, but still getting the same line in the logs.
Best regards
From: Jeremy Ruffer <jeremy.ruffer@gmail.com> Sent: Friday, 13 September 2024 15:55 To: Xymon mailinglist <xymon@xymon.com>; Xymon Mailing List <xymon@xymon.com> Cc: Chris Pretorius <chris.pretorius@coaxle.co.za> Subject: Re: [Xymon] Xymon on Ubuntu 24.04
Hi Chris,
You may need to change some memory limits in xymonserver.cfg MAXMSG_CLIENT MAXMSG_STATUS MAXMSG_DATA
If you have plenty of memory I would multiply them all by 8.
HTH Jeremy
------ Original Message ------ From: "Chris Pretorius via Xymon" <xymon@xymon.com<mailto:xymon@xymon.com>> To: "Xymon Mailing List" <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Sent: 13/09/2024 14:22:38 Subject: [Xymon] Xymon on Ubuntu 24.04
Good day
I please need guidance to configure xymon on Ubuntu 24.04
I installed xymon from the default apt repository. It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure. Also changed the repo to the default mirrors.kernel.org and installed xymon from there.
apt-cache policy xymon
xymon: Installed: 4.3.30-2build3 Candidate: 4.3.30-2build3 Version table: *** 4.3.30-2build3 500 500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status
Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs Confirm port 1984 is listening
I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638 I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating. **** snip **** 2024-09-13 14:50:52.967847 Peer not up, flushing message queue *** buffer overflow detected ***: terminated 2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6 2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0 failed: Broken pipe **** snip ****
This is a fresh install and the only change I made in xymonserver.cfg are: XYMONSERVERIP=”server ip”
Firewall disabled Apparmor disabled
Thank you.
ChrisP
What have you got them set to now?
I would double them again and again if needed.
There is one slight gotcha here. We had a system where the figure was bytes instead of KB in spite of the comments in the file saying they were KB.
Regards
Jeremy
------ Original Message ------ From: "Chris Pretorius" <chris.pretorius@coaxle.co.za> To: "Jeremy Ruffer" <jeremy.ruffer@gmail.com>; "Xymon mailinglist" <xymon@xymon.com> Sent: 13/09/2024 15:01:46 Subject: RE: [Xymon] Xymon on Ubuntu 24.04
Thanx Jeremy
Increased the limit and restarted, but still getting the same line in the logs.
Best regards
From: Jeremy Ruffer <jeremy.ruffer@gmail.com> Sent: Friday, 13 September 2024 15:55 To: Xymon mailinglist <xymon@xymon.com>; Xymon Mailing List <xymon@xymon.com> Cc: Chris Pretorius <chris.pretorius@coaxle.co.za> Subject: Re: [Xymon] Xymon on Ubuntu 24.04
Hi Chris,
You may need to change some memory limits in xymonserver.cfg
MAXMSG_CLIENT
MAXMSG_STATUS
MAXMSG_DATA
If you have plenty of memory I would multiply them all by 8.
HTH
Jeremy
------ Original Message ------
From: "Chris Pretorius via Xymon" <xymon@xymon.com>
To: "Xymon Mailing List" <xymon@xymon.com>
Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za>
Sent: 13/09/2024 14:22:38
Subject: [Xymon] Xymon on Ubuntu 24.04
Good day
I please need guidance to configure xymon on Ubuntu 24.04
I installed xymon from the default apt repository.
It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure.
Also changed the repo to the default mirrors.kernel.org and installed xymon from there.
apt-cache policy xymon
xymon:
Installed: 4.3.30-2build3
Candidate: 4.3.30-2build3
Version table:
*** 4.3.30-2build3 500
500 https://mirrors.kernel.org/ubuntu noble/universe amd64Packages
100 /var/lib/dpkg/statusXymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs
Confirm port 1984 is listening
I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638
I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating.
**** snip ****
2024-09-13 14:50:52.967847 Peer not up, flushing message queue
*** buffer overflow detected ***: terminated
2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6
2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0 failed: Broken pipe
**** snip ****
This is a fresh install and the only change I made in xymonserver.cfg are:
XYMONSERVERIP=”server ip”
Firewall disabled
Apparmor disabled
Thank you.
ChrisP
Hi Jeremy I went berserk and set very high values MAXMSG_CLIENT=4194304 MAXMSG_STATUS=4194304 MAXMSG_DATA=4194304 But the problem is not resolved -------------------------- Output in rrd-status.log with –debug enabled 2024-09-13 21:58:08.000165 Peer at 0.0.0.0:0 failed: Broken pipe 2024-09-13 21:58:13.080151 Peer not up, flushing message queue 13258 2024-09-13 21:58:13.109283 setup_feedback_queue: got ID -1 for key 0xA010D68 13258 2024-09-13 21:58:13.109533 Opening file /usr/lib/xymon/server/etc/rrddefinitions.cfg 13258 2024-09-13 21:58:13.111854 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=4198399 13258 2024-09-13 21:58:13.111894 Got 1856 bytes 13258 2024-09-13 21:58:13.111900 xymond_rrd: Got message 1 @@status#1/xymon.xyz.co.za|1726257493.075018|x.x.x.x||xymon.xyz.co.za|xymongen|1726259293|green||green|1726230891|0||0||1726237717|||0| 13258 2024-09-13 21:58:13.111930 startpos 1856, fillpos 1856, endpos -1 13258 2024-09-13 21:58:13.111969 Transport setup is: 13258 2024-09-13 21:58:13.111995 xymondportnumber = 1984 13258 2024-09-13 21:58:13.111997 xymonproxyhost = NONE 13258 2024-09-13 21:58:13.112043 xymonproxyport = 0 13258 2024-09-13 21:58:13.112045 Recipient listed as 'x.x.x.x' 13258 2024-09-13 21:58:13.112048 Standard protocol on port 1984 13258 2024-09-13 21:58:13.112056 Will connect to address x.x.x.x port 1984 13258 2024-09-13 21:58:13.112726 Connect status is 0 13258 2024-09-13 21:58:13.112769 Sent 16 bytes 13258 2024-09-13 21:58:13.113837 Read 826 bytes 13258 2024-09-13 21:58:13.113861 Closing connection *** buffer overflow detected ***: terminated 2024-09-13 21:58:13.366744 Child process 13258 died: Signal 6 Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com> Sent: Friday, 13 September 2024 16:11 To: Chris Pretorius <chris.pretorius@coaxle.co.za>; Xymon mailinglist <xymon@xymon.com> Subject: Re[2]: [Xymon] Xymon on Ubuntu 24.04 What have you got them set to now? I would double them again and again if needed. There is one slight gotcha here. We had a system where the figure was bytes instead of KB in spite of the comments in the file saying they were KB. Regards Jeremy ------ Original Message ------ From: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> To: "Jeremy Ruffer" <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>>; "Xymon mailinglist" <xymon@xymon.com<mailto:xymon@xymon.com>> Sent: 13/09/2024 15:01:46 Subject: RE: [Xymon] Xymon on Ubuntu 24.04 Thanx Jeremy Increased the limit and restarted, but still getting the same line in the logs. Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>> Sent: Friday, 13 September 2024 15:55 To: Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>>; Xymon Mailing List <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Subject: Re: [Xymon] Xymon on Ubuntu 24.04 Hi Chris, You may need to change some memory limits in xymonserver.cfg MAXMSG_CLIENT MAXMSG_STATUS MAXMSG_DATA If you have plenty of memory I would multiply them all by 8. HTH Jeremy ------ Original Message ------ From: "Chris Pretorius via Xymon" <xymon@xymon.com<mailto:xymon@xymon.com>> To: "Xymon Mailing List" <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Sent: 13/09/2024 14:22:38 Subject: [Xymon] Xymon on Ubuntu 24.04 Good day I please need guidance to configure xymon on Ubuntu 24.04 I installed xymon from the default apt repository. It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure. Also changed the repo to the default mirrors.kernel.org and installed xymon from there. # apt-cache policy xymon xymon: Installed: 4.3.30-2build3 Candidate: 4.3.30-2build3 Version table: *** 4.3.30-2build3 500 500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs Confirm port 1984 is listening I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638 I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating. **** snip **** 2024-09-13 14:50:52.967847 Peer not up, flushing message queue *** buffer overflow detected ***: terminated 2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6 2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0 failed: Broken pipe **** snip **** This is a fresh install and the only change I made in xymonserver.cfg are: XYMONSERVERIP=”server ip” Firewall disabled Apparmor disabled Thank you. ChrisP
Is SELinux enabled on your Ubuntu install? If so, you may need to change it from Enforcing mode to Permissive mode in the /etc/selinux/config file. SELinux will block many of the commands run by Xymon unless they are all explicitly granted permission by SELinux. Tom On Fri, Sep 13, 2024 at 2:07 PM Chris Pretorius via Xymon <xymon@xymon.com> wrote:
Hi Jeremy
I went berserk and set very high values
MAXMSG_CLIENT=4194304
MAXMSG_STATUS=4194304
MAXMSG_DATA=4194304
But the problem is not resolved
--------------------------
Output in rrd-status.log with –debug enabled
2024-09-13 21:58:08.000165 Peer at 0.0.0.0:0 failed: Broken pipe
2024-09-13 21:58:13.080151 Peer not up, flushing message queue
13258 2024-09-13 21:58:13.109283 setup_feedback_queue: got ID -1 for key 0xA010D68
13258 2024-09-13 21:58:13.109533 Opening file /usr/lib/xymon/server/etc/rrddefinitions.cfg
13258 2024-09-13 21:58:13.111854 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=4198399
13258 2024-09-13 21:58:13.111894 Got 1856 bytes
13258 2024-09-13 21:58:13.111900 xymond_rrd: Got message 1 @@status#1/ xymon.xyz.co.za|1726257493.075018|x.x.x.x||xymon.xyz.co.za |xymongen|1726259293|green||green|1726230891|0||0||1726237717|||0|
13258 2024-09-13 21:58:13.111930 startpos 1856, fillpos 1856, endpos -1
13258 2024-09-13 21:58:13.111969 Transport setup is:
13258 2024-09-13 21:58:13.111995 xymondportnumber = 1984
13258 2024-09-13 21:58:13.111997 xymonproxyhost = NONE
13258 2024-09-13 21:58:13.112043 xymonproxyport = 0
13258 2024-09-13 21:58:13.112045 Recipient listed as 'x.x.x.x'
13258 2024-09-13 21:58:13.112048 Standard protocol on port 1984
13258 2024-09-13 21:58:13.112056 Will connect to address x.x.x.x port 1984
13258 2024-09-13 21:58:13.112726 Connect status is 0
13258 2024-09-13 21:58:13.112769 Sent 16 bytes
13258 2024-09-13 21:58:13.113837 Read 826 bytes
13258 2024-09-13 21:58:13.113861 Closing connection
*** buffer overflow detected ***: terminated
2024-09-13 21:58:13.366744 Child process 13258 died: Signal 6
Best regards
*From:* Jeremy Ruffer <jeremy.ruffer@gmail.com> *Sent:* Friday, 13 September 2024 16:11 *To:* Chris Pretorius <chris.pretorius@coaxle.co.za>; Xymon mailinglist < xymon@xymon.com> *Subject:* Re[2]: [Xymon] Xymon on Ubuntu 24.04
What have you got them set to now?
I would double them again and again if needed.
There is one slight gotcha here. We had a system where the figure was bytes instead of KB in spite of the comments in the file saying they were KB.
Regards
Jeremy
------ Original Message ------
From: "Chris Pretorius" <chris.pretorius@coaxle.co.za>
To: "Jeremy Ruffer" <jeremy.ruffer@gmail.com>; "Xymon mailinglist" < xymon@xymon.com>
Sent: 13/09/2024 15:01:46
Subject: RE: [Xymon] Xymon on Ubuntu 24.04
Thanx Jeremy
Increased the limit and restarted, but still getting the same line in the logs.
Best regards
*From:* Jeremy Ruffer <jeremy.ruffer@gmail.com> *Sent:* Friday, 13 September 2024 15:55 *To:* Xymon mailinglist <xymon@xymon.com>; Xymon Mailing List < xymon@xymon.com> *Cc:* Chris Pretorius <chris.pretorius@coaxle.co.za> *Subject:* Re: [Xymon] Xymon on Ubuntu 24.04
Hi Chris,
You may need to change some memory limits in xymonserver.cfg
MAXMSG_CLIENT
MAXMSG_STATUS
MAXMSG_DATA
If you have plenty of memory I would multiply them all by 8.
HTH
Jeremy
------ Original Message ------
From: "Chris Pretorius via Xymon" <xymon@xymon.com>
To: "Xymon Mailing List" <xymon@xymon.com>
Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za>
Sent: 13/09/2024 14:22:38
Subject: [Xymon] Xymon on Ubuntu 24.04
Good day
I please need guidance to configure xymon on Ubuntu 24.04
I installed xymon from the default apt repository.
It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure.
Also changed the repo to the default mirrors.kernel.org and installed xymon from there.
# apt-cache policy xymon
xymon:
Installed: 4.3.30-2build3
Candidate: 4.3.30-2build3
Version table:
*** 4.3.30-2build3 500
500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages
100 /var/lib/dpkg/status
Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs
Confirm port 1984 is listening
I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638
I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating.
**** snip ****
2024-09-13 14:50:52.967847 Peer not up, flushing message queue
*** buffer overflow detected ***: terminated
2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6
2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0 failed: Broken pipe
**** snip ****
This is a fresh install and the only change I made in xymonserver.cfg are:
XYMONSERVERIP=”server ip”
Firewall disabled
Apparmor disabled
Thank you.
ChrisP
_______________________________________________ Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Chris Presumably this is a new installation, are there other hosts that have the client installed? Did you install the client package (xymon-client) onto your Xymon server (it won't monitor itself if that's not the case). The bug reporter said that it seemed to work with Ubuntu 22.04.4, but getting the errors on 22.04.1. What sub-release are you running? Cheers Jeremy On Sat, 14 Sept 2024 at 06:13, Tom Schmidt <tom@4schmidts.com> wrote:
Is SELinux enabled on your Ubuntu install? If so, you may need to change it from Enforcing mode to Permissive mode in the /etc/selinux/config file. SELinux will block many of the commands run by Xymon unless they are all explicitly granted permission by SELinux.
Tom
On Fri, Sep 13, 2024 at 2:07 PM Chris Pretorius via Xymon <xymon@xymon.com> wrote:
Hi Jeremy
I went berserk and set very high values
MAXMSG_CLIENT=4194304
MAXMSG_STATUS=4194304
MAXMSG_DATA=4194304
But the problem is not resolved
--------------------------
Output in rrd-status.log with –debug enabled
2024-09-13 21:58:08.000165 Peer at 0.0.0.0:0 failed: Broken pipe
2024-09-13 21:58:13.080151 Peer not up, flushing message queue
13258 2024-09-13 21:58:13.109283 setup_feedback_queue: got ID -1 for key 0xA010D68
13258 2024-09-13 21:58:13.109533 Opening file /usr/lib/xymon/server/etc/rrddefinitions.cfg
13258 2024-09-13 21:58:13.111854 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=4198399
13258 2024-09-13 21:58:13.111894 Got 1856 bytes
13258 2024-09-13 21:58:13.111900 xymond_rrd: Got message 1 @@status#1/ xymon.xyz.co.za|1726257493.075018|x.x.x.x||xymon.xyz.co.za |xymongen|1726259293|green||green|1726230891|0||0||1726237717|||0|
13258 2024-09-13 21:58:13.111930 startpos 1856, fillpos 1856, endpos -1
13258 2024-09-13 21:58:13.111969 Transport setup is:
13258 2024-09-13 21:58:13.111995 xymondportnumber = 1984
13258 2024-09-13 21:58:13.111997 xymonproxyhost = NONE
13258 2024-09-13 21:58:13.112043 xymonproxyport = 0
13258 2024-09-13 21:58:13.112045 Recipient listed as 'x.x.x.x'
13258 2024-09-13 21:58:13.112048 Standard protocol on port 1984
13258 2024-09-13 21:58:13.112056 Will connect to address x.x.x.x port 1984
13258 2024-09-13 21:58:13.112726 Connect status is 0
13258 2024-09-13 21:58:13.112769 Sent 16 bytes
13258 2024-09-13 21:58:13.113837 Read 826 bytes
13258 2024-09-13 21:58:13.113861 Closing connection
*** buffer overflow detected ***: terminated
2024-09-13 21:58:13.366744 Child process 13258 died: Signal 6
Best regards
*From:* Jeremy Ruffer <jeremy.ruffer@gmail.com> *Sent:* Friday, 13 September 2024 16:11 *To:* Chris Pretorius <chris.pretorius@coaxle.co.za>; Xymon mailinglist < xymon@xymon.com> *Subject:* Re[2]: [Xymon] Xymon on Ubuntu 24.04
What have you got them set to now?
I would double them again and again if needed.
There is one slight gotcha here. We had a system where the figure was bytes instead of KB in spite of the comments in the file saying they were KB.
Regards
Jeremy
------ Original Message ------
From: "Chris Pretorius" <chris.pretorius@coaxle.co.za>
To: "Jeremy Ruffer" <jeremy.ruffer@gmail.com>; "Xymon mailinglist" < xymon@xymon.com>
Sent: 13/09/2024 15:01:46
Subject: RE: [Xymon] Xymon on Ubuntu 24.04
Thanx Jeremy
Increased the limit and restarted, but still getting the same line in the logs.
Best regards
*From:* Jeremy Ruffer <jeremy.ruffer@gmail.com> *Sent:* Friday, 13 September 2024 15:55 *To:* Xymon mailinglist <xymon@xymon.com>; Xymon Mailing List < xymon@xymon.com> *Cc:* Chris Pretorius <chris.pretorius@coaxle.co.za> *Subject:* Re: [Xymon] Xymon on Ubuntu 24.04
Hi Chris,
You may need to change some memory limits in xymonserver.cfg
MAXMSG_CLIENT
MAXMSG_STATUS
MAXMSG_DATA
If you have plenty of memory I would multiply them all by 8.
HTH
Jeremy
------ Original Message ------
From: "Chris Pretorius via Xymon" <xymon@xymon.com>
To: "Xymon Mailing List" <xymon@xymon.com>
Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za>
Sent: 13/09/2024 14:22:38
Subject: [Xymon] Xymon on Ubuntu 24.04
Good day
I please need guidance to configure xymon on Ubuntu 24.04
I installed xymon from the default apt repository.
It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure.
Also changed the repo to the default mirrors.kernel.org and installed xymon from there.
# apt-cache policy xymon
xymon:
Installed: 4.3.30-2build3
Candidate: 4.3.30-2build3
Version table:
*** 4.3.30-2build3 500
500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages
100 /var/lib/dpkg/status
Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs
Confirm port 1984 is listening
I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638
I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating.
**** snip ****
2024-09-13 14:50:52.967847 Peer not up, flushing message queue
*** buffer overflow detected ***: terminated
2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6
2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0 failed: Broken pipe
**** snip ****
This is a fresh install and the only change I made in xymonserver.cfg are:
XYMONSERVERIP=”server ip”
Firewall disabled
Apparmor disabled
Thank you.
ChrisP
_______________________________________________ Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
_______________________________________________ Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Hi Jeremy I haven’t pointed any clients to the xymon server as yet. The local xymon-client service is disabled and not running. The xymonclient is configured in the tasks.cfg, I did disable xymonclient but did not solve the problem. The server where im struggling is is 24.04.1 LTS (Noble Numbat) Best regards ChrisP From: Jeremy Laidman <jeremy@laidman.org> Sent: Saturday, 14 September 2024 03:17 To: Xymon mailinglist <xymon@xymon.com>; Chris Pretorius <chris.pretorius@coaxle.co.za> Subject: Re: [Xymon] Re: Xymon on Ubuntu 24.04 Chris Presumably this is a new installation, are there other hosts that have the client installed? Did you install the client package (xymon-client) onto your Xymon server (it won't monitor itself if that's not the case). The bug reporter said that it seemed to work with Ubuntu 22.04.4, but getting the errors on 22.04.1. What sub-release are you running? Cheers Jeremy On Sat, 14 Sept 2024 at 06:13, Tom Schmidt <tom@4schmidts.com<mailto:tom@4schmidts.com>> wrote: Is SELinux enabled on your Ubuntu install? If so, you may need to change it from Enforcing mode to Permissive mode in the /etc/selinux/config file. SELinux will block many of the commands run by Xymon unless they are all explicitly granted permission by SELinux. Tom On Fri, Sep 13, 2024 at 2:07 PM Chris Pretorius via Xymon <xymon@xymon.com<mailto:xymon@xymon.com>> wrote: Hi Jeremy I went berserk and set very high values MAXMSG_CLIENT=4194304 MAXMSG_STATUS=4194304 MAXMSG_DATA=4194304 But the problem is not resolved -------------------------- Output in rrd-status.log with –debug enabled 2024-09-13 21:58:08.000165 Peer at 0.0.0.0:0<http://0.0.0.0:0> failed: Broken pipe 2024-09-13 21:58:13.080151 Peer not up, flushing message queue 13258 2024-09-13 21:58:13.109283 setup_feedback_queue: got ID -1 for key 0xA010D68 13258 2024-09-13 21:58:13.109533 Opening file /usr/lib/xymon/server/etc/rrddefinitions.cfg 13258 2024-09-13 21:58:13.111854 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=4198399 13258 2024-09-13 21:58:13.111894 Got 1856 bytes 13258 2024-09-13 21:58:13.111900 xymond_rrd: Got message 1 @@status#1/xymon.xyz.co.za<http://xymon.xyz.co.za>|1726257493.075018|x.x.x.x||xymon.xyz.co.za<http://xymon.xyz.co.za>|xymongen|1726259293|green||green|1726230891|0||0||1726237717|||0| 13258 2024-09-13 21:58:13.111930 startpos 1856, fillpos 1856, endpos -1 13258 2024-09-13 21:58:13.111969 Transport setup is: 13258 2024-09-13 21:58:13.111995 xymondportnumber = 1984 13258 2024-09-13 21:58:13.111997 xymonproxyhost = NONE 13258 2024-09-13 21:58:13.112043 xymonproxyport = 0 13258 2024-09-13 21:58:13.112045 Recipient listed as 'x.x.x.x' 13258 2024-09-13 21:58:13.112048 Standard protocol on port 1984 13258 2024-09-13 21:58:13.112056 Will connect to address x.x.x.x port 1984 13258 2024-09-13 21:58:13.112726 Connect status is 0 13258 2024-09-13 21:58:13.112769 Sent 16 bytes 13258 2024-09-13 21:58:13.113837 Read 826 bytes 13258 2024-09-13 21:58:13.113861 Closing connection *** buffer overflow detected ***: terminated 2024-09-13 21:58:13.366744 Child process 13258 died: Signal 6 Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>> Sent: Friday, 13 September 2024 16:11 To: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>>; Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>> Subject: Re[2]: [Xymon] Xymon on Ubuntu 24.04 What have you got them set to now? I would double them again and again if needed. There is one slight gotcha here. We had a system where the figure was bytes instead of KB in spite of the comments in the file saying they were KB. Regards Jeremy ------ Original Message ------ From: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> To: "Jeremy Ruffer" <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>>; "Xymon mailinglist" <xymon@xymon.com<mailto:xymon@xymon.com>> Sent: 13/09/2024 15:01:46 Subject: RE: [Xymon] Xymon on Ubuntu 24.04 Thanx Jeremy Increased the limit and restarted, but still getting the same line in the logs. Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>> Sent: Friday, 13 September 2024 15:55 To: Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>>; Xymon Mailing List <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Subject: Re: [Xymon] Xymon on Ubuntu 24.04 Hi Chris, You may need to change some memory limits in xymonserver.cfg MAXMSG_CLIENT MAXMSG_STATUS MAXMSG_DATA If you have plenty of memory I would multiply them all by 8. HTH Jeremy ------ Original Message ------ From: "Chris Pretorius via Xymon" <xymon@xymon.com<mailto:xymon@xymon.com>> To: "Xymon Mailing List" <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Sent: 13/09/2024 14:22:38 Subject: [Xymon] Xymon on Ubuntu 24.04 Good day I please need guidance to configure xymon on Ubuntu 24.04 I installed xymon from the default apt repository. It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure. Also changed the repo to the default mirrors.kernel.org<http://mirrors.kernel.org> and installed xymon from there. # apt-cache policy xymon xymon: Installed: 4.3.30-2build3 Candidate: 4.3.30-2build3 Version table: *** 4.3.30-2build3 500 500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs Confirm port 1984 is listening I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638 I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating. **** snip **** 2024-09-13 14:50:52.967847 Peer not up, flushing message queue *** buffer overflow detected ***: terminated 2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6 2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0<http://0.0.0.0:0> failed: Broken pipe **** snip **** This is a fresh install and the only change I made in xymonserver.cfg are: XYMONSERVERIP=”server ip” Firewall disabled Apparmor disabled Thank you. ChrisP _______________________________________________ Xymon mailing list -- xymon@xymon.com<mailto:xymon@xymon.com> To unsubscribe send an email to xymon-leave@xymon.com<mailto:xymon-leave@xymon.com> _______________________________________________ Xymon mailing list -- xymon@xymon.com<mailto:xymon@xymon.com> To unsubscribe send an email to xymon-leave@xymon.com<mailto:xymon-leave@xymon.com>
Hi Jeremy Update I purged xymon* Downloaded xymon-client_4.3.30-1build3_amd64.deb and xymon_4.3.30-1build3_amd64.deb from http://archive.ubuntu.com/ubuntu/ubuntu/pool/universe/x/xymon/ Installed the deb file, # apt-cache policy xymon xymon: Installed: 4.3.30-1build3 Candidate: 4.3.30-2build3 Xymon started, no changes made to configs. Web page opened and all client(local) tests (disk, cpu etc) now displays and the rrd graphs also now get generated. Now see rrd files in /var/lib/xymon/rrd/host/* Best regards ChrisP From: Chris Pretorius via Xymon <xymon@xymon.com> Sent: Saturday, 14 September 2024 20:51 To: Jeremy Laidman <jeremy@laidman.org>; Xymon mailinglist <xymon@xymon.com> Cc: Chris Pretorius <chris.pretorius@coaxle.co.za> Subject: [Xymon] Re: Xymon on Ubuntu 24.04 Hi Jeremy I haven’t pointed any clients to the xymon server as yet. The local xymon-client service is disabled and not running. The xymonclient is configured in the tasks.cfg, I did disable xymonclient but did not solve the problem. The server where im struggling is is 24.04.1 LTS (Noble Numbat) Best regards ChrisP From: Jeremy Laidman <jeremy@laidman.org<mailto:jeremy@laidman.org>> Sent: Saturday, 14 September 2024 03:17 To: Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>>; Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Subject: Re: [Xymon] Re: Xymon on Ubuntu 24.04 Chris Presumably this is a new installation, are there other hosts that have the client installed? Did you install the client package (xymon-client) onto your Xymon server (it won't monitor itself if that's not the case). The bug reporter said that it seemed to work with Ubuntu 22.04.4, but getting the errors on 22.04.1. What sub-release are you running? Cheers Jeremy On Sat, 14 Sept 2024 at 06:13, Tom Schmidt <tom@4schmidts.com<mailto:tom@4schmidts.com>> wrote: Is SELinux enabled on your Ubuntu install? If so, you may need to change it from Enforcing mode to Permissive mode in the /etc/selinux/config file. SELinux will block many of the commands run by Xymon unless they are all explicitly granted permission by SELinux. Tom On Fri, Sep 13, 2024 at 2:07 PM Chris Pretorius via Xymon <xymon@xymon.com<mailto:xymon@xymon.com>> wrote: Hi Jeremy I went berserk and set very high values MAXMSG_CLIENT=4194304 MAXMSG_STATUS=4194304 MAXMSG_DATA=4194304 But the problem is not resolved -------------------------- Output in rrd-status.log with –debug enabled 2024-09-13 21:58:08.000165 Peer at 0.0.0.0:0<http://0.0.0.0:0> failed: Broken pipe 2024-09-13 21:58:13.080151 Peer not up, flushing message queue 13258 2024-09-13 21:58:13.109283 setup_feedback_queue: got ID -1 for key 0xA010D68 13258 2024-09-13 21:58:13.109533 Opening file /usr/lib/xymon/server/etc/rrddefinitions.cfg 13258 2024-09-13 21:58:13.111854 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=4198399 13258 2024-09-13 21:58:13.111894 Got 1856 bytes 13258 2024-09-13 21:58:13.111900 xymond_rrd: Got message 1 @@status#1/xymon.xyz.co.za<http://xymon.xyz.co.za>|1726257493.075018|x.x.x.x||xymon.xyz.co.za<http://xymon.xyz.co.za>|xymongen|1726259293|green||green|1726230891|0||0||1726237717|||0| 13258 2024-09-13 21:58:13.111930 startpos 1856, fillpos 1856, endpos -1 13258 2024-09-13 21:58:13.111969 Transport setup is: 13258 2024-09-13 21:58:13.111995 xymondportnumber = 1984 13258 2024-09-13 21:58:13.111997 xymonproxyhost = NONE 13258 2024-09-13 21:58:13.112043 xymonproxyport = 0 13258 2024-09-13 21:58:13.112045 Recipient listed as 'x.x.x.x' 13258 2024-09-13 21:58:13.112048 Standard protocol on port 1984 13258 2024-09-13 21:58:13.112056 Will connect to address x.x.x.x port 1984 13258 2024-09-13 21:58:13.112726 Connect status is 0 13258 2024-09-13 21:58:13.112769 Sent 16 bytes 13258 2024-09-13 21:58:13.113837 Read 826 bytes 13258 2024-09-13 21:58:13.113861 Closing connection *** buffer overflow detected ***: terminated 2024-09-13 21:58:13.366744 Child process 13258 died: Signal 6 Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>> Sent: Friday, 13 September 2024 16:11 To: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>>; Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>> Subject: Re[2]: [Xymon] Xymon on Ubuntu 24.04 What have you got them set to now? I would double them again and again if needed. There is one slight gotcha here. We had a system where the figure was bytes instead of KB in spite of the comments in the file saying they were KB. Regards Jeremy ------ Original Message ------ From: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> To: "Jeremy Ruffer" <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>>; "Xymon mailinglist" <xymon@xymon.com<mailto:xymon@xymon.com>> Sent: 13/09/2024 15:01:46 Subject: RE: [Xymon] Xymon on Ubuntu 24.04 Thanx Jeremy Increased the limit and restarted, but still getting the same line in the logs. Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>> Sent: Friday, 13 September 2024 15:55 To: Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>>; Xymon Mailing List <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Subject: Re: [Xymon] Xymon on Ubuntu 24.04 Hi Chris, You may need to change some memory limits in xymonserver.cfg MAXMSG_CLIENT MAXMSG_STATUS MAXMSG_DATA If you have plenty of memory I would multiply them all by 8. HTH Jeremy ------ Original Message ------ From: "Chris Pretorius via Xymon" <xymon@xymon.com<mailto:xymon@xymon.com>> To: "Xymon Mailing List" <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Sent: 13/09/2024 14:22:38 Subject: [Xymon] Xymon on Ubuntu 24.04 Good day I please need guidance to configure xymon on Ubuntu 24.04 I installed xymon from the default apt repository. It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure. Also changed the repo to the default mirrors.kernel.org<http://mirrors.kernel.org> and installed xymon from there. # apt-cache policy xymon xymon: Installed: 4.3.30-2build3 Candidate: 4.3.30-2build3 Version table: *** 4.3.30-2build3 500 500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs Confirm port 1984 is listening I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638 I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating. **** snip **** 2024-09-13 14:50:52.967847 Peer not up, flushing message queue *** buffer overflow detected ***: terminated 2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6 2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0<http://0.0.0.0:0> failed: Broken pipe **** snip **** This is a fresh install and the only change I made in xymonserver.cfg are: XYMONSERVERIP=”server ip” Firewall disabled Apparmor disabled Thank you. ChrisP _______________________________________________ Xymon mailing list -- xymon@xymon.com<mailto:xymon@xymon.com> To unsubscribe send an email to xymon-leave@xymon.com<mailto:xymon-leave@xymon.com> _______________________________________________ Xymon mailing list -- xymon@xymon.com<mailto:xymon@xymon.com> To unsubscribe send an email to xymon-leave@xymon.com<mailto:xymon-leave@xymon.com>
Good morning I installed xymon on a Ubuntu24.04 virtual server to make sure this is not an Azure Ubuntu problem. I see the same problems on the new install. Seems the problem is on the package provided on the Ubuntu 24.04 repo’s xymon/noble,now 4.3.30-2build3 but xymon/jammy,now 4.3.30-1build3 is 100%. I guess there won’t be any quick fix coming soon. Best regards From: Chris Pretorius <chris.pretorius@coaxle.co.za> Sent: Sunday, 15 September 2024 09:55 To: Xymon mailinglist <xymon@xymon.com>; Jeremy Laidman <jeremy@laidman.org> Subject: RE: [Xymon] Re: Xymon on Ubuntu 24.04 Hi Jeremy Update I purged xymon* Downloaded xymon-client_4.3.30-1build3_amd64.deb and xymon_4.3.30-1build3_amd64.deb from http://archive.ubuntu.com/ubuntu/ubuntu/pool/universe/x/xymon/ Installed the deb file, # apt-cache policy xymon xymon: Installed: 4.3.30-1build3 Candidate: 4.3.30-2build3 Xymon started, no changes made to configs. Web page opened and all client(local) tests (disk, cpu etc) now displays and the rrd graphs also now get generated. Now see rrd files in /var/lib/xymon/rrd/host/* Best regards ChrisP From: Chris Pretorius via Xymon <xymon@xymon.com<mailto:xymon@xymon.com>> Sent: Saturday, 14 September 2024 20:51 To: Jeremy Laidman <jeremy@laidman.org<mailto:jeremy@laidman.org>>; Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Subject: [Xymon] Re: Xymon on Ubuntu 24.04 Hi Jeremy I haven’t pointed any clients to the xymon server as yet. The local xymon-client service is disabled and not running. The xymonclient is configured in the tasks.cfg, I did disable xymonclient but did not solve the problem. The server where im struggling is is 24.04.1 LTS (Noble Numbat) Best regards ChrisP From: Jeremy Laidman <jeremy@laidman.org<mailto:jeremy@laidman.org>> Sent: Saturday, 14 September 2024 03:17 To: Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>>; Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Subject: Re: [Xymon] Re: Xymon on Ubuntu 24.04 Chris Presumably this is a new installation, are there other hosts that have the client installed? Did you install the client package (xymon-client) onto your Xymon server (it won't monitor itself if that's not the case). The bug reporter said that it seemed to work with Ubuntu 22.04.4, but getting the errors on 22.04.1. What sub-release are you running? Cheers Jeremy On Sat, 14 Sept 2024 at 06:13, Tom Schmidt <tom@4schmidts.com<mailto:tom@4schmidts.com>> wrote: Is SELinux enabled on your Ubuntu install? If so, you may need to change it from Enforcing mode to Permissive mode in the /etc/selinux/config file. SELinux will block many of the commands run by Xymon unless they are all explicitly granted permission by SELinux. Tom On Fri, Sep 13, 2024 at 2:07 PM Chris Pretorius via Xymon <xymon@xymon.com<mailto:xymon@xymon.com>> wrote: Hi Jeremy I went berserk and set very high values MAXMSG_CLIENT=4194304 MAXMSG_STATUS=4194304 MAXMSG_DATA=4194304 But the problem is not resolved -------------------------- Output in rrd-status.log with –debug enabled 2024-09-13 21:58:08.000165 Peer at 0.0.0.0:0<http://0.0.0.0:0> failed: Broken pipe 2024-09-13 21:58:13.080151 Peer not up, flushing message queue 13258 2024-09-13 21:58:13.109283 setup_feedback_queue: got ID -1 for key 0xA010D68 13258 2024-09-13 21:58:13.109533 Opening file /usr/lib/xymon/server/etc/rrddefinitions.cfg 13258 2024-09-13 21:58:13.111854 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=4198399 13258 2024-09-13 21:58:13.111894 Got 1856 bytes 13258 2024-09-13 21:58:13.111900 xymond_rrd: Got message 1 @@status#1/xymon.xyz.co.za<http://xymon.xyz.co.za>|1726257493.075018|x.x.x.x||xymon.xyz.co.za<http://xymon.xyz.co.za>|xymongen|1726259293|green||green|1726230891|0||0||1726237717|||0| 13258 2024-09-13 21:58:13.111930 startpos 1856, fillpos 1856, endpos -1 13258 2024-09-13 21:58:13.111969 Transport setup is: 13258 2024-09-13 21:58:13.111995 xymondportnumber = 1984 13258 2024-09-13 21:58:13.111997 xymonproxyhost = NONE 13258 2024-09-13 21:58:13.112043 xymonproxyport = 0 13258 2024-09-13 21:58:13.112045 Recipient listed as 'x.x.x.x' 13258 2024-09-13 21:58:13.112048 Standard protocol on port 1984 13258 2024-09-13 21:58:13.112056 Will connect to address x.x.x.x port 1984 13258 2024-09-13 21:58:13.112726 Connect status is 0 13258 2024-09-13 21:58:13.112769 Sent 16 bytes 13258 2024-09-13 21:58:13.113837 Read 826 bytes 13258 2024-09-13 21:58:13.113861 Closing connection *** buffer overflow detected ***: terminated 2024-09-13 21:58:13.366744 Child process 13258 died: Signal 6 Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>> Sent: Friday, 13 September 2024 16:11 To: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>>; Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>> Subject: Re[2]: [Xymon] Xymon on Ubuntu 24.04 What have you got them set to now? I would double them again and again if needed. There is one slight gotcha here. We had a system where the figure was bytes instead of KB in spite of the comments in the file saying they were KB. Regards Jeremy ------ Original Message ------ From: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> To: "Jeremy Ruffer" <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>>; "Xymon mailinglist" <xymon@xymon.com<mailto:xymon@xymon.com>> Sent: 13/09/2024 15:01:46 Subject: RE: [Xymon] Xymon on Ubuntu 24.04 Thanx Jeremy Increased the limit and restarted, but still getting the same line in the logs. Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>> Sent: Friday, 13 September 2024 15:55 To: Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>>; Xymon Mailing List <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Subject: Re: [Xymon] Xymon on Ubuntu 24.04 Hi Chris, You may need to change some memory limits in xymonserver.cfg MAXMSG_CLIENT MAXMSG_STATUS MAXMSG_DATA If you have plenty of memory I would multiply them all by 8. HTH Jeremy ------ Original Message ------ From: "Chris Pretorius via Xymon" <xymon@xymon.com<mailto:xymon@xymon.com>> To: "Xymon Mailing List" <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Sent: 13/09/2024 14:22:38 Subject: [Xymon] Xymon on Ubuntu 24.04 Good day I please need guidance to configure xymon on Ubuntu 24.04 I installed xymon from the default apt repository. It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure. Also changed the repo to the default mirrors.kernel.org<http://mirrors.kernel.org> and installed xymon from there. # apt-cache policy xymon xymon: Installed: 4.3.30-2build3 Candidate: 4.3.30-2build3 Version table: *** 4.3.30-2build3 500 500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs Confirm port 1984 is listening I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638 I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating. **** snip **** 2024-09-13 14:50:52.967847 Peer not up, flushing message queue *** buffer overflow detected ***: terminated 2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6 2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0<http://0.0.0.0:0> failed: Broken pipe **** snip **** This is a fresh install and the only change I made in xymonserver.cfg are: XYMONSERVERIP=”server ip” Firewall disabled Apparmor disabled Thank you. ChrisP _______________________________________________ Xymon mailing list -- xymon@xymon.com<mailto:xymon@xymon.com> To unsubscribe send an email to xymon-leave@xymon.com<mailto:xymon-leave@xymon.com> _______________________________________________ Xymon mailing list -- xymon@xymon.com<mailto:xymon@xymon.com> To unsubscribe send an email to xymon-leave@xymon.com<mailto:xymon-leave@xymon.com>
Thanks for the update Chris. I wasn't aware that the Xymon packages were available through the Ubuntu repositories (as I mainly work with Red Hat Linux). I generally add the Terabithia repo and just use that, knowing that it's almost certainly going to have the most recent builds with bug fixes. It would be good to provide feedback to the Ubuntu package maintainer, if that's relatively easy to do. Cheers Jeremy On Mon, 16 Sept 2024 at 18:31, Chris Pretorius <chris.pretorius@coaxle.co.za> wrote:
Good morning
I installed xymon on a Ubuntu24.04 virtual server to make sure this is not an Azure Ubuntu problem.
I see the same problems on the new install.
Seems the problem is on the package provided on the Ubuntu 24.04 repo’s
xymon/noble,now 4.3.30-2build3
but xymon/jammy,now 4.3.30-1build3 is 100%.
I guess there won’t be any quick fix coming soon.
Best regards
*From:* Chris Pretorius <chris.pretorius@coaxle.co.za> *Sent:* Sunday, 15 September 2024 09:55 *To:* Xymon mailinglist <xymon@xymon.com>; Jeremy Laidman < jeremy@laidman.org> *Subject:* RE: [Xymon] Re: Xymon on Ubuntu 24.04
Hi Jeremy
Update
I purged xymon*
Downloaded xymon-client_4.3.30-1build3_amd64.deb and xymon_4.3.30-1build3_amd64.deb from http://archive.ubuntu.com/ubuntu/ubuntu/pool/universe/x/xymon/
Installed the deb file,
# apt-cache policy xymon
xymon:
Installed: 4.3.30-1build3
Candidate: 4.3.30-2build3
Xymon started, no changes made to configs.
Web page opened and all client(local) tests (disk, cpu etc) now displays and the rrd graphs also now get generated.
Now see rrd files in /var/lib/xymon/rrd/host/*
Best regards
ChrisP
*From:* Chris Pretorius via Xymon <xymon@xymon.com> *Sent:* Saturday, 14 September 2024 20:51 *To:* Jeremy Laidman <jeremy@laidman.org>; Xymon mailinglist < xymon@xymon.com> *Cc:* Chris Pretorius <chris.pretorius@coaxle.co.za> *Subject:* [Xymon] Re: Xymon on Ubuntu 24.04
Hi Jeremy
I haven’t pointed any clients to the xymon server as yet.
The local xymon-client service is disabled and not running.
The xymonclient is configured in the tasks.cfg, I did disable xymonclient but did not solve the problem.
The server where im struggling is is 24.04.1 LTS (Noble Numbat)
Best regards
ChrisP
*From:* Jeremy Laidman <jeremy@laidman.org> *Sent:* Saturday, 14 September 2024 03:17 *To:* Xymon mailinglist <xymon@xymon.com>; Chris Pretorius < chris.pretorius@coaxle.co.za> *Subject:* Re: [Xymon] Re: Xymon on Ubuntu 24.04
Chris
Presumably this is a new installation, are there other hosts that have the client installed? Did you install the client package (xymon-client) onto your Xymon server (it won't monitor itself if that's not the case).
The bug reporter said that it seemed to work with Ubuntu 22.04.4, but getting the errors on 22.04.1. What sub-release are you running?
Cheers
Jeremy
On Sat, 14 Sept 2024 at 06:13, Tom Schmidt <tom@4schmidts.com> wrote:
Is SELinux enabled on your Ubuntu install? If so, you may need to change it from Enforcing mode to Permissive mode in the /etc/selinux/config file. SELinux will block many of the commands run by Xymon unless they are all explicitly granted permission by SELinux.
Tom
On Fri, Sep 13, 2024 at 2:07 PM Chris Pretorius via Xymon <xymon@xymon.com> wrote:
Hi Jeremy
I went berserk and set very high values
MAXMSG_CLIENT=4194304
MAXMSG_STATUS=4194304
MAXMSG_DATA=4194304
But the problem is not resolved
--------------------------
Output in rrd-status.log with –debug enabled
2024-09-13 21:58:08.000165 Peer at 0.0.0.0:0 failed: Broken pipe
2024-09-13 21:58:13.080151 Peer not up, flushing message queue
13258 2024-09-13 21:58:13.109283 setup_feedback_queue: got ID -1 for key 0xA010D68
13258 2024-09-13 21:58:13.109533 Opening file /usr/lib/xymon/server/etc/rrddefinitions.cfg
13258 2024-09-13 21:58:13.111854 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=4198399
13258 2024-09-13 21:58:13.111894 Got 1856 bytes
13258 2024-09-13 21:58:13.111900 xymond_rrd: Got message 1 @@status#1/ xymon.xyz.co.za|1726257493.075018|x.x.x.x||xymon.xyz.co.za |xymongen|1726259293|green||green|1726230891|0||0||1726237717|||0|
13258 2024-09-13 21:58:13.111930 startpos 1856, fillpos 1856, endpos -1
13258 2024-09-13 21:58:13.111969 Transport setup is:
13258 2024-09-13 21:58:13.111995 xymondportnumber = 1984
13258 2024-09-13 21:58:13.111997 xymonproxyhost = NONE
13258 2024-09-13 21:58:13.112043 xymonproxyport = 0
13258 2024-09-13 21:58:13.112045 Recipient listed as 'x.x.x.x'
13258 2024-09-13 21:58:13.112048 Standard protocol on port 1984
13258 2024-09-13 21:58:13.112056 Will connect to address x.x.x.x port 1984
13258 2024-09-13 21:58:13.112726 Connect status is 0
13258 2024-09-13 21:58:13.112769 Sent 16 bytes
13258 2024-09-13 21:58:13.113837 Read 826 bytes
13258 2024-09-13 21:58:13.113861 Closing connection
*** buffer overflow detected ***: terminated
2024-09-13 21:58:13.366744 Child process 13258 died: Signal 6
Best regards
*From:* Jeremy Ruffer <jeremy.ruffer@gmail.com> *Sent:* Friday, 13 September 2024 16:11 *To:* Chris Pretorius <chris.pretorius@coaxle.co.za>; Xymon mailinglist < xymon@xymon.com> *Subject:* Re[2]: [Xymon] Xymon on Ubuntu 24.04
What have you got them set to now?
I would double them again and again if needed.
There is one slight gotcha here. We had a system where the figure was bytes instead of KB in spite of the comments in the file saying they were KB.
Regards
Jeremy
------ Original Message ------
From: "Chris Pretorius" <chris.pretorius@coaxle.co.za>
To: "Jeremy Ruffer" <jeremy.ruffer@gmail.com>; "Xymon mailinglist" < xymon@xymon.com>
Sent: 13/09/2024 15:01:46
Subject: RE: [Xymon] Xymon on Ubuntu 24.04
Thanx Jeremy
Increased the limit and restarted, but still getting the same line in the logs.
Best regards
*From:* Jeremy Ruffer <jeremy.ruffer@gmail.com> *Sent:* Friday, 13 September 2024 15:55 *To:* Xymon mailinglist <xymon@xymon.com>; Xymon Mailing List < xymon@xymon.com> *Cc:* Chris Pretorius <chris.pretorius@coaxle.co.za> *Subject:* Re: [Xymon] Xymon on Ubuntu 24.04
Hi Chris,
You may need to change some memory limits in xymonserver.cfg
MAXMSG_CLIENT
MAXMSG_STATUS
MAXMSG_DATA
If you have plenty of memory I would multiply them all by 8.
HTH
Jeremy
------ Original Message ------
From: "Chris Pretorius via Xymon" <xymon@xymon.com>
To: "Xymon Mailing List" <xymon@xymon.com>
Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za>
Sent: 13/09/2024 14:22:38
Subject: [Xymon] Xymon on Ubuntu 24.04
Good day
I please need guidance to configure xymon on Ubuntu 24.04
I installed xymon from the default apt repository.
It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure.
Also changed the repo to the default mirrors.kernel.org and installed xymon from there.
# apt-cache policy xymon
xymon:
Installed: 4.3.30-2build3
Candidate: 4.3.30-2build3
Version table:
*** 4.3.30-2build3 500
500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages
100 /var/lib/dpkg/status
Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs
Confirm port 1984 is listening
I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638
I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating.
**** snip ****
2024-09-13 14:50:52.967847 Peer not up, flushing message queue
*** buffer overflow detected ***: terminated
2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6
2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0 failed: Broken pipe
**** snip ****
This is a fresh install and the only change I made in xymonserver.cfg are:
XYMONSERVERIP=”server ip”
Firewall disabled
Apparmor disabled
Thank you.
ChrisP
_______________________________________________ Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
_______________________________________________ Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
On 16/09/2024 10:45, Jeremy Laidman wrote:
It would be good to provide feedback to the Ubuntu package maintainer, if that's relatively easy to do.
The original bug report here looks to be the same as that posted in the following Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638
so it would be helpful to add any extra observations/attempted trouble shooting steps to that bug report. Other affected Ubuntu users can also click the "does this bug affect you?" link if they have the same problem, as that helps to indicate there might be a problem with the package.
Adam
Hi Adam
I did tick the "does this bug affect you", so far only 4 people are listed on the this bug affect you list.
Best regards
ChrisP
-----Original Message----- From: Adam Thorn via Xymon <xymon@xymon.com> Sent: Monday, 23 September 2024 10:17 To: xymon@xymon.com Cc: Adam Thorn <alt36@cam.ac.uk> Subject: [Xymon] Re: Xymon on Ubuntu 24.04
On 16/09/2024 10:45, Jeremy Laidman wrote:
It would be good to provide feedback to the Ubuntu package maintainer, if that's relatively easy to do.
The original bug report here looks to be the same as that posted in the following Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638
so it would be helpful to add any extra observations/attempted trouble shooting steps to that bug report. Other affected Ubuntu users can also click the "does this bug affect you?" link if they have the same problem, as that helps to indicate there might be a problem with the package.
Adam
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Hi Tom SELinux isn’t installed, apparmor is disabled and not running. # aa-status apparmor module is loaded. apparmor filesystem is not mounted. Best regards ChrisP From: Tom Schmidt <tom@4schmidts.com> Sent: Friday, 13 September 2024 22:13 To: Xymon mailinglist <xymon@xymon.com> Cc: Jeremy Ruffer <jeremy.ruffer@gmail.com>; Chris Pretorius <chris.pretorius@coaxle.co.za> Subject: Re: [Xymon] Re: Xymon on Ubuntu 24.04 You don't often get email from tom@4schmidts.com<mailto:tom@4schmidts.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Is SELinux enabled on your Ubuntu install? If so, you may need to change it from Enforcing mode to Permissive mode in the /etc/selinux/config file. SELinux will block many of the commands run by Xymon unless they are all explicitly granted permission by SELinux. Tom On Fri, Sep 13, 2024 at 2:07 PM Chris Pretorius via Xymon <xymon@xymon.com<mailto:xymon@xymon.com>> wrote: Hi Jeremy I went berserk and set very high values MAXMSG_CLIENT=4194304 MAXMSG_STATUS=4194304 MAXMSG_DATA=4194304 But the problem is not resolved -------------------------- Output in rrd-status.log with –debug enabled 2024-09-13 21:58:08.000165 Peer at 0.0.0.0:0<http://0.0.0.0:0> failed: Broken pipe 2024-09-13 21:58:13.080151 Peer not up, flushing message queue 13258 2024-09-13 21:58:13.109283 setup_feedback_queue: got ID -1 for key 0xA010D68 13258 2024-09-13 21:58:13.109533 Opening file /usr/lib/xymon/server/etc/rrddefinitions.cfg 13258 2024-09-13 21:58:13.111854 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=4198399 13258 2024-09-13 21:58:13.111894 Got 1856 bytes 13258 2024-09-13 21:58:13.111900 xymond_rrd: Got message 1 @@status#1/xymon.xyz.co.za<http://xymon.xyz.co.za>|1726257493.075018|x.x.x.x||xymon.xyz.co.za<http://xymon.xyz.co.za>|xymongen|1726259293|green||green|1726230891|0||0||1726237717|||0| 13258 2024-09-13 21:58:13.111930 startpos 1856, fillpos 1856, endpos -1 13258 2024-09-13 21:58:13.111969 Transport setup is: 13258 2024-09-13 21:58:13.111995 xymondportnumber = 1984 13258 2024-09-13 21:58:13.111997 xymonproxyhost = NONE 13258 2024-09-13 21:58:13.112043 xymonproxyport = 0 13258 2024-09-13 21:58:13.112045 Recipient listed as 'x.x.x.x' 13258 2024-09-13 21:58:13.112048 Standard protocol on port 1984 13258 2024-09-13 21:58:13.112056 Will connect to address x.x.x.x port 1984 13258 2024-09-13 21:58:13.112726 Connect status is 0 13258 2024-09-13 21:58:13.112769 Sent 16 bytes 13258 2024-09-13 21:58:13.113837 Read 826 bytes 13258 2024-09-13 21:58:13.113861 Closing connection *** buffer overflow detected ***: terminated 2024-09-13 21:58:13.366744 Child process 13258 died: Signal 6 Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>> Sent: Friday, 13 September 2024 16:11 To: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>>; Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>> Subject: Re[2]: [Xymon] Xymon on Ubuntu 24.04 What have you got them set to now? I would double them again and again if needed. There is one slight gotcha here. We had a system where the figure was bytes instead of KB in spite of the comments in the file saying they were KB. Regards Jeremy ------ Original Message ------ From: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> To: "Jeremy Ruffer" <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>>; "Xymon mailinglist" <xymon@xymon.com<mailto:xymon@xymon.com>> Sent: 13/09/2024 15:01:46 Subject: RE: [Xymon] Xymon on Ubuntu 24.04 Thanx Jeremy Increased the limit and restarted, but still getting the same line in the logs. Best regards From: Jeremy Ruffer <jeremy.ruffer@gmail.com<mailto:jeremy.ruffer@gmail.com>> Sent: Friday, 13 September 2024 15:55 To: Xymon mailinglist <xymon@xymon.com<mailto:xymon@xymon.com>>; Xymon Mailing List <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: Chris Pretorius <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Subject: Re: [Xymon] Xymon on Ubuntu 24.04 Hi Chris, You may need to change some memory limits in xymonserver.cfg MAXMSG_CLIENT MAXMSG_STATUS MAXMSG_DATA If you have plenty of memory I would multiply them all by 8. HTH Jeremy ------ Original Message ------ From: "Chris Pretorius via Xymon" <xymon@xymon.com<mailto:xymon@xymon.com>> To: "Xymon Mailing List" <xymon@xymon.com<mailto:xymon@xymon.com>> Cc: "Chris Pretorius" <chris.pretorius@coaxle.co.za<mailto:chris.pretorius@coaxle.co.za>> Sent: 13/09/2024 14:22:38 Subject: [Xymon] Xymon on Ubuntu 24.04 Good day I please need guidance to configure xymon on Ubuntu 24.04 I installed xymon from the default apt repository. It’s a VM running in Azure and installed using the repo that was setup for a Ubuntu vem on azure. Also changed the repo to the default mirrors.kernel.org<http://mirrors.kernel.org> and installed xymon from there. # apt-cache policy xymon xymon: Installed: 4.3.30-2build3 Candidate: 4.3.30-2build3 Version table: *** 4.3.30-2build3 500 500 https://mirrors.kernel.org/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs Confirm port 1984 is listening I see a bug was also recently reported here https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638 I see similar entries in the xymon {clientdata.log, rrd-status.log alert.log } files, repeating. **** snip **** 2024-09-13 14:50:52.967847 Peer not up, flushing message queue *** buffer overflow detected ***: terminated 2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6 2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0<http://0.0.0.0:0> failed: Broken pipe **** snip **** This is a fresh install and the only change I made in xymonserver.cfg are: XYMONSERVERIP=”server ip” Firewall disabled Apparmor disabled Thank you. ChrisP _______________________________________________ Xymon mailing list -- xymon@xymon.com<mailto:xymon@xymon.com> To unsubscribe send an email to xymon-leave@xymon.com<mailto:xymon-leave@xymon.com>
Hi Chris!
As the Debian developer who released 4.3.30-2, I'll try to help here, but I'm not sure, whether I can help, since I didn't try this out on Ubuntu yet but only on Debian 12.
apt-cache policy xymon
xymon: Installed: 4.3.30-2build3
Okay, this should be 4.3.30-2 without changes but only re-build on Ubuntu.
I hope that you have xymon-client installed, too?
Xymon does start and generates the pages which I can view but is missing the client tests (disk, cpu, memory etc..), and the rrd graphs Confirm port 1984 is listening
Okay, just tried this myself on a freshly installed Debian 12 (with 4.3.30-2 backported to Debian 12). I first had to install apache2 first, otherwise enabling mod rewrite and xymon conf may have been done by hand. Then I installed xymon and xymon-client and used 127.0.0.1 as "Xymon server" via debconf (as well as the FQDN of the server as "Client hostname") on installation of xymon-client.
**** snip **** 2024-09-13 14:50:52.967847 Peer not up, flushing message queue *** buffer overflow detected ***: terminated 2024-09-13 14:50:53.187820 Child process 5496 died: Signal 6 2024-09-13 14:51:52.977025 Peer at 0.0.0.0:0 failed: Broken pipe **** snip ****
Hmmm, I doesn't observe these on Debian, maybe Ubuntu uses some other type of hardening, which breaks the package or there is some other build problem?
This is a fresh install and the only change I made in xymonserver.cfg are: XYMONSERVERIP="server ip"
Why do you do so? The idea of the configuration is that you define the Xymon server IP via debconf when installing xymon-client, which sets XYMONSERVERS="127.0.0.1" (or a different IP) in /etc/default/xymon-client This variable is used as the server IP automatically.
With this setup xymon comes up and I see the client tests and after some cycles also some data in the graphs. Works without problems for me.
Maybe I really have to try this out with Ubuntu 24.04...
[...]
Okay, I now have a minimal Ubuntu 24.04 server installed, installed apache2 and xymon (including xymon-client). Again I used 127.0.0.1 as the server IP (which is written to /etc/defaults/xymon-client). And now I can reproduce your issue. I see no local data fields (disk, cpu,...) and I see "buffer overflow detected" messages in the logs.
Comparing "systemctl status xymon" I see, that 2*xymond_rrd, xymond_client, xymond_alert are missing (AKA not running) on the Ubuntu server, seems that this are the processes that had a buffer overflow.
So I tried to re-compile 4.3.30-2 on this server, but the result didn't change (still does not work as expected).
Since you wrote, that 4.3.30-1build3 (from Ubuntu 23.10) worked without problems, I downloaded the source of 4.3.30-1 and did another build but this also doesn't work without problems.
So from my perspective there is some problem with the compile options or hardening in Ubuntu 24.04, which breaks the xymon package, while 4.3.30-1build3 used a different build system (Ubuntu 23.10), which wasn't that strict and didn't run into issues.
Maybe I should compare compiler options between Ubuntu 24.04 and Debian 12 (and/or Debian unstable) and try to reproduce the issue on Debian. Or I should try to find out, where the "buffer overflow detected" messages come from and fix the root cause. But that's a job for another day...
Sorry not to have a solution for you now, but this seems to be harder to fix...
Greetings Roland
Hi!
On Mon, 23 Sep 2024, I wrote:
So from my perspective there is some problem with the compile options or hardening in Ubuntu 24.04, which breaks the xymon package, while 4.3.30-1build3 used a different build system (Ubuntu 23.10), which wasn't that strict and didn't run into issues.
Maybe I should compare compiler options between Ubuntu 24.04 and Debian 12 (and/or Debian unstable) and try to reproduce the issue on Debian. Or I should try to find out, where the "buffer overflow detected" messages come from and fix the root cause. But that's a job for another day...
Today I dug a bit deeper and found out that the relevant difference between Debian unstable and Ubuntu 24.04 is, that Ubuntu uses -D_FORTIFY_SOURCE=3 since 24.04, while Debian still uses -D_FORTIFY_SOURCE=2.
dpkg-dpkg-buildflags --get CPPFLAGS shows this difference: Debian unstable: -Wdate-time -D_FORTIFY_SOURCE=2 Ubuntu 24.04: -Wdate-time -D_FORTIFY_SOURCE=3
To change this behavior just set environment variable DEB_CPPFLAGS_MAINT_SET="-Wdate-time -D_FORTIFY_SOURCE=2" on Ubuntu or DEB_CPPFLAGS_MAINT_SET="-Wdate-time -D_FORTIFY_SOURCE=3" on Debian
This doesn't fix the issue bug shows the problem trigger: FORTIFY_SOURCE=3 implements better fortification and more security regarding to buffer overflows, but there seem to be some bugs in xymon sources, that trigger these checks and stop some modules working.
Next step would be digging deeper and finding the root causes of these buffer overflows and to fix them, maybe some upstream xymon developer, since my C skills are quite limited :-(
Greetings Roland
On Tue, 24 Sep 2024, I wrote:
Next step would be digging deeper and finding the root causes of these buffer overflows and to fix them, maybe some upstream xymon developer, since my C skills are quite limited :-(
According to systemd coredumpctl we have at least coredumps in xymond_client, xymond_rrd and xymond_alert. Here is the output of gdb bt full for them (maybe someone else understands more of what the root cause is): xymond_client: ============== #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 tid = <optimized out> ret = 0 pd = <optimized out> old_mask = {__val = {0}} ret = <optimized out> #1 0x00007fd7c6fe1e9f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 No locals. #2 0x00007fd7c6f92fb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 ret = <optimized out> #3 0x00007fd7c6f7d472 in __GI_abort () at ./stdlib/abort.c:79 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, sa_mask = {__val = {0, 0, 0, 0, 0, 0, 0, 0, 140721929553312, 3558782228032748576, 1675727637748588544, 94097479924736, 94097479924736, 140721929553552, 94097479835289, 140721929553696}}, sa_flags = 2, sa_restorer = 0x7ffc609f85a0} #4 0x00007fd7c6fd6430 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fd7c70f0210 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:155 ap = {{gp_offset = 24, fp_offset = 0, overflow_arg_area = 0x7ffc609f86f0, reg_save_area = 0x7ffc609f8680}} fd = <optimized out> list = <optimized out> nlist = <optimized out> cp = <optimized out> #5 0x00007fd7c706f0f2 in __GI___fortify_fail (msg=msg@entry=0x7fd7c70f01b6 "buffer overflow detected") at ./debug/fortify_fail.c:26 No locals. #6 0x00007fd7c706dc00 in __GI___chk_fail () at ./debug/chk_fail.c:28 No locals. #7 0x00007fd7c706d835 in ___snprintf_chk (s=s@entry=0x5594c6dd7c02 <md_string+2> "", maxlen=maxlen@entry=35, flag=flag@entry=2, slen=slen@entry=31, format=format@entry=0x5594c6dc1e99 "%02x") at ./debug/snprintf_chk.c:29 mode = <optimized out> ap = {{gp_offset = 48, fp_offset = 48, overflow_arg_area = 0x7ffc609f8800, reg_save_area = 0x7ffc609f8740}} ret = <optimized out> #8 0x00005594c6db7581 in snprintf (__fmt=0x5594c6dc1e99 "%02x", __n=35, __s=0x5594c6dd7c02 <md_string+2> "") at /usr/include/x86_64-linux-gnu/bits/stdio2.h:54 No locals. #9 md5hash ( input=input@entry=0x5594c83023e0 "#\n# Master configuration file for Xymon\n#\n# This file defines several things:\n#\n# 1) By adding hosts to this file, you define hosts that are monitored by Xymon\n# 2) By adding \"page\", \"subpage\", \"group"...) at ./lib/digest.c:44 ctx = 0x5594c83023a0 md_value = "\301tJ\342^\312T\032bGjɨ\f\267I" md_string = "c1", '\000' <repeats 30 times> i = 1 p = 0x5594c6dd7c02 <md_string+2> "" #10 0x00005594c6db2c39 in prepare_fromnet () at ./lib/loadhosts_file.c:104 sres = 0x5594c83023a0 sendstat = <optimized out> fdata = 0x5594c83023e0 "#\n# Master configuration file for Xymon\n#\n# This file defines several things:\n#\n# 1) By adding hosts to this file, you define hosts that are monitored by Xymon\n# 2) By adding \"page\", \"subpage\", \"group"... fhash = <optimized out> contentmd5 = '\000' <repeats 32 times> sres = <optimized out> sendstat = <optimized out> fdata = <optimized out> fhash = <optimized out> #11 load_hostnames (hostsfn=0x7ffc609fb889 "/usr/lib/xymon/server/etc/hosts.cfg", extrainclude=extrainclude@entry=0x0, fqdn=fqdn@entry=1) at ./lib/loadhosts_file.c:142 prepresult = <optimized out> ip1 = 0 ip2 = 0 ip3 = 0 ip4 = 0 groupid = <optimized out> pageidx = <optimized out> hostname = '\000' <repeats 40 times>, "z\033\036\307\327\177\000\000\000\000\000\000\000\000\000\000\300\215\237`\374\177\000\000 \220 \307\327\177\000\000h\345\035\307\327\177\000\000\006\000\000\000\004\000\000\000@\000\000\000\000\000\000\000@\000\000\000\000\000\000\000@\000\000\000\000\000\000\000\020\003\000\000\000\000\000\000\020\003\000\000\000\000\000\000\b\000\000\000\000\000\000\000\003\000\000\000\004\000\000\000\360\n\032\000\000\000\000\000\360\n\032\000\000\000\000\000\360\n\032\000\000\000\000\000\034\000\000\000\000\000\000\000\034\000\000\000\000\000\000\000\020\000\000\000\000\000\000\000\001\000\000\000\004", '\000' <repeats 27 times>... dgname = 0x0 dgname_buflen = 0 curtoppage = <optimized out> curpage = <optimized out> pgtail = <optimized out> htree = <optimized out> cfgdata = <optimized out> inbol = <optimized out> ineol = <optimized out> insavchar = 0 '\000' #12 0x00005594c6d83b59 in main (argc=<optimized out>, argv=0x7ffc609f9c48) at ./xymond/xymond_client.c:2181 eoln = <optimized out> restofmsg = <optimized out> p = <optimized out> metadata = {0x41564952 <error: Cannot access memory at address 0x41564952>, 0x0, 0x62696c5f5f004554 <error: Cannot access memory at address 0x62696c5f5f004554>, 0x5f796c7261655f63 <error: Cannot access memory at address 0x5f796c7261655f63>, 0x60 <error: Cannot access memory at address 0x60>, 0x0, 0x18 <error: Cannot access memory at address 0x18>, 0x0 <repeats 14 times>} metacount = <optimized out> nowtimer = 308 msg = 0x7fd7c6ed2010 "@@client#1/xymon12.sail.spinnaker.de|1727205554.416384|127.0.0.1|xymon12.sail.spinnaker.de|linux|linux|\nclient xymon12,sail,spinnaker,de.linux linux\n[date]\nTue Sep 24 21:19:09 CEST 2024\n[uname]\nLinux "... running = 1 argi = <optimized out> seq = 1 sa = {__sigaction_handler = {sa_handler = 0x5594c6d84450 <sig_handler>, sa_sigaction = 0x5594c6d84450 <sig_handler>}, sa_mask = {__val = {0 <repeats 16 times>}}, sa_flags = 0, sa_restorer = 0x0} nextconfigload = 908 configfn = <optimized out> collectors = 0x5594c83022a0 xymond_rrd: =========== #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 tid = <optimized out> ret = 0 pd = <optimized out> old_mask = {__val = {0}} ret = <optimized out> #1 0x00007f892b9cee9f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 No locals. #2 0x00007f892b97ffb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 ret = <optimized out> #3 0x00007f892b96a472 in __GI_abort () at ./stdlib/abort.c:79 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, sa_mask = {__val = {0, 0, 0, 0, 0, 0, 0, 0, 140720416982192, 3558782991895767008, 8200057225952544256, 94861342943168, 94861342943168, 140720416982432, 94861342820529, 140720416982576}}, sa_flags = 2, sa_restorer = 0x7ffc067784b0} #4 0x00007f892b9c3430 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f892badd210 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:155 ap = {{gp_offset = 24, fp_offset = 0, overflow_arg_area = 0x7ffc06778600, reg_save_area = 0x7ffc06778590}} fd = <optimized out> list = <optimized out> nlist = <optimized out> cp = <optimized out> #5 0x00007f892ba5c0f2 in __GI___fortify_fail (msg=msg@entry=0x7f892badd1b6 "buffer overflow detected") at ./debug/fortify_fail.c:26 No locals. #6 0x00007f892ba5ac00 in __GI___chk_fail () at ./debug/chk_fail.c:28 No locals. #7 0x00007f892ba5a835 in ___snprintf_chk (s=s@entry=0x5646a0a627c2 <md_string+2> "", maxlen=maxlen@entry=35, flag=flag@entry=2, slen=slen@entry=31, format=format@entry=0x5646a0a448b1 "%02x") at ./debug/snprintf_chk.c:29 mode = <optimized out> ap = {{gp_offset = 48, fp_offset = 48, overflow_arg_area = 0x7ffc06778710, reg_save_area = 0x7ffc06778650}} ret = <optimized out> #8 0x00005646a0a2a481 in snprintf (__fmt=0x5646a0a448b1 "%02x", __n=35, __s=0x5646a0a627c2 <md_string+2> "") at /usr/include/x86_64-linux-gnu/bits/stdio2.h:54 No locals. #9 md5hash ( input=input@entry=0x5646a26010d0 "#\n# Master configuration file for Xymon\n#\n# This file defines several things:\n#\n# 1) By adding hosts to this file, you define hosts that are monitored by Xymon\n# 2) By adding \"page\", \"subpage\", \"group"...) at ./lib/digest.c:44 ctx = 0x5646a26000c0 md_value = "\301tJ\342^\312T\032bGjɨ\f\267I" md_string = "c1", '\000' <repeats 30 times> i = 1 p = 0x5646a0a627c2 <md_string+2> "" #10 0x00005646a0a3d699 in prepare_fromnet () at ./lib/loadhosts_file.c:104 sres = 0x5646a26000c0 sendstat = <optimized out> fdata = 0x5646a26010d0 "#\n# Master configuration file for Xymon\n#\n# This file defines several things:\n#\n# 1) By adding hosts to this file, you define hosts that are monitored by Xymon\n# 2) By adding \"page\", \"subpage\", \"group"... fhash = <optimized out> contentmd5 = '\000' <repeats 32 times> sres = <optimized out> sendstat = <optimized out> fdata = <optimized out> fhash = <optimized out> #11 load_hostnames (hostsfn=0x7ffc0677f88c "/usr/lib/xymon/server/etc/hosts.cfg", extrainclude=extrainclude@entry=0x0, fqdn=fqdn@entry=1) at ./lib/loadhosts_file.c:142 prepresult = <optimized out> ip1 = 0 ip2 = 0 ip3 = 0 ip4 = 0 groupid = <optimized out> pageidx = <optimized out> hostname = '\000' <repeats 16 times>, "/usr/lib/xymon/server/etc/rrddefinitions.cfg", '\000' <repeats 3404 times>... dgname = 0x0 dgname_buflen = 0 curtoppage = <optimized out> curpage = <optimized out> pgtail = <optimized out> htree = <optimized out> cfgdata = <optimized out> inbol = <optimized out> ineol = <optimized out> insavchar = 0 '\000' #12 0x00005646a0a0d08f in main (argc=<optimized out>, argv=<optimized out>) at ./xymond/xymond_rrd.c:329 eoln = <optimized out> ctlbuf = '\000' <repeats 4095 times> restofmsg = 0x0 metacount = <optimized out> testname = 0x0 sender = 0x0 ldef = 0x0 n = <optimized out> now = 458 classname = 0x0 pagepaths = 0x0 gotcachectlmessage = <optimized out> metadata = {0x0 <repeats 21 times>} p = <optimized out> hostname = 0x0 tstamp = <optimized out> childstat = 0 msg = 0x7f892877e010 "@@status#8/xymon12.sail.spinnaker.de|1727205704.508355|127.0.0.1||xymon12.sail.spinnaker.de|xymongen|1727207504|green||green|1727205584|0||0||1727205554|linux||0|\nstatus xymon12,sail,spinnaker,de.xymo"... argi = <optimized out> sa = {__sigaction_handler = {sa_handler = 0x5646a0a0d740 <sig_handler>, sa_sigaction = 0x5646a0a0d740 <sig_handler>}, sa_mask = {__val = {0 <repeats 16 times>}}, sa_flags = 0, sa_restorer = 0x0} exthandler = <optimized out> extids = <optimized out> processor = <optimized out> ctlsockaddr = {sun_family = 1, sun_path = "/var/lib/xymon/tmp/rrdctl.1656", '\000' <repeats 77 times>} ctlsocket = 3 usebackfeedqueue = 0 xymond_alert: ============= #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 tid = <optimized out> ret = 0 pd = <optimized out> old_mask = {__val = {0}} ret = <optimized out> #1 0x00007f7ae955de9f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 No locals. #2 0x00007f7ae950efb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 ret = <optimized out> #3 0x00007f7ae94f9472 in __GI_abort () at ./stdlib/abort.c:79 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, sa_mask = {__val = {0, 0, 0, 0, 0, 0, 0, 0, 140729827760864, 3558781987793485696, 18061915719574039552, 93857240661856, 93857240661856, 140729827761104, 93857240583353, 140729827761248}}, sa_flags = 2, sa_restorer = 0x7ffe37649ae0} #4 0x00007f7ae9552430 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f7ae966c210 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:155 ap = {{gp_offset = 24, fp_offset = 0, overflow_arg_area = 0x7ffe37649c30, reg_save_area = 0x7ffe37649bc0}} fd = <optimized out> list = <optimized out> nlist = <optimized out> cp = <optimized out> #5 0x00007f7ae95eb0f2 in __GI___fortify_fail (msg=msg@entry=0x7f7ae966c1b6 "buffer overflow detected") at ./debug/fortify_fail.c:26 No locals. #6 0x00007f7ae95e9c00 in __GI___chk_fail () at ./debug/chk_fail.c:28 No locals. #7 0x00007f7ae95e9835 in ___snprintf_chk (s=s@entry=0x555cd77d3f62 <md_string+2> "", maxlen=maxlen@entry=35, flag=flag@entry=2, slen=slen@entry=31, format=format@entry=0x555cd77c0cb9 "%02x") at ./debug/snprintf_chk.c:29 mode = <optimized out> ap = {{gp_offset = 48, fp_offset = 48, overflow_arg_area = 0x7ffe37649d40, reg_save_area = 0x7ffe37649c80}} ret = <optimized out> #8 0x0000555cd77ba6d1 in snprintf (__fmt=0x555cd77c0cb9 "%02x", __n=35, __s=0x555cd77d3f62 <md_string+2> "") at /usr/include/x86_64-linux-gnu/bits/stdio2.h:54 No locals. #9 md5hash ( input=input@entry=0x555cd81e5390 "#\n# Master configuration file for Xymon\n#\n# This file defines several things:\n#\n# 1) By adding hosts to this file, you define hosts that are monitored by Xymon\n# 2) By adding \"page\", \"subpage\", \"group"...) at ./lib/digest.c:44 ctx = 0x555cd81e5350 md_value = "\301tJ\342^\312T\032bGjɨ\f\267I" md_string = "c1", '\000' <repeats 30 times> i = 1 p = 0x555cd77d3f62 <md_string+2> "" #10 0x0000555cd77b5d89 in prepare_fromnet () at ./lib/loadhosts_file.c:104 sres = 0x555cd81e5350 sendstat = <optimized out> fdata = 0x555cd81e5390 "#\n# Master configuration file for Xymon\n#\n# This file defines several things:\n#\n# 1) By adding hosts to this file, you define hosts that are monitored by Xymon\n# 2) By adding \"page\", \"subpage\", \"group"... fhash = <optimized out> contentmd5 = '\000' <repeats 32 times> sres = <optimized out> sendstat = <optimized out> fdata = <optimized out> fhash = <optimized out> #11 load_hostnames (hostsfn=0x7ffe3764f88f "/usr/lib/xymon/server/etc/hosts.cfg", extrainclude=extrainclude@entry=0x0, fqdn=fqdn@entry=1) at ./lib/loadhosts_file.c:142 prepresult = <optimized out> ip1 = 0 ip2 = 0 ip3 = 0 ip4 = 0 groupid = <optimized out> pageidx = <optimized out> hostname = '\000' <repeats 3720 times>... dgname = 0x0 dgname_buflen = 0 curtoppage = <optimized out> curpage = <optimized out> pgtail = <optimized out> htree = <optimized out> cfgdata = <optimized out> inbol = <optimized out> ineol = <optimized out> insavchar = 0 '\000' #12 0x0000555cd77a09a8 in main (argc=3, argv=0x7ffe3764d1c8) at ./xymond/xymond_alert.c:533 msg = <optimized out> seq = 0 argi = <optimized out> alertcolors = 56 alertinterval = 1800 configfn = <optimized out> checkfn = <optimized out> loadresult = <optimized out> reloadconfigtime = 0 checkpointinterval = <optimized out> acklogfn = '\000' <repeats 2888 times>... acklogfd = 0x0 notiflogfn = "P\003\000\000\000\000\000\000 \000\000\000\000\000\000\000 \000\000\000\000\000\000\000\b\000\000\000\000\000\000\000\004\000\000\000\004\000\000\000p\003\000\000\000\000\000\000p\003\000\000\000\000\000\000p\003\000\000\000\000\000\000D\000\000\000\000\000\000\000D\000\000\000\000\000\000\000\004\000\000\000\000\000\000\000\a\000\000\000\004\000\000\000\320\350\034\000\000\000\000\000\320\350\034\000\000\000\000\000\320\350\034\000\000\000\000\000\020\000\000\000\000\000\000\000\220\000\000\000\000\000\000\000\b\000\000\000\000\000\000\000S\345td\004\000\000\000P\003\000\000\000\000\000\000P\003\000\000\000\000\000\000P\003\000\000\000\000\000\000 \000\000\000\000\000\000\000 \000\000\000\000\000\000\000\b\000\000\000\000\000\000\000"... notiflogfd = 0x0 tracefn = <optimized out> sa = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, sa_mask = {__val = {0 <repeats 16 times>}}, sa_flags = 0, sa_restorer = 0x0} configchanged = <optimized out> lastxmit = 0 Greetings Roland
Sorry to quote myself all the time, but I hope, that I found/fixed the root cause now.
On Tue, 24 Sep 2024, I wrote:
#9 md5hash ( input=input@entry=0x5594c83023e0 "#\n# Master configuration file for Xymon\n#\n# This file defines several things:\n#\n# 1) By adding hosts to this file, you define hosts that are monitored by Xymon\n# 2) By adding \"page\", \"subpage\", \"group"...) at ./lib/digest.c:44 ctx = 0x5594c83023a0 md_value = "\301tJ\342^\312T\032bGjɨ\f\267I" md_string = "c1", '\000' <repeats 30 times> i = 1 p = 0x5594c6dd7c02 <md_string+2> ""
Seems that there's a bug in the calculation of the buffer size. The attached patch should fix this. At least compilation with -D_FORTIFY_SOURCE=3 using this patch no longer results in buffer overflow messages on my test system.
Greetings Roland
participants (6)
-
Adam Thorn
-
Chris Pretorius
-
Jeremy Laidman
-
Jeremy Ruffer
-
Roland Rosenfeld
-
Tom Schmidt