This has been an issue for years. I've seen it in every version since 1.8 and it persists in 2.4. Random items, usually network related, simply decide they are not supported. They ARE supported, they are basic items that work on every other system of the same OS version with the same agent version. Version of agent doesn't fix this. Deleting and re-adding the item does not fix this. It's the same item as it's in a template that's working on the other systems, again of the same OS version. It seems the problem is something just breaks in the database where it's convinced a certain item for a certain host is unsupported, and you can never again get it to work unless you delete the entire host and start over. I have submitted bugs about this and they have been ignored.
Has anyone found a good way to deal with this perpetual issue? Or are we stuck with scrapping and starting over when a host breaks?
Has anyone found a good way to deal with this perpetual issue? Or are we stuck with scrapping and starting over when a host breaks?