New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


SSH Memory Sensor: error code: PE094

Votes:

1

Your Vote:

Up

Down

Hallo,

we have Updated our PRTG few days ago to ver. 20.2.59.1689. Our Linux Servers with Linux Ubuntu 32 bit Ver. 12.04.4 LTS and Linux Ubuntu 32 bit Ver. 12.04.5 LTS giving the error code PE094. The device you want to monitor is not compatible. The sensor cannot parse the reply data.

According to release notes the problem was fixed with the ver. 20.2.59.1689

I have tried to recreate the sensor but the new one showing the same error.

Best Regards,

memory pe094 ssh

Created on Jun 4, 2020 8:17:34 AM by  InfraK (1) 1



8 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

Thank you for your post.

According to our development the issue appears if a different shell is being used instead of the "bash"-shell. Which shell are you using?

Can you change it to "bash" (if not set already), and check if the sensor works afterwards?


Kind regards,
Sasa Ignjatovic, Tech Support Team

Created on Jun 4, 2020 1:01:45 PM by  Sasa Ignjatovic [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Sasa,

thanks a lot for your reply. We are already using bash shell.

Regards, Khaldon

Created on Jun 5, 2020 10:57:08 AM by  InfraK (1) 1



Votes:

0

Your Vote:

Up

Down

Hello Khaldon,

Can you please check if you have "/proc/zoneinfo" on the target system?


Kind regards,
Sasa Ignjatovic, Tech Support Team

Created on Jun 8, 2020 11:11:47 AM by  Sasa Ignjatovic [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Sasa,

yes, it is available and contains the following information. I noticed that the query worked twice in the last 48 hours. And then After that, the same error appeared.

https://drive.google.com/file/d/11jR6oI05_gO20LvJawZguoUTlxj6m6FR/view?usp=sharing

Regards, Khaldon

Node 0, zone      DMA
  pages free     1565
        min      196
        low      245
        high     294
        scanned  0
        spanned  4080
        present  3951
        managed  3979
    nr_free_pages 1565
    nr_inactive_anon 0
    nr_active_anon 0
    nr_inactive_file 906
    nr_active_file 1199
    nr_unevictable 0
    nr_mlock     0
    nr_anon_pages 0
    nr_mapped    0
    nr_file_pages 2105
    nr_dirty     0
    nr_writeback 0
    nr_slab_reclaimable 76
    nr_slab_unreclaimable 97
    nr_page_table_pages 0
    nr_kernel_stack 0
    nr_unstable  0
    nr_bounce    0
    nr_vmscan_write 832046
    nr_vmscan_immediate_reclaim 478490
    nr_writeback_temp 0
    nr_isolated_anon 0
    nr_isolated_file 0
    nr_shmem     0
    nr_dirtied   69261253
    nr_written   69370368
    nr_anon_transparent_hugepages 0
    nr_free_cma  0
        protection: (0, 869, 4039, 4039)
  pagesets
    cpu: 0
              count: 0
              high:  0
              batch: 1
  vm stats threshold: 4
    cpu: 1
              count: 0
              high:  0
              batch: 1
  vm stats threshold: 4
  all_unreclaimable: 0
  start_pfn:         16
  inactive_ratio:    1
Node 0, zone   Normal
  pages free     44321
        min      11054
        low      13817
        high     16581
        scanned  0
        spanned  224254
        present  222502
        managed  204371
    nr_free_pages 44321
    nr_inactive_anon 23691
    nr_active_anon 21334
    nr_inactive_file 18091
    nr_active_file 17620
    nr_unevictable 0
    nr_mlock     0
    nr_anon_pages 43809
    nr_mapped    732
    nr_file_pages 47672
    nr_dirty     2
    nr_writeback 0
    nr_slab_reclaimable 74236
    nr_slab_unreclaimable 3994
    nr_page_table_pages 25
    nr_kernel_stack 312
    nr_unstable  0
    nr_bounce    0
    nr_vmscan_write 1004451
    nr_vmscan_immediate_reclaim 763443
    nr_writeback_temp 0
    nr_isolated_anon 0
    nr_isolated_file 0
    nr_shmem     10
    nr_dirtied   33599361
    nr_written   45069003
    nr_anon_transparent_hugepages 0
    nr_free_cma  0
        protection: (0, 0, 25366, 25366)
  pagesets
    cpu: 0
              count: 60
              high:  186
              batch: 31
  vm stats threshold: 16
    cpu: 1
              count: 181
              high:  186
              batch: 31
  vm stats threshold: 16
  all_unreclaimable: 0
  start_pfn:         4096
  inactive_ratio:    1
Node 0, zone  HighMem
  pages free     18745
        min      128
        low      10210
        high     20293
        scanned  0
        spanned  1082370
        present  811737
        managed  820194
    nr_free_pages 18745
    nr_inactive_anon 124169
    nr_active_anon 124170
    nr_inactive_file 275732
    nr_active_file 274316
    nr_unevictable 0
    nr_mlock     0
    nr_anon_pages 246477
    nr_mapped    2985
    nr_file_pages 569638
    nr_dirty     4
    nr_writeback 0
    nr_slab_reclaimable 0
    nr_slab_unreclaimable 0
    nr_page_table_pages 1847
    nr_kernel_stack 0
    nr_unstable  0
    nr_bounce    0
    nr_vmscan_write 25946022
    nr_vmscan_immediate_reclaim 33099813
    nr_writeback_temp 0
    nr_isolated_anon 0
    nr_isolated_file 0
    nr_shmem     129
    nr_dirtied   0
    nr_written   0
    nr_anon_transparent_hugepages 0
    nr_free_cma  0
        protection: (0, 0, 0, 0)
  pagesets
    cpu: 0
              count: 107
              high:  186
              batch: 31
  vm stats threshold: 24
    cpu: 1
              count: 161
              high:  186
              batch: 31
  vm stats threshold: 24
  all_unreclaimable: 0
  start_pfn:         228350
  inactive_ratio:    5

Created on Jun 9, 2020 8:24:22 AM by  InfraK (1) 1



Votes:

1

Your Vote:

Up

Down

Hello Khaldon,

Can you please thy the "Compatibility Mode" as the "SSH Engine" in the sensor settings. Does the sensor work afterwards?


Kind regards,
Sasa Ignjatovic, Tech Support Team

Created on Jun 10, 2020 7:17:38 AM by  Sasa Ignjatovic [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Sasa,

it worked in "compatibility mode".

Regards, Khaldon

Created on Jun 10, 2020 10:03:02 AM by  InfraK (1) 1



Votes:

0

Your Vote:

Up

Down

Hello Sasa,

will this workaround be considered as solution to this problem? According to documentation the "compatibility mode" might removed from PRTG soon. Could you please make a statement?


Compatibility Mode (deprecated): Try this legacy method only if the default mode does not work on a target device. The compatibility mode is the SSH engine that PRTG used in previous versions. It is deprecated. We will remove this legacy option soon, so try to get your SSH sensors running with the default SSH engine.


Regards, Khaldon

Created on Jun 17, 2020 9:42:29 AM by  InfraK (1) 1



Votes:

0

Your Vote:

Up

Down

Hello Khaldon,

We are still investigating this issue, so the compatibility mode will not be removed until the default settings is fixed. Also, please keep an eye on our release notes for any changes to the SSH Meminfo sensor.


Kind regards,
Sasa Ignjatovic, Tech Support Team

Created on Jun 17, 2020 12:49:06 PM by  Sasa Ignjatovic [Paessler Support]



Please log in or register to enter your reply.


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.