Domino on Linux: Updated/additional lnsnmp Start/Stop-Script that is compatible with systemd based Linux OS

Does SNMP work for you outside the container in Domino 12.0.2?
I can't get it working on current servers. I even used strace to trace the lnsnmp process.


The SNMP server on the host is running and I get this back before the process terminates.

Even if we solve it, it's not clear if we can get it working in combination.

We need lnsnmp probably running inside the container. Or maybe it would be OK to run it on the host?

I tried right now on a normal server and failed. Does it need to be installed inside the container?
Could it run on the container host and the Domino servertasks communicate with it on the host?

Still you would need a systemd service - which would not be too complicated to build.

But I don't get it working even I traced it with strace. Any tip what might be missing?

It was trying to read a lnsnmp.ini file in various places. but that's just optional. Even with debug enabled -D 255 I see only the output below and no errors.

Constructing Instigator
Constructing EESA EndPoint
HCL Domino SNMP Agent (Version 8.0)
Copyright (c) HCL Technologies 1994, 2019. All Rights Reserved.
Server list read from lnsnmp.ini:
Constructing Instigator
Constructing CSIPC
Attaching to local SNMP agent
Allocating instigator attributes
Opening SMUX session
Registering a local MIB with EESAEndPoint
Trying to add the mib, calling AddMib()
Registering / unregistering a MIB with SMUX
Sending registration request to SMUX
Waiting for response to registration request
Waiting for SMUX message
Got an SNMP request, processing it now
Processing a SMUX message
Closing SMUX session

It's simple to make systemd service, but the lnsnmp.sh script does not work with systemd based Linux OS.

systemd[1]: Starting LNSNMP(SNMP) Daemon....
lnsnmp.sh[36098]: Don't know how to start/stop lnsnmp on this version of Linux.
systemd[1]: lnsnmp.service: Control process exited, code=exited status=1
systemd[1]: Failed to start LNSNMP(SNMP) Daemon..
systemd[1]: lnsnmp.service: Unit entered failed state.
systemd[1]: lnsnmp.service: Failed with result 'exit-code'.

Also the lnsnmp.sh contains old default path which hasn’t been used in many years.

maybe Daniel Nashed start script is worth including in standard Domino install packege?

Daniel Nashed created such a tool for UNIX/Linux.  See:

http://www.nashcom.de/nshweb/pages/startscript.htm

Very simple to set up and use. It just works!!  I have it on all my Linux Domino servers.

As discussed on https://atnotes.de/index.php/topic,61967.0.html Ulrich Krause posted an service-Definition for lnsnmp that could be used directly (or as a base) for Shipping with Domino:

[Unit]
Description=LNSNMP
After=network.target

[Service]
Type=simple
User=root
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
Environment=PATH=/usr/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
PIDFile=/var/run/lnsnmp.pid

ExecStart=/opt/ibm/domino/notes/latest/linux/lnsnmp

[Install]
WantedBy=multi-user.target