Description: Occasionally when sending an inventory scan from a Linux or Unix agent (64-bit agent) the scan will not be received by the core.
Cause: If map-scheduler and map-scraper encounter an error of just about any type the process will halt. This is by current design however this is scheduled to be changed in a future release of the Linux/Unix agent.
Resolution: If the problem is fixed the scan should complete normally. Note: Depending on how busy the server is the scan can take a long time to complete. If no errors are found using the troubleshooting help below then provide the server plenty of time to finish.
Example error: "map-fetchvuldefs: Failed to retrieve vulnerability definitions."
Exampe resolution: This error was caused by name resolution issues. Once a proper resolution was entered into /etc/hosts the scan completed correctly.
Troubleshooting help:
- After fixing the problem restart the map-scheduler and the scan should proceed: "/etc/init.d/map-scheduler stop" then "/etc/init.d/map-scheduler start". On HPUX the path is different: /sbin/init.d/map-scheduler stop/start.
- Check the following logs for errors:
/opt/landesk/logs/scheduler.log
/opt/landesk/logs/landesk.log
/opt/landesk/logs/vulscan.log
- Check the errorscan folder: /opt/landesk/scan_repository/errorscan
- Clean up the /opt/landesk/jobs folder. Normally only the following files are present: "ldiscan_daily.xml", "startup_scan.xml", and "vulscan_daily.xml". All other files are tasks/scans in process. Checking the date of the files may indicate how long they've been stuck. See above note...the agent may need plenty of time on a busy server.