Meh. Imagined connections. We all know the plague of people blaming a random unrelated change for some other issue.

Nothing has changed to how storage works for a very very long time beyond removing the -state table, which if anything should make this sort of thing significantly less likely.

What exactly is the problem? It's not very well explained.

Adam.

Sent from BlueMail

On 7 Aug 2017, at 23:33, Tom Laermans <tom.laermans@powersource.cx> wrote:

Tim,

Hm. That's odd. Maybe Adam has any idea?

Tom

On 08/08/2017 00:28, Timothy Illguth wrote:

t seems to have been an issue after we went pro. When we were on CE we didn't have this problem

-Tim

On Mon, Aug 7, 2017 at 1:26 PM, Tom Laermans <tom.laermans@powersource.cx> wrote:

Are you running the C or Pro?

If I recall correctly, a number of tables containing such data were memory tables in CE. They have been converted to on-disk ones in Pro.
This means if you reset MySQL on the Observium servers the data is gone until next discovery (or poll?).

Tom

On 07/08/2017 20:41, Timothy Illguth wrote:

Hello Support,

Any advice on fixing observium so it doesn't drop reading storage? 

This seems to happen at random. I'll reboot the observium server and it comes up reading random machines as 0 storage. 

Thanks

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