July 2024 - Xymon - Xymon mailman web

assistance for auto start of xymon in Rocky 9
by David Smith 23 Jan '25

23 Jan '25

Hi I am looking for some clues to autostart xymon in Rocky9 I copied my method from a Centos 7 box which has been running successfully for quite a number of years I made a xymonlaunch.service file which I placed in /etc/system/system, contents below # xymonlaunch.service # systemd file for Fedora 18 and up, or RHEL 7 and up [Unit] Description=Xymon systems and network monitor Documentation=man:xymon(7) man:xymonlaunch(8) man:xymon(1) After=network.target [Install] # Compatibility with "xymon" and "xymon-client" Alias=xymon.service Alias=xymon-client.service WantedBy=multi-user.target [Service] #EnvironmentFile=/etc/sysconfig/xymonlaunch User=xymon # We wrap in xymoncmd to eliminate the need for the bulk of the old init script ExecStart=/opt/BB/bbsw/server/bin/xymoncmd /opt/BB/bbsw/server/bin/xymonlaunch --no-daemon $XYMONLAUNCHOPTS Type=simple # Kill xymonlaunch, but don't send kills to the underlying procs, since they # might be doing important things (like writing checkpoints and flushing caches) KillMode=process # SendSIGHUP=yes SendSIGKILL=no I then did systemctl enable xymonlaunch.service, and this made 2 symbolic links in the same directory one named xymon.service and one named xymon-client.service What is happening on Rocky9 is that on the server is being started, the client part does not start Any ideas what may be awry? The same method worked/works without issue on Centos 7 Any help, guidance, clues would be much appreciated. I know that I would be able to cobble something together to stick into rc.local, but the powers that be up above would rather I did it using the method that uses systemctl Best regards David Renfrewshire Council Website -http://www.renfrewshire.gov.uk This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Renfrewshire Council may, in accordance with the Telecommunications(Lawful Business Practice) (Interception of Communications) Regulations 2000, intercept e-mail messages for the purpose of monitoring or keeping a record of communications on the Council's system. If a message contains inappropriate dialogue it will automatically be intercepted by the Council's Internal Audit section who will decide whether or not the e-mail should be onwardly transmitted to the intended recipient(s). Renfrewshire Council Website -http://www.renfrewshire.gov.uk This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Renfrewshire Council may, in accordance with the Telecommunications(Lawful Business Practice) (Interception of Communications) Regulations 2000, intercept e-mail messages for the purpose of monitoring or keeping a record of communications on the Council's system. If a message contains inappropriate dialogue it will automatically be intercepted by the Council's Internal Audit section who will decide whether or not the e-mail should be onwardly transmitted to the intended recipient(s).

4 7

Re: analysis tolerances not applying to scripted MacOS host
by Kris Springer 01 Aug '24

01 Aug '24

