After doing OS updates on 4.4.11-23.53.amzn1.x86_64 the ssh meminfo sensor fails with: The host's system is unable to process PRTG's command: "cat /proc/meminfo". (code: PE096) The failures are intermittent but consistent. Is there something on the OS that needs to be configured so this works again?
ssh meminfo sensor failures
Votes:
0
3 Replies
Votes:
0
Hello,
We will need some more details:
- Which distribution do you use?
- Which permissions has a user to run this command?
- What is the output of this command if you run it the command line?
Created on Jun 17, 2016 12:17:32 PM by
Votes:
0
14.2.10.2114 x64
Full Permissions
Output: cat /proc/meminfo
MemTotal: 7662540 kB MemFree: 1864772 kB MemAvailable: 6041760 kB Buffers: 415852 kB Cached: 3562904 kB SwapCached: 0 kB Active: 3107416 kB Inactive: 1979184 kB Active(anon): 1107948 kB Inactive(anon): 17908 kB Active(file): 1999468 kB Inactive(file): 1961276 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 17936 kB Writeback: 0 kB AnonPages: 1107848 kB Mapped: 41696 kB Shmem: 18008 kB Slab: 527324 kB SReclaimable: 469660 kB SUnreclaim: 57664 kB KernelStack: 13488 kB PageTables: 133912 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 3831268 kB Committed_AS: 14363380 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB AnonHugePages: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 12288 kB DirectMap2M: 7852032 kB
Last change on Jun 20, 2016 10:57:01 AM by
Votes:
0
Hello,
Kindly note that we cannot go into debugging of outdated PRTG versions (e.g. PRTG v 14), as in the meantime we introduced several improvements and bug fixes in SSH sensors.
If possible, please first update your PRTG installation to the latest version. If the issue still persists, please open a support ticket and send us the screenshots of the sensor. Please also enable debug logging (sensor Settings -> Result Handling -> Write sensor result to disk) and send us the result file in the ticket as well.
As an immediate help, please try restarting the target system as well as the PRTG Probe. Once this is done, please set the sensor to run on a longer scanning interval (at least 300 seconds).
Created on Jun 20, 2016 11:12:58 AM by
Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Add comment