→ Having trouble accessing our new support portal or creating a ticket? Please notify our team here

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
PMontgomerie
Engaged Sweeper II

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.

11 REPLIES 11

Thanks for your efforts.   We filed a support ticket. 

What is locale?