Hello Support,
Any advice on fixing observium so it doesn't drop reading storage?
[image: Inline image 1] This seems to happen at random. I'll reboot the observium server and it comes up reading random machines as 0 storage.
Thanks
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?
Inline image 1 This seems to happen at random. I'll reboot the observium server and it comes up reading random machines as 0 storage.
Thanks
-- ___________________________ Tim Illguth Jr. Systems Administrator Alaska Satellite Facility (907) 474-7924
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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?
[image: Inline image 1] This seems to happen at random. I'll reboot the observium server and it comes up reading random machines as 0 storage.
Thanks
-- ___________________________ Tim Illguth Jr. Systems Administrator Alaska Satellite Facility (907) 474-7924
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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 mailto: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? Inline image 1 This seems to happen at random. I'll reboot the observium server and it comes up reading random machines as 0 storage. Thanks
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, 23:33, 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 mailto: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-diskones
in Pro. This means if you reset MySQL on the Observium servers the datais
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 readingstorage?
Inline image 1 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
On 08/08/2017 00:50, Adam Armstrong wrote:
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.
Exactly - that was the first and only thing to come into my mind, it should be better now. :-)
Tom
If you guys don't know why your software is not working properly just say so.
On Mon, Aug 7, 2017 at 2:50 PM, Adam Armstrong adama@memetic.org wrote:
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 http://www.bluemail.me/r?b=10256 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?
[image: Inline image 1] 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
Looks like user error.
On 08/08/2017 01:09, Timothy Illguth wrote:
If you guys don't know why your software is not working properly just say so.
On Mon, Aug 7, 2017 at 2:50 PM, Adam Armstrong <adama@memetic.org mailto:adama@memetic.org> wrote:
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.
Great, how do I fix it?
On Mon, Aug 7, 2017 at 3:13 PM, Tom Laermans tom.laermans@powersource.cx wrote:
Looks like user error.
On 08/08/2017 01:09, Timothy Illguth wrote:
If you guys don't know why your software is not working properly just say so.
On Mon, Aug 7, 2017 at 2:50 PM, Adam Armstrong adama@memetic.org wrote:
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.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Replace the user?
On 08/08/2017 01:15, Timothy Illguth wrote:
Great, how do I fix it?
On Mon, Aug 7, 2017 at 3:13 PM, Tom Laermans <tom.laermans@powersource.cx mailto:tom.laermans@powersource.cx> wrote:
Looks like user error. On 08/08/2017 01:09, Timothy Illguth wrote:If you guys don't know why your software is not working properly just say so. On Mon, Aug 7, 2017 at 2:50 PM, Adam Armstrong <adama@memetic.org <mailto:adama@memetic.org>> wrote: 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.
Have I got the wrong idea? is this not a support channel?
On Mon, Aug 7, 2017 at 3:17 PM, Tom Laermans tom.laermans@powersource.cx wrote:
Replace the user?
On 08/08/2017 01:15, Timothy Illguth wrote:
Great, how do I fix it?
On Mon, Aug 7, 2017 at 3:13 PM, Tom Laermans tom.laermans@powersource.cx wrote:
Looks like user error.
On 08/08/2017 01:09, Timothy Illguth wrote:
If you guys don't know why your software is not working properly just say so.
On Mon, Aug 7, 2017 at 2:50 PM, Adam Armstrong adama@memetic.org wrote:
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.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
This is a user discussion list.
adam. On 08/08/2017 00:18:56, Timothy Illguth tillguth@alaska.edu wrote: Have I got the wrong idea? is this not a support channel?
On Mon, Aug 7, 2017 at 3:17 PM, Tom Laermans <tom.laermans@powersource.cx [mailto:tom.laermans@powersource.cx]> wrote:
Replace the user?
On 08/08/2017 01:15, Timothy Illguth wrote:
Great, how do I fix it?
On Mon, Aug 7, 2017 at 3:13 PM, Tom Laermans <tom.laermans@powersource.cx [mailto:tom.laermans@powersource.cx]> wrote:
Looks like user error.
On 08/08/2017 01:09, Timothy Illguth wrote:
If you guys don't know why your software is not working properly just say so.
On Mon, Aug 7, 2017 at 2:50 PM, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
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.
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
--
___________________________ Tim Illguth Jr. Systems Administrator Alaska Satellite Facility (907) 474-7924
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong -
Timothy Illguth -
Tom Laermans