TechZen - Zenoss User Community Forums

Hi, We're certainly affected by this. Although pleasingly have not seen it for a while but then we have currently set the blocking timeout to 0, i.e. do not use blocking timeout! as we can't be in a situation where as there may not be access to zenoss ...

Removing or editing this file is definitely the way to get the datasources collecting again - but it doesn't get to the root cause of the problem which is that devices are not responding to zenpython fast enough and are then "blocking".  The real problem ...

I'm performing some custom logic where my user commands are using a shell script on disk. So a typical command would look like /bin/sh /var/zenoss/command.sh actionX ${device/id} In my command.sh script for example, actionX is $1, ${device/id} ...

Is this a command being executed by zencommand?  If not, please explain further. And where do you want to gather the parameters like the device and user?  In a template?  in the event console? Cheers, Jane ------------------------------ Jane Curry ...

Don't know the answer to that, Jad.  But traditionally, Zenoss Core pre version 5, did not have audit logging - only in the paid version. Cheers, Jane ------------------------------ Jane Curry Skills 1st United Kingdom jane.curry@skills-1st.co.uk ...

Looks like your zeneventd daemon is not running or running very slowly. Run "zenoss status" to check all daemons. If zeneventd isn't running, restart it and then watch your rabbit queues. If zeneventd IS running, have you changed any transforms recently?  ...

Hello, Is there a way to get the username of the user who executed a command? I mean something like ${user/id} since we can already get the device it is being executed on with  ${device/id} Thank you ------------------------------ Jad ------- ...

As per the latest documentation , I should be able to find application audit logs at  /var/log/serviced/application-audit.log on my host. However, also looking here , it says: application-audit.log records application audit messages, and is present ...

Hi, In terms of unblocking the blocked datasources, this involves removing the name of the blocked datasource from either /var/zenoss/zenpython.blocked on Zenoss 5, or /opt/zenoss/var/zenpython.blocked on Zenoss 4 and then restarting zenpython daemon. ...

Sigh. OK, I'll try to upgrade this weekend, but I'm thinking it's a bigger job that just installing the new code... We'll see. ------------------------------ Paul Giordano Senior Systems Engineer Zethcon Corporation ------------------------------

Paul, I know you mentioned in another thread you were running version 6.1.2; if you can, I'd highly recommend moving to 6.2.1, as version 6.1.x had some problems with memory leaks, exceptions being thrown, zombie threads running at 100% utilization and ...

Answered my own question, go to Advanced -> Monitoring Templates, expand ESXiHost, select /Devices/VMWare/ESXiHost, double click on the datasource, disable and enable it again. This doesn't fix the original problem, but it resets the disabled datasources. ...