Items failing out to "not supported"

[ebonweaver]

Once again slammed hard into this bug that's never been addressed and hoping someone has found a work around for it.
Red Hat systems, been working for months, all of the sudden half the systems I'm monitoring claim that net.if.in[eth0,bytes] and net.if.out[eth0,bytes] are Not Supported. Obviously that's false, the question is why did they suddenly fail, and how do you get them to register as valid again (and why don't the developers fix an issue that randomly cripples the entire point of the software). I assume there must be a way to clear whatever flag has been tripped, but I have no idea where this would be, and if it's client or server side.

Thanks for any help.

[tchjts1]

It is easier if you mention what version of Zabbix you are using.
Backtracking through some of your posts, it appears you have recently upgraded to 2.0.9.

I use 2.0.9 and I have zero issues with pulling data on on my RHEL hosts.
I DO use the stock Linux OS template which has LLD rules for interface discovery, so it discovers all interfaces automatically and creates the graphs automatically.

Does your Linux OS template look like this?

[ebonweaver]

As mentioned, I wasn't having any trouble until today, it had been working fine for months. Previously I had only seen issues on Windows server dropping things randomly as not supported. I was trying out graph styles on the one host today playing with the options for the memory graph. At that time, Zabbix suddenly decided that the keys mentioned were not supported on RHEL 6. The RHEL 5 boxes are still working. Nothing was changed concerning these items, they just died.

No, I do not have discovery items on my hosts, or in the template. I copied items from the template rather than using the whole template as I didn't want to monitor hundreds of items, just 6, at my own intervals and retention settings.

Yes, the server and clients are both 2.0.9

[ebonweaver]

Still looking for anyone who has a fix for this. The dev team refuses to help since this is perceived as an issue with SELinux configuration in RHEL6 and not a Zabbix bug. I get that idea, despite it seeming pretty obvious that the installer should grant permissions it needs to work, but so far I've not found anyone who has a fix or is willing to share the knowledge. Has anyone resolved this?