TechZen - Zenoss User Community Forums

Setting zPingMonitor to truw should disable pinging, but the error you're seeing indicates that you have a template bound or a datasource set for the device that is trying to run a command via SSH against the device, but none of the information Zenoss ...

I've set zPingMonitorIgnore=true for all my devices yet I keep getting this message: "zCommandUsername is not set so SSH-based commands will not run". I thought zPingMonitor ignore should disable pinging altogether. Any idea what I'm missing? ------------------------------ ...

Hello, It seems monitoring templates are only running when a device is first created and when previous "Down events" have been closed. The way that I've confirmed this is by leaving Zenoss as is for a full day: not a single monitoring template runs. ...

Hi Team, We have windows servers configured. Due to some reason, we have not receiving alerts since Monday 10th Dec.  What could be the reason? What i am supposed to check in regards with this? Awaiting response. ------------------------------ Nilesh ...

Further to that, if the command is run from within Zenoss, the username and password is defined in the zCommandUsername and zCommandPassword properties, which make for a generic command ID and not who initiated the command within the application. I suspect ...

You can use ${dev/zCommandUsername} to get the userid Zenoss is using to ssh to the device. I think that's what you are looking for. If you are just executing the commands on the Zenoss server, everything is run as the zenoss user.  ------------------------------ ...

This has been something of a pain for myself, as well - I have a task on my end to try and figure out what is causing us to run long, and I suspect it might have something to do with when we upgrade our ZenPacks and update our remote collectors. I have ...

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 ...