But thus far it appears not to be happening to anyone else.
Adam.
observium(a)velder.li wrote:
>It appears on different hardware/software.. For now i reverted to
>backup from 19.02.2013 (daily incremental). We will see...
>
>
>
>Am 23.02.2013 01:22, schrieb Adam Armstrong:
>> I can't replicate it and I can't see why it's happening, unless your
>> agent
>> is randomly becoming unreachable.
>>
>> Also, no one else is reporting the problem.
>>
>> adam.
>>
>>
>> On Sat, 23 Feb 2013 02:09:01 +0100, observium(a)velder.li wrote:
>>> Unfourtinately, i don't have additional infos in the logfile :( Do
>>> you
>>> need more infos from somewhere else?
>>>
>>> Regards,
>>> Patrick
>>>
>>>
>>> Am 23.02.2013 01:15, schrieb Adam Armstrong:
>>>> Very helpful debugging. Thanks.
>>>>
>>>> On Sat, 23 Feb 2013 01:59:35 +0100, observium(a)velder.li wrote:
>>>>> Still """rebooting""". Few days ago, i hadn't that problem :(
>>>>> Think
>>>>> it's because svn update..
>>>>>
>>>>>
>>>>>
>>>>> Am 22.02.2013 21:05, schrieb Adam Armstrong:
>>>>>> svn up. I've added logging for unix agent connection failures to
>>>>>> the
>>>>>> observium.log
>>>>>>
>>>>>> root@alpha:/home/observium/demo# grep agent observium.log
>>>>>> Connection to UNIX agent on alpha.memetic.org:6556 failed. ERROR:
>>>>>> 111
>>>>>> Connection refused
>>>>>> Connection to UNIX agent on alpha.memetic.org:6556 failed. ERROR:
>>>>>> 111
>>>>>> Connection refused
>>>>>> Connection to UNIX agent on alpha.memetic.org:6556 failed. ERROR:
>>>>>> 111
>>>>>> Connection refused
>>>>>> root@alpha:/home/observium/demo#
>>>>>>
>>>>>> Could do with some timestamps too, maybe. :)
>>>>>>
>>>>>> adam.
>>>>>>
>>>>>>
>>>>>> On Fri, 22 Feb 2013 21:53:41 +0100, observium(a)velder.li wrote:
>>>>>>> See uptime on Observium Host:
>>>>>>> root@admin:~# uptime
>>>>>>> 21:51:48 up 60 days, 21:27, 1 user, load average: 0.00,
>>>>>>> 0.00,
>>>>>>> 0.00
>>>>>>>
>>>>>>>
>>>>>>> Uptime of "accesspoint"
>>>>>>> root@accesspoint:~# uptime
>>>>>>> 21:52:17 up 12 days, 42 min, load average: 0.03, 0.03, 0.04
>>>>>>>
>>>>>>>
>>>>>>> Uptime uf "ns3"
>>>>>>> root@ns3:~# uptime
>>>>>>> 21:52:37 up 64 days, 7:39, 1 user, load average: 0.00,
>>>>>>> 0.00,
>>>>>>> 0.00
>>>>>>>
>>>>>>>
>>>>>>> "accesspoint" is about 5km from the observium host, site to site
>>>>>>> vpn..
>>>>>>> ns3 directly over internet, 6400km.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Am 22.02.2013 20:58, schrieb Adam Armstrong:
>>>>>>>> that uptime comes from /proc/uptime, i think it's quite
>>>>>>>> reliable:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>> http://demo.observium.org/graphs/type=device_uptime/device=6/to=1361566071/…
>>>>>>>>
>>>>>>>> Is it possible that your agent is failing to connect? Is the
>>>>>>>> host
>>>>>>>> in
>>>>>>>> question far away from the observium server?
>>>>>>>>
>>>>>>>> adam.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, 22 Feb 2013 21:34:18 +0100, observium(a)velder.li wrote:
>>>>>>>>> Hi Adam
>>>>>>>>>
>>>>>>>>> www-data@admin:~/observium.mydomain.ch$ ./poller.php -h 6 -m
>>>>>>>>> unix-agent,system -d| grep uptime
>>>>>>>>> RRD[update
>>>>>>>>>
>>>>>>>>> /var/www/observium.mydomain.ch/rrd/admin.mydomain.ch/uptime.rrd
>>>>>>>>> N:5183936] Uptime: 59 days, 23h 58m 56s
>>>>>>>>> [uptime] => 5183936
>>>>>>>>> SQL[UPDATE `devices` set `uptime` ='5183936',`last_polled`
>>>>>>>>> =NOW(),`last_polled_timetaken` ='0.053' WHERE `device_id` =
>>>>>>>>> '6']
>>>>>>>>> UPDATED!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Am 22.02.2013 20:37, schrieb Adam Armstrong:
>>>>>>>>>> For example:
>>>>>>>>>>
>>>>>>>>>> root@alpha:/home/observium/demo# ./poller.php -h 6 -m
>>>>>>>>>> unix-agent,system -d
>>>>>>>>>> | grep uptime
>>>>>>>>>> (root,7688,836,0.0) grep --color=auto uptime
>>>>>>>>>> [uptime] => 20405260.06 64091168.44
>>>>>>>>>> RRD[update
>>>>>>>>>> /mnt/ramdisk/observium_demo/alpha.memetic.org/uptime.rrd
>>>>>>>>>> N:20405260] Uptime: 236 days, 4h 7m 40s
>>>>>>>>>> [uptime] => 20405260
>>>>>>>>>> SQL[UPDATE `devices` set `uptime` ='20405260',`last_polled`
>>>>>>>>>> =NOW(),`last_polled_timetaken` ='0.483' WHERE `device_id` =
>>>>>>>>>> '6']
>>>>>>>>>> UPDATED!
>>>>>>>>>> root@alpha:/home/observium/demo#
>>>>>>>>>>
>>>>>>>>>> adam.
>>>>>>>>>>
>>>>>>>>>> On Fri, 22 Feb 2013 21:23:54 +0100, observium(a)velder.li
>>>>>>>>>> wrote:
>>>>>>>>>>> No, it's on multiple devices, and snmpd is running since
>>>>>>>>>>> last
>>>>>>>>>>> reboot.
>>>>>>>>>>> Poller has different values than Graph, "uptime" on system,
>>>>>>>>>>> devices
>>>>>>>>>>> page
>>>>>>>>>>
>>>>>>>>>>> ;)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Am 22.02.2013 21:20, schrieb Mark Chaney:
>>>>>>>>>>>> Its just probably stupid snmpd restarting or saying that
>>>>>>>>>>>> they
>>>>>>>>>>>> did.
>>>>>>>>>>>> Nothing you can really do about that.
>>>>>>>>>>>>
>>>>>>>>>>>> On 2013-02-22 14:09, observium(a)velder.li wrote:
>>>>>>>>>>>>> Hi there
>>>>>>>>>>>>>
>>>>>>>>>>>>> just saw that observium says that many devices were
>>>>>>>>>>>>> rebooted
>>>>>>>>>>>>> today.
>>>>>>>>>>>>> But that's not true. See Screenshot. Is that a bug?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards
>>>>>>>>>>>>> Patrick
>>>>>>>>>>>>>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> observium mailing list
>>>>>>>>>>>>> observium(a)observium.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> observium mailing list
>>>>>>>>>>>> observium(a)observium.org
>>>>>>>>>>>>
>>>>>>>>>>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> observium mailing list
>>>>>>>>>>> observium(a)observium.org
>>>>>>>>>>>
>>>>>>>>>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>>>>>>>>> _______________________________________________
>>>>>>>>>> observium mailing list
>>>>>>>>>> observium(a)observium.org
>>>>>>>>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>>>>>>>> _______________________________________________
>>>>>>>>> observium mailing list
>>>>>>>>> observium(a)observium.org
>>>>>>>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>>>>>>> _______________________________________________
>>>>>>>> observium mailing list
>>>>>>>> observium(a)observium.org
>>>>>>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>>>>>> _______________________________________________
>>>>>>> observium mailing list
>>>>>>> observium(a)observium.org
>>>>>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>>>>> _______________________________________________
>>>>>> observium mailing list
>>>>>> observium(a)observium.org
>>>>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>>> _______________________________________________
>>>> observium mailing list
>>>> observium(a)observium.org
>>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>> _______________________________________________
>>> observium mailing list
>>> observium(a)observium.org
>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>> _______________________________________________
>> observium mailing list
>> observium(a)observium.org
>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>_______________________________________________
>observium mailing list
>observium(a)observium.org
>http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hello,
I have a few IP which I am able to get the SNMP and it showing alive but
observium not able to resolve. Below are the output:
[image: Inline image 2]
[image: Inline image 3]
Anything else I should check? Please advice. Thanks.
Regards,
Afif
Hi all,
It is possible to give a user access to a port on for example a switch. But
you can't give them specific access to a sensor. With the ipoman for
example i would like to give a user access to a specific sensor, so they
can monitor their powerport and their ampere consumption.
Would it be possible to implement this in the authentication protocol?
--
Alexander Lantink
ColoCenter bv
http://www.colocenter.nl
info(a)colocenter.nl
Can someone help me understand the algorithm/conditions that will cause
a device to be flagged up/down in Observium?
Reason I ask is I'm seeing instances where devices will get flagged as
'down' however when I login to the Observium host and manually test via
fping/snmpwalk, I get valid responses back. The devices come back a few
minutes later.
I don't see anything in observium.log aside from poller completion
results, so I could use some more info/ideas to help debug why these
devices keep going offline intermittently.
Cheers,
-Chris
Hiya,
I'd like to make a feature request. It's a slight modification really.
In the User Management -> Edit User section you can grant a user access to a
device by selecting a device from a drop down box.
Would it be possible to change this from a single select to a multi-select
box please?
We may have to add over a hundred devices to several users. A multi-select
would reduce this work from mind-numbing to merely tedious.
Thanks,
Mike
--
Mike Richardson
Networks (network(a)manchester.ac.uk)
IT Services, University of Manchester
*Plain text only please - attachments stripped on arrival*
Hi everyone,
just would like to know, if there is already a "just undocumented" RANCID
integration for Observium?
I found a list point in the docu wiki, so I am just curious about.
You guys do a great job, btw!
Best regards,
Florian
Hi there,
I was wondering if anyone's got an idea as to why graphs would suddenly stop working? (see attachment)
I hadn't updated anything or changed anything, the rrd's all have data in.
It's running off Centos 6.2
Any ideas on how to troubleshoot?
[cid:18152FC1-6ED1-47C0-8A4D-DC5CBEF4B7BF@mill-ny.com]
