[ZBX-9321] Hosts that were disabled become monitored again after server upgrade Created: 2015 Feb 18 Updated: 2017 May 30 Resolved: 2015 Feb 26 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 2.4.3 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Minor |
| Reporter: | scott mcg | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | dm, proxy, upgrade | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 6.5 |
||
| Description |
|
Hi Is there a known bug where hosts that are disabled and are configured to use a DM Node, after upgrading will transition to become enabled again ? We upgraded from 2.0.3 to 2.4.3 last night. It all went well apart from many hosts that were disabled/not-monitored all of a sudden being resurrected and made active. From the same hosts, on becoming active, some had the error "Field 'groupid' is not integer' because their group list was empty. The hosts in question were configured to use DM Nodes. I know in 2.4 this feature was removed and it's now only proxies. Thanks. |
| Comments |
| Comment by richlv [ 2015 Feb 18 ] |
|
just a guess - some time ago a frontend bug allowed hosts to stay without hostgroups, but such hosts were not visible at all. after an upgrade, those hosts became visible. could that be the case here ? |
| Comment by scott mcg [ 2015 Feb 18 ] |
|
hi.. yes that is very possible for the hosts the appeared after the upgrade with no groups associated. Do you know of any other bugs that would explain the hosts that were in a disabled state, becoming enabled after the upgrade. I am trying to confirm 100% but i believe the hosts in question were configured as monitored by a Distributed Monitor node. Maybe there is some broken logic that during the upgrade, when the DM code is removed.. hosts that were configured to use a DM node get confused somehow and transition back to enabled state. |
| Comment by scott mcg [ 2015 Feb 18 ] |
|
just to add some more info. The upgrade notes https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240 hint at the behaviour that we saw when upgrading. The bit about "Node-based distributed monitoring removed". What the upgrade notes don't mention is that nodes that were Node-based DM monitored and were disabled... will become enabled after the upgrade. It's this last bit that might be a bug in the upgrade process ? |
| Comment by scott mcg [ 2015 Feb 26 ] |
|
unable to reproduce so closing off |