Hi Guys. I looked at my reporting today and discovered that the graphs for Internal and External are blank. Is there a bug that I missed or do I need to reset something
Which version? That normally indicates that the SNMP server is not running , therefore no data could be collected. The selfmonitoring check for the SNMP server is in since 5.011.
I'm running 5.022. I have rebooted and restarted the deamon and I am getting partial graphs now. I think it may have been due to the last up2date. I will re post after 24 hours
If you encounter such a case and you are running the latest version, can you please check the /etc/no-selfmonitoring directory and the selfmonitoring log file for SNMPd related data? This might help us in tracking why this happens although the selfmonitoring normally checks the SNMPd.
Now (with everything riunning) I took a look at /etc/no-selfmonitoring. There is nothing about snmp.
In the selfmon-log I found only 2004:09:14-23:34:56 (none) selfmonng[3826]: Loading Selfmonitoring Check 'snmpd_running' Yesterday's logfile is empty. But snmpd wasn't running til noon.
Mybe it's would be a good thing to notify the user that disabling snmp will also stop the network reporting graph to work. You can not expect form people that they know this [;)]
As I found out yesterday, the traffic graphs weren't updates since wednesday. The directory /etc/no-selfmonitor contained the file snmpd; the logfile /var/log/selfmon/..... contained only the snmpd-line: Loading Selfmonitoring Check 'snmpd_running'
I removed the snmpd-file, snmpd was restartet and the graphs get updated.
The problem still apears on V5.100. The directory /etc/no-selfmonitor contained the file snmpd after I rebooted the firewall. After removing this file the graphics got updated. The question is why that file is written....
We found the source of that problem - a race condition in the snmpd init script. This bug is already fixed and ready to be released in one of the next up2dates.
We found the source of that problem - a race condition in the snmpd init script. This bug is already fixed and ready to be released in one of the next up2dates.
