NetXMS Support Forum

Can you please check that latest SQLite amalgamation (http://www.sqlite.org/2013/sqlite-amalgamation-3080200.zip) compiles on FreeBSD 9.2? If yes, I'll just replace current version with latest one.

Best regards,
Victor

Try to get a stack backtrace from core (bt command in gdb).

Best regards,
Victor

You cannot suppress second event from log parser but you can handle duplicate event differently. For example, you can set some custom attribute to the time stamp of received event, and ignore all next events if they are within certain time frame. Actual solution depends on how you are using those events.

Best regards,
Victor

Hi!

Usually you setup one or more DCIs on the node to control service health, and the use GetDCIValue family functions to check values against thresholds.

Best regards,
Victor

Looks strange. I'll try your policy on my test system later today.

Best regards,
Victor

Hi!

1) On SYS_NODE_DOWN event you can set some custom attribute for the node to current time, executing script like this:


SetCustomAttribute($node, "DowntimeStart", time());


then, you can use macros which call script in notification on SYS_NODE_UP, like this: %[GetDowntimeText]

and script (GetDowntimeText in our example) in script library like this:


return SecondsToUptime(time() - GetCustomAttribute($node, "DowntimeStart"));


2) You can use PING subagent to do regular pings and set threshold for rtt > 75. Ping subagents described here: http://wiki.netxms.org/wiki/Subagent:Ping.

Best regards,
Victor

Actually, there is an etrror in the script: you should use || (logical or) instead of && (logical and).

Best regards,
Victor

Hi!

When login screen is displayed, web server checks URL http://127.0.0.1/netxms_login.dat . If this URL points to valid image file (PNG, JPEG, or GIF), then it will be displayed instead of standard logo. This is not very convenient, so I'll add possibility to configure custom logo in nxmc.properties file in next release.

Best regards,
Victor

Hi!

I see few possible solutions here.

1. Use dummy DCI, and in transformation script call AgentReadParameter to get LdapQuery from agent with required parameters.

2. If values of custom attributes not changing, you can embed them into DCI on template apply time using template macros. It could be something like


LdapQuery(%{script:LdapParameters})


and in script library you can create script named LdapParameters like this:


return GetCustomAttribute($node, "ip") . "," . GetCustomAttribute($node, "user") . "," . GetCustomAttribute($node, "GUID") . "," . GetCustomAttribute($node, "value");


Best regards,
Victor

Quote from: sperlm on January 24, 2014, 03:02:06 PM
p.s. could I get my old topic Dependency script based on infrastructure unlocked to post what I came up with to share with others ?

unlocked.

Best regards,
Victor

Quote from: sperlm on January 24, 2014, 12:29:02 PM
   if I understand it - just by configuring these options and having LogFile = {syslog} in netxmsd.conf (by default) should (after server restart) start up syslog in NetXMS console and start filling it with NetXMS log ?

No, just opposite - LogFile = {syslog} in netxmsd.conf is not related to built-in syslog server in any way. You have to enabled built-in syslog server using EnableSyslogDaemon and company as I described before. Note that these are server configuration variables stored in database (editable in console via Configuration -> Server configuration), not parameters in netxmsd.conf.

Best regards,
Victor

Your problem here is that i->peerNode is an object, not a string, so you should use something like i->peerNode->name.

Best regards,
Victor

Hi!

What version of NetXMS, on what platform and database? Also, can you share portion of server log file (running server with debug level 6)?

Best regards,
Victor

There was a bug in gauge widget. I've fixed it. Fix will be included in 1.2.12 release.

Best regards,
Victor

Not yet. I'll add this as feature request (https://www.radensolutions.com/chiliproject/issues/483).

I'll think about instance discovered DCIs on one graph. Currently it should be possible to fix them using nxshell, but probably it will not be easy.

Best regards,
Victor