Thanks Zak. I finally got back to working on my Mac client and have made significant progress now that I'm sending things to the server in the correct format. I am now hitting an issue that I was also running into previously regarding the server not generating a cpu (la) graph. It seems that everything else works fine with my client, but no matter what I do I can't get the server to generate a cpu graph when sending the data as client $hostname.$ostype $clientclass The cpu graph works perfectly if I send data as status $hostname.cpu green\n$cpuData But of course I can't do that because it forces the color green and then I can't use the analysis.cfg tolerances on it. If I send it with no color it doesn't work at all. status $hostname.cpu $cpuData I've looked all through the original XymonPSclient for Windows that I'm using as a functioning example, but I'm not seeing the magic sauce that makes the cpu graph work. All the other tests graphs work just fine, but this cpu graph has given me trouble since I first started this project. Any ideas? I've tried the following $ostype $clientclass options with none seeming to change anything. linux freebsd netbsd openbsd darwin bbwin powershell generic Kris Springer On 7/10/24 03:42, Beck, Zak wrote: > > Hi Kris > > Jeremy is right – for server side analysis, don’t send multiple > individual status messages for these core tests. I don’t think > analysis is triggered for status messages. > > Instead, send one ‘client’ message with [cpu], [disk], [memory] > sections, and send it as a client message, e.g. this from the Windows > Powershell client: > > client $($clientname).$($script:XymonSettings.clientsoftware) > $($script:XymonSettings.clientclass) XymonPS > > The defaults here are ‘powershell’ for clientsoftware (which is really > OSTYPE) and clientclass. > > If you have a Windows host running the Powershell client, you can see > the last client message sent to xymon in the xymon-lastcollect.txt > file. This is verbatim what is sent to the server via TCP. > > https://www.xymon.com/help/manpages/man1/xymon.1.html > > client[/COLLECTORID] HOSTNAME.OSTYPE [HOSTCLASS] > > Used to send a "client" message to the Xymon server. Client messages > are generated by the Xymon client; when sent to the Xymon server they > are matched against the rules in the /analysis.cfg > <https://www.xymon.com/help/manpages/man5/analysis.cfg.5.html>(5)/ > configuration file, and status messages are generated for the > client-side tests. The COLLECTORID is used when sending client-data > that are additions to the standard client data. The data will be > concatenated with the normal client data. > > You need to find the right OSTYPE for MacOS… xymond/xymond_client.c in > the server source is what handles these messages, you’ll see a bunch > of includes to match different OS types: > > #include "client/linux.c" > > #include "client/freebsd.c" > > #include "client/netbsd.c" > > #include "client/openbsd.c" > > #include "client/solaris.c" > > #include "client/hpux.c" > > #include "client/osf.c" > > #include "client/aix.c" > > #include "client/darwin.c" > > #include "client/irix.c" > > #include "client/sco_sv.c" > > #include "client/bbwin.c" > > #include "client/powershell.c" /* Must go after client/bbwin.c */ > > #include "client/zvm.c" > > #include "client/zvse.c" > > #include "client/zos.c" > > #include "client/mqcollect.c" > > #include "client/snmpcollect.c" > > #include "client/generic.c" > > These included files handle the different OSTYPEs and differences in > message formats between each (e.g. the output of the df command has > different headings for some OSes). > > My guess is Darwin is something like OS X, you’re right that there’s > nothing for modern MacOS. Maybe Darwin would work. > > Alternatively, if you can make the output resemble what you’d get from > a Unix client then you could use OSTYPE = one of the unix types > (possibly one of the BSDs, as MacOS has BSD origins). > > I‘d be tempted to start with darwin, and look in > xymond/client/darwin.c - note that xymond_client is probably expecting > to see some sections that you may not be sending yet: > > timestr = getdata("date"); > > uptimestr = getdata("uptime"); > > clockstr = getdata("clock"); > > msgcachestr = getdata("msgcache"); > > whostr = getdata("who"); > > psstr = getdata("ps"); > > topstr = getdata("top"); > > dfstr = getdata("df"); > > inodestr = getdata("inode"); > > meminfostr = getdata("meminfo"); > > msgsstr = getdata("msgs"); > > netstatstr = getdata("netstat"); > > ifstatstr = getdata("ifstat"); > > portsstr = getdata("ports"); > > Cheers > > Zak > > *From:*Kris Springer <kspringer(a)innovateteam.com> > *Sent:* Wednesday, July 10, 2024 5:37 AM > *To:* Xymon mailinglist <xymon(a)xymon.com>; Jeremy Laidman > <jeremy(a)laidman.org> > *Subject:* [External] [Xymon] Re: analysis tolerances not applying to > scripted MacOS host > > > > > *CAUTION:*External email. Be cautious with links and attachments. > > > > Understood, and thanks for the info. I thought it might be something > like that. The problem is that there isn't a modern functioning MacOS > xymon client that uses the xymond_client process. All the math is > wrong in the 2015 version. The cpu, mem, and disk checks are all > different in the modern MacOS versions than they were 10 years ago. > For whatever reason Xymon has seemed to ignore that Mac's need > monitored too. I've got a good script that produces good data, but > it's not using any xymond_client process. I'd be happy to share my > code with anyone who can assist with getting this working the > 'correct' way. We could wrap it up into an App.dmg for easy install. > Then we'll finally have a MacOS client available just like we already > have the Windows PS client and the Linux clients. > > --- > > Kris Springer > > On July 9, 2024 10:01:28 PM Jeremy Laidman <jeremy(a)laidman.org> wrote: > > The analysis.cfg thresholds are applied in central mode. If you > are operating in local mode (which you appear to be, as you are > sending status messages from the client) then the CPU thresholding > needs to be done on the client. > > In central mode, the xymond_client process parses client messages > for relevant sections (eg [df] for disk data, [uptime] for CPU > load averages) and performs thresholding checks against settings > in analysis.cfg. It's my understanding that in local mode, the > xymond_client process runs on the client side, so if you're > implementing a full client that runs in local mode, you have to > replicate the behaviour of xymond_client. > > It's far simpler to make a client that runs only in central mode. > You construct a client message consisting of all of the sections > you're interested in, and send it to the server for it to parse > for thresholding and extracting metrics for rrd files. The > structure of the client message contents is important, as the > parser expects the sections to be in a format that matches the OS > ID of the client ("darwin" for MacOS?). > > J > > On Wed, 10 July 2024, 07:28 Kris Springer, > <kspringer(a)innovateteam.com> wrote: > > I've been working to create a new MacOS Xymon Client since the > last > iteration I can find is using MacPorts and it's from 2015. > I've tried > both Python and Powershell using Homebrew and I've settled on > Powershell. I may convert it to Python later once I get it > finalized. > It's just a single script that gathers host data and sends it > to the > server without any 2-way communication or client-local.cfg > handshake > stuff going on. I have data being sent successfully from a > Mac laptop > and the server is displaying everything fine with graphs and text > outputs. But the server isn't applying the analysis.cfg > tolerances to > the host and I don't know why. Is there some magic piece of > code that > I'm overlooking or don't know exists that tells the server to > compare > the data to the tolerances in analysis.cfg? > > My MacPSclient.ps1 is sending it's data in this format, but > the status > is always green on the server. > "status $hostname.cpu green\n$cpuData" > > This also works, but the status is always green. > "status $hostname.cpu green $timestamp $cpuData" > > This also works, but the status is always green. > "status $hostname.disk green\n[disk]\n$diskUsageToSend" > > I can change the word green to yellow and it changes the color > on the > server, but if I remove the word green, no data is updated on > the server > side when the script is ran. So I'm assuming the color tag is > required. > I've attempted to read how-to's, looked in other client > scripts for a > clue, and searched in forums, but I'm not finding anything. > Can someone here help? > > Thanks so much! > > -- > Kris Springer > > _______________________________________________ > Xymon mailing list -- xymon(a)xymon.com > To unsubscribe send an email to xymon-leave(a)xymon.com > > _______________________________________________ > > Xymon mailing list -- xymon(a)xymon.com <mailto:xymon%40xymon.com> > > To unsubscribe send an email to xymon-leave(a)xymon.com > <mailto:xymon-leave%40xymon.com> > > > ------------------------------------------------------------------------ > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise confidential information. If you > have received it in error, please notify the sender immediately and > delete the original. Any other use of the e-mail by you is prohibited. > Where allowed by local law, electronic communications with Accenture > and its affiliates, including e-mail and instant messaging (including > content), may be scanned by our systems for the purposes of > information security, AI-powered support capabilities, and assessment > of internal compliance with Accenture policy. Your privacy is > important to us. Accenture uses your personal data only in compliance > with data protection laws. For further information on how Accenture > processes your personal data, please see our privacy statement at > https://www.accenture.com/us-en/privacy-policy. > ______________________________________________________________________________________ > > www.accenture.com

