NetXMS Support Forum

Hi!

They work on some controllers (mostly ATA and SATA). If they are working (you got response from agent), then SMART status could be following:
0 - OK
1 - Bad
2 - Unknown

Best regards,
Victor

Hi!

LogFile = {syslog} in nxagentd.conf and netxmsd.conf does not relate in any way to built-in syslog server enabled with EnableSyslogDaemon parameter. Setting log file to {syslog} only means that serevr or agent will use system logging facility for logging (syslog call in UNIX). It is up to you (or server admin) to configure syslog on that particular server for remote logging to NetXMS server's syslog server. Here is an example of how to configure rsyslogd for sending messages to remote server: http://www.rsyslog.com/sending-messages-to-a-remote-syslog-server/. You should check what syslog server is used on your servers.

In short, message flow for remote agent is like following:

nxagentd -> syslogd ---------------> netxmsd syslog server
-----------------------                        -------------------------
  remote host               network            netxms server


If you want local netxmsd log to be catch by netxms syslog:

netxmsd -> syslogd ---------------> netxmsd syslog server
                                 loopback

Best regards,
Victor

Hi!

To disable SNMP for node go to node properties, then "Polling" page, and check "Disable SNMP".

Best regards,
Victor

Hi!

It's a bug in a server. I just fix it, 1.2.12 patch release will include this fix.

Best regards,
Victor

Quote from: Marco Incalcaterra on January 30, 2014, 01:42:27 PM
Is there a particular size to be observed?

No, login form will resize as needed.

Best regards,
Victor

Are all stack traces identical?

Best regards,
Victor

Yes, it's what I was interested in. Thank you!

Best regards,
Victor

Yes, exactly. I can possibly suggest some if you tell me how you want to use those events.

Best regards,
Victor

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