David,
     Have you checked to see if there are any errors in the /var/log/xymon/xymonclient.log file?  This file is created by the xymon client.  If there are no errors, this file may be empty or non-existent.

Tom

On Thu, Jul 25, 2024 at 1:07 PM Josh Luthman <josh@imaginenetworksllc.com> wrote:
The only different in Tom's post and the Terabithia package is the ExecStart xymonlaunch binary location FWIW (I'm using Alma9).

On Thu, Jul 25, 2024 at 11:20 AM Tom Schmidt <tom@4schmidts.com> wrote:
Below is what I have on Rocky8 and Rocky9, and both the server and client startup fine for me.  Update the path to xymon appropriately for your installation.

Tom

Symbolic links:
/etc/systemd/system/xymon-client.service -> /usr/lib/systemd/system/xymonlaunch.service
/etc/systemd/system/xymon.service -> /usr/lib/systemd/system/xymonlaunch.service

Contents of /usr/lib/systemd/system/xymonlaunch.service file:

# unit file for Fedora 18 and up, RHEL 7 and up, or other systemd distros

[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/default/xymonlaunch
EnvironmentFile=-/etc/sysconfig/xymonlaunch
User=xymon
# We wrap in xymoncmd to eliminate the need for the bulk of the old init script
ExecStart=/home/xymon/server/bin/xymoncmd /home/xymon/server/bin/xymonlaunch --no-daemon $XYMONLAUNCHOPTS
# xymoncmd exec's xymonlaunch, and xymonlaunch will propagate -HUP as needed
ExecReload=/bin/kill -HUP $MAINPID
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
# Give an extra 6s beyond xymonlaunch to let things disconnect
RestartSec=6
Restart=on-failure

On Thu, Jul 25, 2024 at 8:46 AM David Smith <david.smith@renfrewshire.gov.uk> wrote:

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).

_______________________________________________
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
_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com