NetXMS Support Forum

Hi,

most likely something in event processing policy cause slow processing. Can you enable debug level 6 for some time and trace processing of few events? Also, you can try to disable all rules in event processing policy and see if it helps. If it will, try to re-enable them one by one to catch what rule causing delay.

Best regards,
Victor

I've fixed this bug. Fix will be included in 2.0-RC2.

Best regards,
Victor

Hi,

I've made some checks and was unable to detect memory leak when agent cannot connect to database. What Oracle client you are using?

Best regards,
Victor

Hi,

what NetXMS version you are using?

Best regards,
Victor

Hi,

operation and value are ignored for data collection error thresholds.

Best regards,
Victor

Hi,

what version of agent you are running and on what OS? Could you run agent for some time with debug level 6 and send me log file?

Best regards,
Victor

Hi,

in most cases it is hold by mmc.exe because it contains message catalog that is used by event log viewer. Try to ensure that all mmc instances (or any other process that possibly reading event log) are stopped.

Best regards,
Victor

Hi,

try to create database and user for NetXMS using MySQL management tools and in server installer select "use existing database" and specify user and database you created.

Best regards,
Victor

Hi,

for monitoring network service object server just reads ServiceCheck.* parameters from appropriate node, so basically there are no difference in monitoring method, only in result presentation. For SMTP check you should enter valid email address in request field, response is ignored. Checker will try to send email to that address.

Best regards,
Victor

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