NetXMS Support Forum

Hi,

I really recommend you to upgrade to 2.0. RC1 is quite stable, and we will roll out RC2 soon which should be even better. Upgrade procedure is the same as from 1.2.16 to 1.2.17, and you can upgrade directly to 2.0-RC1 or higher.

Best regards,
Victor

Hi,

you mean you getting two nodes - one with old IP and one with new IP? Server is supposed to detect IP change by MAC address, but if node does not support SNMP server can rely only on switch forwarding databases. Does server has access to switches where all those nodes are connected? Are MAC addresses correctly detected for non-SNMP nodes?

Best regards,
Victor

Hi,

do you have any messages in server log started with "SQL query failed"?

Best regards,
Victor

Hi,

from the trace I see that server is blocked on reading one of Service.Check(...) parameters (and I see there are lot of them) which probably takes some time to complete. As DCI is locked when it is being polled, when item poller thread attempts to access this DCI it locks, and so watchdog warning is triggered.
Actually new feature called "agent side DCI cache" introduced in 2.0-RC1 can help - you can turn on agent cache for those DCIs (or all DCIs). This will switch then from polling mode to push mode, thus eliminating long locks on server side.

Best regards,
Victor

Only direct parents are examined. Recursive script could looks like this:


rcpt = GetRecipients($node);
return (rcpt != null) ? rcpt : "default@email";  // fallback email if nothing was set in containers

sub GetRecipients(obj)
{
    rcpt = GetCustomAttribute(obj, "recipients");
    if (rcpt != null)
return rcpt;
    foreach(p : GetObjectParents(obj))
    {
        rcpt = GetRecipients(p);
  if (rcpt != null)
return rcpt;
    }
    return null;
}


and if you want that any closest parent had higher priority:


rcpt = GetRecipients($node);
return (rcpt != null) ? rcpt : "default@email";  // fallback email if nothing was set in containers

sub GetRecipients(obj)
{
    foreach(p : GetObjectParents(obj))
    {
        rcpt = GetCustomAttribute(p, "recipients");
if (rcpt != null)
return rcpt;
    }
    foreach(p : GetObjectParents(obj))
    {
        rcpt = GetRecipients(p);
if (rcpt != null)
return rcpt;
    }
    return null;
}


Best regards,
Victor

Hi,

it's possible, but way is long

To be able to use value in charts, you have to create DCI. You receive events from log parser, and have to convert them into data in DCI. Easiest way is to create push DCI and script action, which will use PushDCIData function to push new value extracted from event. Then you can add this DCI to chart as usual.

Best regards,
Victor

Hi,

how script to extract recipients looks like?

Best regards,
Victor

Hi,

you can add threshold on data collection error - it should fire if server was unable to read data for any reason.

Best regards,
Victor

Hi,

when you encounter hang next time, could you please capture process state using following instruction?

1. Check netxmsd PID
2. Run

gdb netxmsd

(use full path if necessary). It will show (gdb) prompt.

3. Within gdb run

attach <netxmsd_pid>

it should show (gdb) prompt again.

4.  Run

thread apply all bt

and send me the output (could be quite long, so make sure you have adequate buffer length in terminal).

5. Run

detach

to detach from netxmsd and let it run.

Best regards,
Victor

PM sent.

Best regards,
Victor

Hi,

you can create VPN connector objects to match your VPN topology - then NetXMS server will know that remote network is behind VPN gateway and will correlate gateway down event properly.

Best regards,
Victor

Hi,

I suppose you are talking about server side syslog parser. Seems like a bug, I'll check.
But anyway, I don't see how invert will help you - I suppose you'll need two rules anyway: first rule will match "xyz" and stop processing, and second rule will match "abc" and do what is needed.

Best regards,
Victor

Hi,

there is installation guide, outdated, but still mostly valid: https://wiki.netxms.org/wiki/Server_Installation_Guide. Check upgrade section. If you monitor only SNMP devices, then you don't need agent packages. You'll have to download appropriate server package and upgrade server. Then you'll need new managemet console (if you are using desktop version) and/or new web UI package if you are using it.

Best regards,
Victor

Yes, it should pick correct location then. Also, you can set config file location in registry by setting: HKLM\Software\NetXMS\Agent\ConfigFile (and optionally HKLM\Software\NetXMS\Agent\ConfigIncludeDir).

Best regards,
Victor

По подтверждению - как workaround можно в текст добавить макрос %n, например:

Are you sure to execute this on node %n?