NetXMS Forum

Even-though the packages work on Wheezy when porting an older version of libssl from squeeze, I would appreciate if we could get native wheezy packages. There is also a problem with dependencies, as postgresql-8.4 is not standard in newer debian releases. So each time I install netxms, I manually have to modify the packages and change the dependency from postgresql-8.4 to postgresql-9.1 Squeeze is nearing EOL, so perhaps its time to move on?

Hi Victor, and thanks for your answer. So one or more of these are not enabled in terms of showing a notification when something goes wrong? I have used netxms for a while and it performs as expected as long as the poll values don't go red and show error. I only discover that something's wrong when I actually view the values manually. Raymond @victor said in netxms polling fails, no error/notification: Hi! System will generate events in case anything goes wrong with the node - you can handle these events and create alarms, send notifications, etc. Most important events are following: SYS_NODE_DOWN - entire node is down (NetXMS server cannot communicate using any allowed means) SYS_NODE_UNREACHABLE - NetXMS server cannot communicate with the node because of intermediate router failure SYS_NODE_UNMANAGED - someone put node into unmanaged state SYS_NODE_UNKNOWN - status of the node is unknown SYS_IF_DOWN - network interface is down SYS_IF_UNKNOWN - status if network interface is unknown (usually because of disconnected agent) SYS_IF_DISABLED - network interface was disabled SYS_SERVICE_DOWN - network service is down SYS_SERVICE_UNKNOWN - network service state cannot be determined (usually because of agent failure) SYS_AGENT_UNREACHABLE - NetXMS agent is unreachable SYS_SNMP_UNREACHABLE - SNMP agent is unreachable SYS_DCI_UNSUPPORTED - DCI goes to "unsupported" state SYS_SCRIPT_ERROR - NXSL script execution error SYS_SMTP_FAILURE - server was unable to sent e-mail notification SYS_SMS_FAILURE - server was unable to sent SMS notification Best regards, Victor

Perfect! Really an exciting feature as this will make netxms more appealing for enterprise environments. If you need someone to do testing, just give me a wink.

Thanks Victor. Figured it out myself a short time after my post. I created an action on the console side, hooked it up to a trigger which ran action "varnish.restart". The nxconfig file contained the following: Action = varnish.restart:/etc/init.d/varnish restart Worked like a charm. Just posting my findings as a reference to others that stumble upon this post. marking this post as solved.

You need to setup environment for cross-compiling, quick search on google resulted in this link: http://www.dd-wrt.com/dd-wrtv2/downloads/others/sourcecode/toolchains/current-toolchains.tar.bz2 Check this link for more info: http://wiki.openwrt.org/doc/devel/crosscompile

Hi! It's bug in a package. As a fix, you should manually run update-rc.d nxagentd defaults 99 01 I'll fix this in next version. Best regards, Victor