[ZBX-6351] Active Agent Auto Registration via Zabbix Proxy Created: 2013 Mar 05 Updated: 2017 May 30 Resolved: 2013 Mar 06 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G), Proxy (P), Server (S) |
Affects Version/s: | 2.0.3 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Minor |
Reporter: | Walter Spencer | Assignee: | Unassigned |
Resolution: | Won't fix | Votes: | 0 |
Labels: | autoregistration | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Linux RHEL 6 |
Attachments: |
![]() ![]() ![]() ![]() |
Description |
When a host Auto Registers through a zabbix proxy, I find that sometimes the ip address of the host gets populated and sometimes it populates with 0.0.0.0 I added one today and it populated 0.0.0.0, previously I had about 50 hosts auto register and about 10-15 % were 0.0.0.0 I haven't confirmed it working without proxy, however I assume it would be a issue that more folks would run into it didn't have something to do with proxy. I would also be happy if the dns populated with the hostname. I have mostly active items, but there are passive items as well configured in the template that gets assigned. |
Comments |
Comment by richlv [ 2013 Mar 06 ] |
are all the agents of version 2.0.3 ? |
Comment by Oleksii Zagorskyi [ 2013 Mar 06 ] |
Please start that agent (which has been added with 0.0.0.0) with DebugLevel=4. Also attach it's config zabbix_agentd.conf On one screenshot I see TCP port 13684 used for agents, is it so ? |
Comment by Oleksii Zagorskyi [ 2013 Mar 06 ] |
In the attached log we can see: 15511:20130306:093256.606 refresh_active_checks('10.251.4.233',13685) 15511:20130306:093256.606 Sending [{ "request":"active checks", "host":"xxx.com", "ip":"10.251.5.9", "port":13684}] so zabbix agent itself is ok, thanks. |
Comment by Walter Spencer [ 2013 Mar 06 ] |
All Agents 2.0.3, because I couldn't be 100% positive during the initial run, so I just took one host and deleted it and added it back with 2.0.3 agent and 1.9.4 (my previous version). The IP was added correctly both times. I have attached a log of my 2.0.3 agent starting during normal processing. I then removed the host again, waited for the host removal to sync with proxy. Then started 2.0.3 agent. That log is attached also. Again it seemed to work fine. I am using port 13684. Big orgization and the zabbix port was in use. Here is the config: Server=10.251.4.233,10.251.4.62 UserParameter=ms.discovery[*],/ms/dist/ipm/PROJ/hpe-zabbix-runtime/$ZBX_ENV/etc/getData.sh -d $1 $2 $3 $4 $5 UserParameter=SetProxy[*],/ms/dist/ipm/PROJ/hpe-zabbix-runtime/prod/etc/setServer.sh $1 $2 |
Comment by Walter Spencer [ 2013 Mar 06 ] |
Of course it keeps working....Here is the debug level from the proxy of another host. The IP was added correctly at the server level. And the dns populates correctly. I was mistaken by saying this was left out. All of my successful hosts have it populated. I will keep trying to get the proxy snippet of a case in which it fails. 7798:20130306:102655.201 In send_data_to_server() [{ ], |
Comment by Walter Spencer [ 2013 Mar 06 ] |
Ok. Not a bug. A self inflicted wound. Upon startup I make sure I assign ListenIP so that I don't listen to all available IPs as there is time sensitive traffic on the other IPs. The problem as soon as the box is booted the agent starts and the interface configuration specically to NIC bonding may not be setup and my check doesn't account for this and finds 0.0.0.0 and puts that in the conf file. Which make sense as to why the host I added yesterday failed because it doesn't follow this setup I was looking for. And due to the fact that by the time I investigate the box was rebooted and setup correctly and the conf file is correct I assumed it was getting dropped. However, the real issue is that I missed that initial registration window. I do appreciate you time in helping me diagnose. My Apologies. Here is the bad conf file: Server=10.251.4.233,10.251.4.62 UserParameter=ms.discovery[*],/ms/dist/ipm/PROJ/hpe-zabbix-runtime/$ZBX_ENV/etc/getData.sh -d $1 $2 $3 $4 $5 UserParameter=SetProxy[*],/ms/dist/ipm/PROJ/hpe-zabbix-runtime/prod/etc/setServer.sh $1 $2 This is the zabbix proxy snippet associated with the bad conf file. 7806:20130306:103723.165 Trapper got [ { "request":"active checks", "host":"ivelocity137.vhub.halsey.ms.com", "ip":"0.0.0.0", "port":13684}] len 104 ... 7798:20130306:103723.177 In send_data_to_server() [{ ], |
Comment by Walter Spencer [ 2013 Mar 06 ] |
Operator Error, Not a bug. |