LsAgent on Ubuntu 18.04 - Not getting updated in the console

[rpokkyarath]

Hi,

Installed LsAgent on an Ubuntu (18.04). I'm testing before rolling it out to other Linux machines in our environment. systemctl status LansweeperAgentService shows the service is up and running. However I do not see the machine listed in the Scanning -> Lsagent Scanning -> Assets section of the console even after 2 days.

Following is the output from the /opt/LanSweeperAgent/lsagentlog.txt on the machine with the agent.

2019-05-21 09:50:01,409 [DEBUG] : Waiting for next scheduled scan...
2019-05-21 10:05:01,415 [INFO ] : CreateReachableEndPoint for <CLOUD-RELAY-AUTHENTICATION-KEY>
2019-05-21 10:05:01,420 [INFO ] : Url Check with address failed. Endpoint with address 'https://<LOCAL-LANSWEEPER-IP>:9524/lsagent' was not reachable: No such device or address No such device or address
2019-05-21 10:05:01,420 [WARN ] : Connection to url https://<LOCAL-LANSWEEPER-IP>:9524/lsagent failed
2019-05-21 10:05:01,422 [INFO ] : Url Check with address failed. Endpoint with address 'http://<LOCAL-LANSWEEPER-IP>:9524/lsagent' was not reachable: No such device or address No such device or address
2019-05-21 10:05:01,422 [WARN ] : Connection to url http://<LOCAL-LANSWEEPER-IP>:9524/lsagent failed
2019-05-21 10:05:01,422 [DEBUG] : Created RelayCommunicationSender to URL https://relay.lansweeper.com/EchoService.svc
2019-05-21 10:05:02,747 [DEBUG] : Asset is enabled.
2019-05-21 10:05:02,747 [DEBUG] : Retrieving configuration...
2019-05-21 10:05:03,075 [DEBUG] : Updating local config
2019-05-21 10:05:03,079 [DEBUG] : Checking version.
2019-05-21 10:05:03,079 [DEBUG] : No installer found.
2019-05-21 10:05:03,079 [DEBUG] : Update needed to version 7.1.110.1
2019-05-21 10:05:03,430 [DEBUG] : Waiting for schedule...
2019-05-21 10:05:03,431 [DEBUG] : Waiting for next scheduled scan...

Verified the cloud relay key in /opt/Lansweeperagent/lsagentconfiguration.xml - All seems fine.

Is there any other setting that I need to turn on to make this work? Thanks

PS - I'm assuming the error associated with not being able to contact the local lansweeper sever can be ignored since these machines are going to be outside our office network.

[Susan_A · Accepted solution]

I just wanted to post some updated information for anyone who might be reading this topic. The behavior reported by the customer can occur if scanning exclusions exist for the client machines under Scanning\Scanning Targets in the web console. It is important to keep in mind that an exclusion will prevent an asset from being scanned by any scanning method, even by the LsAgent or LsPush scanning agent.

[Esben_D]

What's your scanning schedule set to? It almost seems like it is still waiting to be triggered.

You can also update to the latest hotfix version just released: https://www.lansweeper.com/update-lansweeper/

If it still doesn't show up after some time, you can take a look at your Lansweeper errorlog or contact support.

[rpokkyarath]

Esben.D wrote:

If it still doesn't show up after some time, you can take a look at your Lansweeper errorlog or contact support.

I see that the scan output is present in my /var/log/LansweeperAgentService.log. So it seems to be running daily but the results are not getting pushed to the Lansweeper servers or the local console is not able to pull it down.

The LansweeperAgentService.err has a few errors, though none of it looks important enough to cause the issue

/bin/bash: xl: command not found
/bin/bash: prtdiag: command not found
/bin/bash: /usr/sbin/prtdiag: No such file or directory
/bin/bash: /usr/sbin/eeprom: No such file or directory
uname: invalid option -- 'X'
Try 'uname --help' for more information.
/bin/bash: lshal: command not found

[rpokkyarath]

Esben.D wrote:
What's your scanning schedule set to? It almost seems like it is still waiting to be triggered.

Thank you. I looked into the lsagentconfiguration.xml again and see this section below. I assume these values are auto-populated since I don't recall providing any of these values at install time. The StartDateTime is set to 05/22/2019 (today) even though I installed this 3-4 days ago. Not sure if this file is getting updated daily with the next scan time. I see a huge value for 'Interval' and not sure what that even means.

	<LsAgentConfigItem>
		<Type>Trigger</Type>
		<Settings>
			<DataItem>
				<Key>Type</Key>
				<Value>FullScan</Value>
			</DataItem>
			<DataItem>
				<Key>ScheduleName</Key>
				<Value>Daily at Midday</Value>
			</DataItem>
			<DataItem>
				<Key>StartDateTime</Key>
				<Value>05/22/2019 01:37:12</Value>
			</DataItem>
			<DataItem>
				<Key>Interval</Key>
				<Value>864000000000</Value>
			</DataItem>
			<DataItem>
				<Key>WeekDays</Key>
				<Value>0</Value>
			</DataItem>
			<DataItem>
				<Key>MonthDays</Key>
				<Value>0</Value>
			</DataItem>
			<DataItem>
				<Key>ExecutionMode</Key>
				<Value>Daily</Value>
			</DataItem>
		</Settings>
	</LsAgentConfigItem>

Have sent an email to support. Will check the latest installer version as well.