lansweeper:lsagent_troubleshooting
Table of Contents
LSAgent op Linux
context
dit document beschrijft wat troubleshooting van LSAgent
nakijken laatste verbinding
- voer volgende query uit:
Select Top 1000000 tblAssets.AssetID, tblAssets.AssetName, tsysAssetTypes.AssetTypename, tsysAssetTypes.AssetTypeIcon10 As icon, tblAssets.IPAddress, tblAssets.LastLsAgent From tblAssets Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID Inner Join tsysAssetTypes On tsysAssetTypes.AssetType = tblAssets.Assettype Inner Join tblLsAgentAsset On tblAssets.AssetID = tblLsAgentAsset.AssetID Where tblAssetCustom.State = 1 Order By tblAssets.LastLsAgent Desc
- dit geeft je een tijdstip waarop de laaste imports zijn gedaan
- doorzoek Errorlog.txt en zoek naar entries rond dat tijdstip
- activeer debug.
zo ziet een gebruikelijke sync actie (5 minuut interval) met Relay eruit:2021-01-11 09:57:52,424 [1] INFO LogLsAgent set to Debug 2021-01-11 09:59:29,081 [28] INFO LOGLSAGENT DEBUG Synchronize configuration schedule triggered. 2021-01-11 09:59:29,331 [28] INFO LOGLSAGENT DEBUG Syncing 0 updated groups and 0 updated assets with relay 2021-01-11 09:59:29,393 [38] INFO LOGLSAGENT DEBUG Synchronize assets schedule triggered. 2021-01-11 09:59:29,487 [38] INFO LOGLSAGENT DEBUG Requesting scans from relay... 2021-01-11 09:59:32,659 [38] INFO LOGLSAGENT DEBUG Scanfile identified as Windows. 2021-01-11 10:04:41,346 [52] INFO LOGLSAGENT DEBUG Synchronize configuration schedule triggered. 2021-01-11 10:04:41,877 [52] INFO LOGLSAGENT DEBUG Syncing 1 updated groups and 1 updated assets with relay
meer info
- interessante case hiervoor.
lansweeper/lsagent_troubleshooting.txt · Last modified: 2021/01/13 11:47 by koen