Zurück
-
Titel
fglam-temp-xx.sh scripts in /tmp directory on Linux host -
Beschreibung
Script file is empty but foglight not cleaning up in /tmp directory leaving lots of files every 1 to 4 minutes.-rw------- 1 opc opc 0 Feb 4 10:27 fglam-temp-3de9eec2-3943-4928-bfaf-c97721e5b1a8.sh-rw------- 1 opc opc 0 Feb 4 10:31 fglam-temp-1afe0605-e292-4ba1-8453-bbe387a39aa6.sh-rw------- 1 opc opc 0 Feb 4 10:31 fglam-temp-1a86ad71-ac1c-4c43-aa3f-bf0a9afbd3eb.sh-rw------- 1 opc opc 0 Feb 4 10:32 fglam-temp-e26beef1-fe76-4794-a401-95ebe9f2101f.sh-rw------- 1 opc opc 0 Feb 4 10:36 fglam-temp-33fe8301-c952-4adf-a51f-bd706e908aae.shWe see SSH session errors when trying to remotely execute the file cleanup such as /usr/bin/env LC_ALL=C rm -f /tmp/fglam-temp-1d52da30-7c56-43ba-a71d-32d534b6228d.shENV: Windows FglAm client monitoring remote Linux host with UnixAgentPlus agent.Agent Log -- Monitor@MyLinuxHost_2020-01-22_055103_007.log2020-02-04 12:58:03.481 WARN [Quartz[0]-33415] com.quest.glue.core.remoteconnection.ssh.SSHGanymedConnectionImpl - Could not execute the remote command [/usr/bin/env LC_ALL=C rm -f /tmp/fglam-temp-1d52da30-7c56-43ba-a71d-32d534b6228d.sh] to clean up the temporarily uploaded script after execution.com.quest.glue.api.services.ConnectionBrokenException: SSH session could not be opened...Caused by: java.io.IOException: Sorry, this connection is closed.Caused by: java.net.SocketException: Connection reset -
Lösung
STATUS: Tried the following but the test was successful. Used Workaround listed in step 5.You may have to search for a SSH server or client software to put on your Windows FglAm perform a test.1. Connection reset is usually caused by the server side (the target host in this case) or firewall/routers.2. Install a ssh client on the Windows FglAM host, connect via SSH to the monitored host and run the following command to check whether it also shows connect resets./usr/bin/env LC_ALL=C rm -f /tmp/fglam-temp-5aab309f-1747-4785-852d-dcac09a147c7.sh3. Check /etc/ssh/sshd_config file for settings.4. Review sshd log file's last 100 lines:journalctl -u sshd -n 100 > sshlog.txt5. Workaround: Create cron job on Linux host to periodically delete the tmp files.rm /tmp/fglam-temp-*