Storage sizes flapping between actual size and 0B after upgrading to latest Pro from CE
Below is an example of one system (there are quite a few more doing the same thing) that seems to flap between storage sizes 0B and actual size consistently. I am wondering if there are any known issues that may be causing this behavior. The affected systems are VMs running Centos6 on a Centos6 VMhost running KVM.
Any ideas???
Thanks in advance!
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 265GB (/tmp) 2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 4.68GB (/home) 2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 476MB (/boot) 2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 15.2GB (/) 2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 265GB -> 0B (/tmp) 2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 4.68GB -> 0B (/home) 2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 476MB -> 0B (/boot) 2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 15.2GB -> 0B (/)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 265GB (/tmp) 2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 4.68GB (/home) 2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 476MB (/boot) 2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 15.2GB (/) 2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 265GB -> 0B (/tmp) 2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 4.68GB -> 0B (/home) 2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 476MB -> 0B (/boot) 2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 15.2GB -> 0B (/)
Hi Michael,
I don't know of any known issues, it would be good if you'd be able to capture the going to 0B in a poller debug log (./poller.php -h scaleout7* -m storage -d)
Tom
On 25/05/2017 23:57, Michael Rohl wrote:
Below is an example of one system (there are quite a few more doing the same thing) that seems to flap between storage sizes 0B and actual size consistently. I am wondering if there are any known issues that may be causing this behavior. The affected systems are VMs running Centos6 on a Centos6 VMhost running KVM.
Any ideas???
Thanks in advance!
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 15.2GB -> 0B (/)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 15.2GB -> 0B (/)
-- Michael Rohl System Administrator Alaska Satellite Facility 907.474.7864 mjrohl@alaska.edu mailto:mjrohl@alaska.edu
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Tom
Seeing same behaviour also even on cisco routers:
Storage size changed: 1B -> 55.2MB (flash device on switch 1)
It doesn't happen on every poll - we're seeing it every couple of hours but its happening for any of our servers or other devices with storage.
Observium 17.5.8561 (rolling)
I've tried to capture it with poller debug as above but can't get it at 0B
Brians
On Fri, May 26, 2017 at 7:38 AM, Tom Laermans tom.laermans@powersource.cx wrote:
Hi Michael,
I don't know of any known issues, it would be good if you'd be able to capture the going to 0B in a poller debug log (./poller.php -h scaleout7* -m storage -d)
Tom
On 25/05/2017 23:57, Michael Rohl wrote:
Below is an example of one system (there are quite a few more doing the same thing) that seems to flap between storage sizes 0B and actual size consistently. I am wondering if there are any known issues that may be causing this behavior. The affected systems are VMs running Centos6 on a Centos6 VMhost running KVM.
Any ideas???
Thanks in advance!
2017-05-25 13:40:13 scaleout7 /tmp Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:40:13 scaleout7 /home Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:40:13 scaleout7 /boot Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:40:13 scaleout7 / Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:37:54 scaleout7 /tmp Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:37:54 scaleout7 /home Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:37:54 scaleout7 /boot Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:37:54 scaleout7 / Storage size changed: 15.2GB -> 0B (/)
2017-05-25 13:35:15 scaleout10 /tmp Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:35:15 scaleout10 /home Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:35:15 scaleout10 /boot Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:35:15 scaleout10 / Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:32:09 scaleout10 /tmp Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:32:09 scaleout10 /home Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:32:09 scaleout10 /boot Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:32:09 scaleout10 / Storage size changed: 15.2GB -> 0B (/)
-- Michael Rohl System Administrator Alaska Satellite Facility 907.474.7864 mjrohl@alaska.edu
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
Fixed in r8576.
Brian : wrote:
Hi Tom
Seeing same behaviour also even on cisco routers:
Storage size changed: 1B -> 55.2MB (flash device on switch 1)
It doesn't happen on every poll - we're seeing it every couple of hours but its happening for any of our servers or other devices with storage.
Observium 17.5.8561 (rolling)
I've tried to capture it with poller debug as above but can't get it at 0B
Brians
On Fri, May 26, 2017 at 7:38 AM, Tom Laermans tom.laermans@powersource.cx wrote:
Hi Michael,
I don't know of any known issues, it would be good if you'd be able to capture the going to 0B in a poller debug log (./poller.php -h scaleout7* -m storage -d)
Tom
On 25/05/2017 23:57, Michael Rohl wrote:
Below is an example of one system (there are quite a few more doing the same thing) that seems to flap between storage sizes 0B and actual size consistently. I am wondering if there are any known issues that may be causing this behavior. The affected systems are VMs running Centos6 on a Centos6 VMhost running KVM.
Any ideas???
Thanks in advance!
2017-05-25 13:40:13 scaleout7 /tmp Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:40:13 scaleout7 /home Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:40:13 scaleout7 /boot Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:40:13 scaleout7 / Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:37:54 scaleout7 /tmp Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:37:54 scaleout7 /home Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:37:54 scaleout7 /boot Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:37:54 scaleout7 / Storage size changed: 15.2GB -> 0B (/)
2017-05-25 13:35:15 scaleout10 /tmp Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:35:15 scaleout10 /home Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:35:15 scaleout10 /boot Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:35:15 scaleout10 / Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:32:09 scaleout10 /tmp Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:32:09 scaleout10 /home Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:32:09 scaleout10 /boot Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:32:09 scaleout10 / Storage size changed: 15.2GB -> 0B (/)
-- Michael Rohl System Administrator Alaska Satellite Facility 907.474.7864 mjrohl@alaska.edu
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
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Thanks Mike - updated and confirmed!
On Sat, May 27, 2017 at 10:22 AM, Mike Stupalov mike@observium.org wrote:
Fixed in r8576.
Brian : wrote:
Hi Tom
Seeing same behaviour also even on cisco routers:
Storage size changed: 1B -> 55.2MB (flash device on switch 1)
It doesn't happen on every poll - we're seeing it every couple of hours but its happening for any of our servers or other devices with storage.
Observium 17.5.8561 (rolling)
I've tried to capture it with poller debug as above but can't get it at 0B
Brians
On Fri, May 26, 2017 at 7:38 AM, Tom Laermans tom.laermans@powersource.cx wrote:
Hi Michael,
I don't know of any known issues, it would be good if you'd be able to capture the going to 0B in a poller debug log (./poller.php -h scaleout7* -m storage -d)
Tom
On 25/05/2017 23:57, Michael Rohl wrote:
Below is an example of one system (there are quite a few more doing the same thing) that seems to flap between storage sizes 0B and actual size consistently. I am wondering if there are any known issues that may be causing this behavior. The affected systems are VMs running Centos6 on a Centos6 VMhost running KVM.
Any ideas???
Thanks in advance!
2017-05-25 13:40:13 scaleout7 /tmp Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:40:13 scaleout7 /home Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:40:13 scaleout7 /boot Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:40:13 scaleout7 / Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:37:54 scaleout7 /tmp Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:37:54 scaleout7 /home Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:37:54 scaleout7 /boot Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:37:54 scaleout7 / Storage size changed: 15.2GB -> 0B (/)
2017-05-25 13:35:15 scaleout10 /tmp Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:35:15 scaleout10 /home Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:35:15 scaleout10 /boot Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:35:15 scaleout10 / Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:32:09 scaleout10 /tmp Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:32:09 scaleout10 /home Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:32:09 scaleout10 /boot Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:32:09 scaleout10 / Storage size changed: 15.2GB -> 0B (/)
-- Michael Rohl System Administrator Alaska Satellite Facility 907.474.7864 mjrohl@alaska.edu
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
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Mike Stupalov Observium Limited, http://observium.org
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
When I updated observium today, I had a large run of systems fix their 0B disk space to the correct size. But then I noticed one host has flapped back to 0B. I then ran the debug on it. Attached my debug of this system.
Thanks
Mike
On Thu, May 25, 2017 at 10:38 PM, Tom Laermans tom.laermans@powersource.cx wrote:
Hi Michael,
I don't know of any known issues, it would be good if you'd be able to capture the going to 0B in a poller debug log (./poller.php -h scaleout7* -m storage -d)
Tom
On 25/05/2017 23:57, Michael Rohl wrote:
Below is an example of one system (there are quite a few more doing the same thing) that seems to flap between storage sizes 0B and actual size consistently. I am wondering if there are any known issues that may be causing this behavior. The affected systems are VMs running Centos6 on a Centos6 VMhost running KVM.
Any ideas???
Thanks in advance!
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:40:13 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:37:54 scaleout7 https://mon.asf.alaska.edu/device/device=27/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=27/tab=health/metric=storage/ Storage size changed: 15.2GB -> 0B (/)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 265GB (/tmp)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 4.68GB (/home)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 476MB (/boot)
2017-05-25 13:35:15 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 0B -> 15.2GB (/)
2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /tmp https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 265GB -> 0B (/tmp)
2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /home https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 4.68GB -> 0B (/home)
2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ /boot https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 476MB -> 0B (/boot)
2017-05-25 13:32:09 scaleout10 https://mon.asf.alaska.edu/device/device=30/tab=logs/section=eventlog/ / https://mon.asf.alaska.edu/device/device=30/tab=health/metric=storage/ Storage size changed: 15.2GB -> 0B (/)
-- Michael Rohl System Administrator Alaska Satellite Facility 907.474.7864 <(907)%20474-7864> mjrohl@alaska.edu
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
participants (4)
-
Brian : -
Michael Rohl -
Mike Stupalov -
Tom Laermans