Now that you mention that, it makes sense there could be a new processor ID. There was a kernel update. That very well could cause that.
On Mon, Jun 15, 2015 at 1:02 AM, Peter Persson peter.persson@bredband2.se wrote:
Hey,
I've seen this on several machines that have rebooted, so the processor have gotten a new id via SNMP. I think it would be that kind of discovery that have caused it.
Regards, Peter
2015-06-13 0:51 GMT+02:00 Jason Vanlandingham van.sjason@gmail.com:
I had a problem with the machine Observium is running on. The CPU fan/heatsink fell off. After I got the machine up again on the evening
of 11
June, the CPU Temp graph showed normal temps in the 30-45 range for
months,
then a big spike up to 115. (eek!) But at least the server came back to life, and I still had all my data.
Everything still seems to be running OK, but all of a sudden there is
now no
data at all in the CPU temp graph before ~1:00AM 12 June. From this
machine
I get temp readings for CPU temp, Motherboard temp, and 4 other "temp#" listings. "Temp1" and "Temp3" still seem to have the data they should,
but
the others are missing.
One thing I did change after the recovery: I noticed the time zone on the server was set to US Eastern, and I changed it to US Central. I would
think
if that was the cause of my problem it would hit a lot more of the data.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium