Linux installation Unhandled exception. System.ArgumentOutOfRangeException

[PMontgomerie]

I am attempting to install the Ls-Agent on our production Linux servers.  We have successfully installed using the same process on our lower Dev and Staging environments with no issues.   All of our production servers are experiencing this issue.   Our production systems are the created from the same AMI as our STG environment.   We installed the low environments a couple weeks ago for testing and attempted production deployment a couple days ago.   I have attempted to uninstall and reinstall as well.   Any assistance would be helpful.  

The journalctl provides the following response.  

May 06 17:35:39 mylocal.host.com systemd[1]: Started Lansweeper Agent.
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,086 [INFO ] : Program is Running
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,179 [INFO ] : Reading ini file.
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,311 [INFO ] : Getting asset id
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,311 [INFO ] : Existing asset id found: <Removed for posting on forums>
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,314 [INFO ] : Creating communication channel
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,324 [INFO ] : CreateReachableEndPoint for <Removed for posting on forums>
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,651 [INFO ] : Creating InternalCommunicationSender to URL https://our.lshost.com:9524/lsagent
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,660 [INFO ] : Getting asset status from the server
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,711 [INFO ] : Asset is enabled
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,711 [INFO ] : Retrieving configuration
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,711 [INFO ] : Getting configuration from the server
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,746 [INFO ] : Updating local config
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,771 [INFO ] : Saving ini settings
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,774 [INFO ] : Creating ini backup.
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: 2024-05-06 17:35:40,774 [INFO ] : Waiting until next scheduled iteration: January 1, 0001 00:00
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: Unhandled exception. System.ArgumentOutOfRangeException: Number must be either non-negative and less than or equal to Int32.MaxValue or -1. (Parameter 'timeout')
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: at System.Threading.WaitHandle.ToTimeoutMilliseconds(TimeSpan timeout)
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: at Lansweeper.Echo.Client.BL.EchoClient.RunLsAgentProcess()
May 06 17:35:40 mylocal.host.com LsAgent[1744591]: at Lansweeper.Echo.Client.Application.Program.Main(String[] args)
May 06 17:35:40 mylocal.host.com systemd[1]: ls-agent.service: Main process exited, code=dumped, status=6/ABRT
May 06 17:35:40 mylocal.host.com systemd[1]: ls-agent.service: Failed with result 'core-dump'.
May 06 17:35:41 mylocal.host.com systemd[1]: ls-agent.service: Service RestartSec=100ms expired, scheduling restart.
May 06 17:35:41 mylocal.host.com systemd[1]: ls-agent.service: Scheduled restart job, restart counter is at 1.
May 06 17:35:41 mylocal.host.com systemd[1]: Stopped Lansweeper Agent.

[Mister_Nobody]

Incorrect scheduled date. Create support case 

[PMontgomerie]

Forgot to mention all of the Agents reported in on installation to the Lansweeper application server.  We can see them in console and all the system info.   We are using 10.42.1 version 

[Mister_Nobody]

Often a user's linux comp is scanned by Lansweeper using an agent. In this case some service is registered in the operating system. On my Debian workstation this is ls-agent.service. As a rule, the service runs in an environment with the default OS locale. If the “scanning” command returns locale-insensitive output, Lansweeper may not “recognize” the received text and may not fill in the corresponding data sections in Ls.
It is recommended to configure the agent service to work in “own” English locale. To do this on systems using systemd, do the following:
In /etc/systemd/system/ a directory ls-agent.service.d is created, in it a *.conf file is created with the following contents:

[Service]
Environment="LANG=en_US.UTF-8"

Then run: systemctl daemon-reload, systemctl restart ls-agent.service

[PMontgomerie]

Attempted this solution with no luck.  

● ls-agent.service - Lansweeper Agent
Loaded: loaded (/etc/systemd/system/ls-agent.service; enabled; vendor preset: disabled)
Active: failed (Result: core-dump) since Tue 2024-05-07 10:30:36 EDT; 9s ago
Process: 2533609 ExecStart=/opt/LansweeperAgent/LSAgent (code=dumped, signal=ABRT)
Main PID: 2533609 (code=dumped, signal=ABRT)

May 07 10:30:36 mylocal.host.com systemd[1]: ls-agent.service: Main process exited, code=dumped, status=6/ABRT
May 07 10:30:36 mylocal.host.com systemd[1]: ls-agent.service: Failed with result 'core-dump'.
May 07 10:30:36 mylocal.host.com systemd[1]: ls-agent.service: Service RestartSec=100ms expired, scheduling restart.
May 07 10:30:36 mylocal.host.com systemd[1]: ls-agent.service: Scheduled restart job, restart counter is at 5.
May 07 10:30:36 mylocal.host.com systemd[1]: Stopped Lansweeper Agent.
May 07 10:30:36 mylocal.host.com systemd[1]: ls-agent.service: Start request repeated too quickly.
May 07 10:30:36 mylocal.host.com systemd[1]: ls-agent.service: Failed with result 'core-dump'.
May 07 10:30:36 mylocal.host.com systemd[1]: Failed to start Lansweeper Agent.

[Mister_Nobody]

Did you try 9.x version?

https://www.lansweeper.com/product/download/lsagent/

[PMontgomerie]

I assume you are meaning the legacy agent.  I have not attempted that.   

[Mister_Nobody]

What is version of your Linux? 

Do you use selinux? 

[PMontgomerie]

This is happening on both RHEL 8 , 9 and AWS Linux 2 and 3. 

SeLinux is passive

[Mister_Nobody]

You have to create support case