Hey. I have a server with FreeBSD operating system. I want to create a free sensor monitoring disk space in SNMP Disk Free template, but get an error - "Could not find any matching data on this device (code: PE187).". On the server with the operating system, this sensor is installed without any problems. How can I keep track of free disk space on the server with FreeBSD operating system?

Article Comments

Is SNMP configured correctly on the FreeBSD host (exposing the disks)?
Firewall also allows SNMP requests? Do other SNMP based sensors, like SNMP uptime work properly?


Jan, 2017 - Permalink

Hey. I set up some LUTS sensors on FreeBSD: Storage /, type: ufs, dev: / dev / gpt / rootfs / Size, HOST-RESOURCES-MIB :: hrStorageUsed.4, SNMP CPU Load, SNMP Messages In, they all work, then SNMP server is running. Storage /, type: ufs, dev: / dev / gpt / rootfs / Size shows me the disk volume, but does not show how much free space is left. I have a Linux server on which I have set up the sensor - Disk Free: /, where there is Total, Free Bytes, Free Space in%. But when I turn like a sensor on FreeBSD, I have an error occurs.


Jan, 2017 - Permalink

You mean the error occurs with the SSH Disk Free sensors on FreeBSD?


Jan, 2017 - Permalink

No, I say that the error I get when SNMP Disk Free Sensor is turned on - error Could not find any matching data on this device. (Code: PE187), SNMP Linux Physical Disk - error Could not find any disk on this device. (Code: PE188). SNMP Sensor Disk Free Sensor - Error No such object (SNMP error # 222). SSH sensor I do not need.


Jan, 2017 - Permalink

Is it possible that the disks are not included in your SNMP config? Could you post the entire configuration here? I won't publish it so that only support can see it.


Feb, 2017 - Permalink

disk /

Can you put this at the end of your config and restart the snmpd service? Then the disk sensors should work. Given that the rest is configured correctly and SNMP Uptime works.


Feb, 2017 - Permalink

We added at the end of the configuration disk / and we stopped working SNMPD service.

Log: Feb 2 12:21:15 rproxy-node-a snmpd[74444]: bad character '/' Feb 2 12:21:15 rproxy-node-a snmpd[74444]: in file /etc/snmpd.config line 303 Feb 2 12:21:15 rproxy-node-a snmpd[74444]: error in config file

FreeBSD 10.1-RELEASE Begemot simple SNMP daemon. Copyright (c) 2001-2002 Fraunhofer Institute for Open Communication Systems (FhG Fokus). All rights reserved. Copyright (c) 2010 The FreeBSD Foundation. All rights reserved.


Feb, 2017 - Permalink

Strange, that should work according to FreeBSD. Could you try using includeAllDisks 10% instead?


Feb, 2017 - Permalink

I do not quite understand what you mean. Please explain more what we need to do. Thank you.


Feb, 2017 - Permalink

Sorry if my previous post was ambiguous. Simply execute the following, remember to modify the path to your snmpd.conf according to your system: 

echo includeAllDisks 10% >> /etc/conf.d/snmpd.conf

Then restart the snmpd service. Does that work, i.e. does the service start again and do the sensors work afterwards?


Feb, 2017 - Permalink

Just out of curiosity, did you already try to use the SSH Disk Free sensor?


Feb, 2017 - Permalink