[ZBX-1174] Server resets Agent Port randomly back to default Created: 2009 Nov 03  Updated: 2017 May 30  Resolved: 2009 Dec 17

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 1.9.0 (alpha)
Fix Version/s: 1.8, 1.9.0 (alpha)

Type: Incident report Priority: Major
Reporter: J. Fischer Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHEL 5.x, MySQL 5.x, ZABBIX 1.7.1

Issue Links:
Duplicate
is duplicated by ZBX-1549 Agents are not discovered on configur... Closed

 Description   

The ZABBIX server seems to reset the Agent Port value back to the default value of 10050 despite it was being explicitly set to another value (10500).

How to reproduce:

  • Configure ZABBIX agent on some remote host(s) to listen to port 10500
  • In ZABBIX GUI, use "Mass update" to set the the Agent Port for the reconfigured hosts to 10500
  • From now, the servers are reachable again (Server asks Zabbix Agent on Port 10500)
  • Wait some time (20-30 Minutes)
  • See that the agent port has been reset to the default value of 10050, thus makes the agent unusable

Additional notes:

  • Some (2 out of 60) hosts seem to be immune against this
  • Environment has been upgraded from 1.6.4 to 1.7.1

How to fix:

  • unknown -

 Comments   
Comment by richlv [ 2009 Nov 03 ]

is network discovery active ?

Comment by J. Fischer [ 2009 Nov 03 ]

Yes, we just noticed that this has to do with network discovery - in discovery, the agent port is configured to port 10500 and all hosts are already discovered.
The query executed by get_discovered_agent_port() returns an empty result set, because dservices has now row with type 9 and a dhostid associated with dserviceid.

Comment by Dmitry Borovikov [ 2009 Dec 04 ]

This issue is due to "Discovery" problem when adding host in actions.

Comment by Dmitry Borovikov [ 2009 Dec 07 ]

Now ports for already existing hosts discovered by any discovery rules will not be updated to the default value or to any other different value. For now we do not bother how many agent sit on one IP, that's why this change won't brake discovery logic. Ports for existing hosts must be updated manually.

Comment by J. Fischer [ 2009 Dec 08 ]

Great. Has this made it in the 1.8 release already, or should I wait until 1.8.1?

Comment by richlv [ 2009 Dec 08 ]

yes, this should be in 1.8

Comment by J. Fischer [ 2009 Dec 08 ]

We just upgraded our reference environment from 1.6.6 to 1.8 and thus, I can confirm this issue is fixed.
Thanks!

Comment by richlv [ 2009 Dec 11 ]

works as expected with the head of the dev branch

Comment by Dmitry Borovikov [ 2009 Dec 14 ]

Minor fixes.

Comment by richlv [ 2009 Dec 16 ]

according to ZBX-1549, not fixed in 1.8.
if will be fixed in 1.8.1, please close this report, thanks

Comment by Dmitry Borovikov [ 2009 Dec 17 ]

Minor error fixed.

Generated at Fri Mar 14 17:58:56 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.