I'm somewhat surprised that there isn't a one-to-one correspondence between the various Zenoss Plugins utilities and the Collector Plugins. It's not at all obvious which Collector Plugin uses which Zenoss Plugin, nor that any thought has been given to controlling this.
So, when there is a problem with a Zenoss Plugin, I just get a steady stream of error events. In this case, I'm getting errors from "disk", claiming that the disks don't exist. I suspect this has something to do with the fact that machine I'm running it on is actually virtualized, I'm willing to accept that "disk" simply doesn't work with it (the information isn't that critical) -- but I can't see any way to shut off the warnings. Is there some way to isolate this problem and mark it as ignored? One thing I do find strange, though, is that 'df' works fine on the server and contains the filesystem info that is missing on this device, so why doesn't the collector "zenoss.cmd.df" work? Surely the name means it collects info using the 'df' command? -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=22423#22423 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
