Hi Marco,
Many things to learn and understand in zabbix ...OMG..
Finally , I am able to see my router getting auto-registered as part of
zabbix server and I am also able to see the network interfaces traffic
(incoming and outgoing ) graphs.
when I connect a client to my router I don't see any tx/rx , wireless
clients connection in nutshell I am not able to see the wireless properties
information of router in zabbix server.
Is there any special wireless package which has to be added as part of
zabbix agent or zabbix server to get this wireless properties stats ?
Here is the screenshot of the network interface which is detected by zabbix
server.
regards
On Wednesday, 29 March 2017 23:52:20 UTC+5:30, SKapoor wrote:
>
> Yes , they are in the same LAN..
>
> Auto discovery rule is added under configuration->action tab...I can see
> router host name getting added as part of auto registration but still in
> the dashboard zabix server having problem and the zabix agent which gets
> added as part of auto registration it's graph , other configuration are not
> getting updated..
> I m still working on it ..let me take a day and come back to you again
> with success/ failure :)
>
> Regards
>
> On Wed, 29 Mar 2017 at 6:57 PM, marco.cappellacci <
> marco.cappella...@gmail.com> wrote:
>
>> Is the zabbix server and device in the same lan network?
>> Do you add autodiscovery rule in zabbix admin interface?
>>
>>
>> Il giorno lunedì 27 marzo 2017 17:27:28 UTC+2, SKapoor ha scritto:
>>>
>>> thanks Marco.. What I am seeing is in my router box is:
>>>
>>> root@EE-0C-BD-2E-C6-2A:/# cat /tmp/zabbix_agentd.log
>>> 1211:20170327:143822.517 Starting Zabbix Agent [zabbix]. Zabbix 2.4.6
>>> (revision 54796).
>>> 1211:20170327:143822.517 using configuration file:
>>> /etc/zabbix_agentd.conf
>>> 1211:20170327:143822.518 agent #0 started [main process]
>>> 1218:20170327:143822.520 agent #1 started [collector]
>>> 1219:20170327:143822.521 agent #2 started [listener #1]
>>> 1220:20170327:143822.522 agent #3 started [active checks #1]
>>> 1220:20170327:143822.523 active check configuration update from [
>>> 192.168.1.102:10051] started to fail (cannot connect to
>>> [[192.168.1.102]:10051]: [1)
>>> 1220:20170327:143934.745 active check configuration update from [
>>> 192.168.1.102:10051] is working again
>>> 1220:20170327:145138.331 active check configuration update from [
>>> 192.168.1.102:10051] started to fail (cannot connect to
>>> [[192.168.1.102]:10051]: [4)
>>> 1220:20170327:151340.688 active check configuration update from [
>>> 192.168.1.102:10051] is working again
>>>
>>> but zabbix server says :
>>> zabbix agent on zabbix is unreachable for 5mins.
>>> Attached is the screenshot for the same.
>>>
>>> what is wrong here still this is not integrated in openwisp2 ?
>>>
>>> Surely, will also use UCI commands once we do will pass it on.
>>>
>>> regards,
>>>
>>>
>>> On Monday, 27 March 2017 15:21:57 UTC+5:30, Federico Capoano wrote:
>>>>
>>>> The deamon is needed because the openwisp-config deamon calls a script
>>>> which reloads deamons which have their configuration changed.
>>>>
>>>> The script in question is in /usr/sbin/openwisp-reload-config
>>>> <https://github.com/openwisp/openwisp-config/blob/master/openwisp-config/files/sbin/openwisp-reload-config>
>>>>
>>>> which in turn is a slight variation of the default /bin/reload_config
>>>> script present in OpenWRT
>>>> <https://github.com/openwrt/openwrt/blob/master/package/system/procd/files/reload_config>
>>>> .
>>>>
>>>> This workaround could not be necessary if the maintainers of the zabbix
>>>> openwrt package could improve the integration with openwrt (use UCI for
>>>> configuration directives and register the agent to procd).
>>>>
>>>> Federico
>>>>
>>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "OpenWISP" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/openwisp/DodaHOTJFCE/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> openwisp+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to openwisp+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