2 8

Mailing lists?
by John Horne 30 Jul '24

30 Jul '24

Hi, I am going to be retiring in a few months, and since work has dropped off (for me) I have been trying to do the nice thing of unsubscribing from various mailing lists. For Xymon lists I have two questions: 1) I saw Henrik's message from early July about moving the mailing lists to a new server. No problem with that, and I resubscribed as requested. However, I have just noticed at the bottom of the 'Welcome to the "Xymon" mailing list' message I received, it says: "If you have forgotten your password you will need to reset it via the web UI." What web UI? No URL was included. I don't want to unsubscribe from this list yet, but, as said, will do in a few months. 2) From 2012 I have a similar 'Welcome to the ...' message, but for the 'xymon- announce' mailing list. (I tend to keep any of these welcome messages for mailing lists I have joined. Typically just so that I know how to unsubscribe from them.) Does this announcement list still exist? This list I want to unsubscribe from (if it exists). Thanks, John. -- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [https://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

4 4

assistance for auto start of xymon in Rocky 9
by David Smith 26 Jul '24

26 Jul '24

Hi I am looking for some clues to autostart xymon in Rocky9 I copied my method from a Centos 7 box which has been running successfully for quite a number of years I made a xymonlaunch.service file which I placed in /etc/system/system, contents below # xymonlaunch.service # systemd file for Fedora 18 and up, or RHEL 7 and up [Unit] Description=Xymon systems and network monitor Documentation=man:xymon(7) man:xymonlaunch(8) man:xymon(1) After=network.target [Install] # Compatibility with "xymon" and "xymon-client" Alias=xymon.service Alias=xymon-client.service WantedBy=multi-user.target [Service] #EnvironmentFile=/etc/sysconfig/xymonlaunch User=xymon # We wrap in xymoncmd to eliminate the need for the bulk of the old init script ExecStart=/opt/BB/bbsw/server/bin/xymoncmd /opt/BB/bbsw/server/bin/xymonlaunch --no-daemon $XYMONLAUNCHOPTS Type=simple # Kill xymonlaunch, but don't send kills to the underlying procs, since they # might be doing important things (like writing checkpoints and flushing caches) KillMode=process # SendSIGHUP=yes SendSIGKILL=no I then did systemctl enable xymonlaunch.service, and this made 2 symbolic links in the same directory one named xymon.service and one named xymon-client.service What is happening on Rocky9 is that on the server is being started, the client part does not start Any ideas what may be awry? The same method worked/works without issue on Centos 7 Any help, guidance, clues would be much appreciated. I know that I would be able to cobble something together to stick into rc.local, but the powers that be up above would rather I did it using the method that uses systemctl Best regards David Renfrewshire Council Website -http://www.renfrewshire.gov.uk This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Renfrewshire Council may, in accordance with the Telecommunications(Lawful Business Practice) (Interception of Communications) Regulations 2000, intercept e-mail messages for the purpose of monitoring or keeping a record of communications on the Council's system. If a message contains inappropriate dialogue it will automatically be intercepted by the Council's Internal Audit section who will decide whether or not the e-mail should be onwardly transmitted to the intended recipient(s). Renfrewshire Council Website -http://www.renfrewshire.gov.uk This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Renfrewshire Council may, in accordance with the Telecommunications(Lawful Business Practice) (Interception of Communications) Regulations 2000, intercept e-mail messages for the purpose of monitoring or keeping a record of communications on the Council's system. If a message contains inappropriate dialogue it will automatically be intercepted by the Council's Internal Audit section who will decide whether or not the e-mail should be onwardly transmitted to the intended recipient(s).

2 3

xymoncgimsg.cgi timeout limit
by Kris Springer 26 Jul '24

26 Jul '24

I've been adding a lot of hosts to our system using the XymonPSclient which sends it's data over port 443 to xymoncgimsg.cgi I've got 1 hosts who's payload is over a Meg and the logs seem to indicate that it's timing out before the payload completes it's send. The client logs say this. body length 1075939, timeout 100000ms I know 100000 ms is nearly 2 minutes, but I've already got the Xymon server set to accept very large payloads and have never had this problem before. And it's only this 1 host that has a large payload. Where would I look to expand the timeout limit? Is this a PS client script issue, an Apache server issue, or a xymoncgimsg.cgi config issue? -- Kris Springer

2 3

Monitoring
by Yuh, Joel 16 Jul '24

16 Jul '24

Dear Xymon Support Team, I hope this message finds you well. I am writing to inquire about Xymon, your monitoring tool, and its capabilities. Our organization is currently evaluating various monitoring solutions to enhance our infrastructure's performance and reliability, and we are keen to understand how Xymon can fit into our environment. Specifically, I would appreciate detailed information on the following aspects: Features and Capabilities: What are the core features of Xymon? Does Xymon support real-time monitoring and alerting for both hardware and software components? How does Xymon handle scalability and performance in large environments? Integration and Compatibility: What types of systems and applications can Xymon monitor? Can Xymon integrate with other tools and systems, such as Always On windows failover cluster. Installation and Configuration: Could you provide an overview of the installation process for Xymon? Are there specific prerequisites or configurations needed for optimal performance? User Interface and Reporting: What kind of user interface does Xymon offer, and how customizable is it? Does Xymon provide comprehensive reporting and data visualization options? Support and Documentation: What types of support are available for Xymon users (e.g., documentation, community support, professional support)? Are there any training resources or user manuals available? Licensing and Costs: Could you provide details on the licensing model and associated costs for Xymon? We are particularly interested in how Xymon can help us achieve improved monitoring and proactive management of our IT infrastructure. A demonstration or trial version of the tool would also be highly beneficial to us. Please let us know a convenient time for a call or a demo session. Your assistance in providing this information will be invaluable to our decision-making process. Thank you for your attention to this matter. I look forward to your response. Mit freundlichen Grüßen Joel Yuh ____________________________________________ Kommunalverband für Jugend und Soziales Baden-Württemberg Referat Organisation, IT und Fortbildung Lindenspürstraße 39 70176 Stuttgart Telefon: 0711 6375-472 www.kvjs.de<http://www.kvjs.de/>

2 1

analysis tolerances not applying to scripted MacOS host
by Kris Springer 11 Jul '24

11 Jul '24

I've been working to create a new MacOS Xymon Client since the last iteration I can find is using MacPorts and it's from 2015. I've tried both Python and Powershell using Homebrew and I've settled on Powershell. I may convert it to Python later once I get it finalized. It's just a single script that gathers host data and sends it to the server without any 2-way communication or client-local.cfg handshake stuff going on. I have data being sent successfully from a Mac laptop and the server is displaying everything fine with graphs and text outputs. But the server isn't applying the analysis.cfg tolerances to the host and I don't know why. Is there some magic piece of code that I'm overlooking or don't know exists that tells the server to compare the data to the tolerances in analysis.cfg? My MacPSclient.ps1 is sending it's data in this format, but the status is always green on the server. "status $hostname.cpu green\n$cpuData" This also works, but the status is always green. "status $hostname.cpu green $timestamp $cpuData" This also works, but the status is always green. "status $hostname.disk green\n[disk]\n$diskUsageToSend" I can change the word green to yellow and it changes the color on the server, but if I remove the word green, no data is updated on the server side when the script is ran. So I'm assuming the color tag is required. I've attempted to read how-to's, looked in other client scripts for a clue, and searched in forums, but I'm not finding anything. Can someone here help? Thanks so much! -- Kris Springer

2 3

Digest mode?
by Greg Earle 07 Jul '24

07 Jul '24

On 5 July 2024, at 12:32:15 CEST Henrik Størner wrote: > In a few moments (or later today) you will all receive an invitation > to join the Xymon mailing list. You must confirm this in order to > keep receiving mails about Xymon. Will the new list come in Digest form or not? I was on Digest mode before. - Greg

2 1

New list is live
by Henrik 05 Jul '24

05 Jul '24

Glad you made it here :-) /Henrik

1 0

List test 2
by Henrik Juul Stoerner 05 Jul '24

05 Jul '24

Checking with HyperKitty /Henrik

1 0