NetXMS Support Forum

Hi,

logic behind node down/node up is following:

if status poll detects that all interfaces and agents are not responding, it marks node as unreachable. Then it checks network path - for nodes behind proxy it involves proxy checking. If server considers proxy node down, it marks current node as having network path problems and generates SYS_NODE_UNREACHABLE event, otherwise SYS_NODE_DOWN is generated. When contact with node restored, SYS_NODE_UP generated. To distinguish between SYS_NODE_UP generated from down nodes or nodes with network path problems, SYS_NODE_UP comes with parameter number 1 set to 0 if node recovered from "down" state or 1 if node recovered from "network path problem" state.

Is it possible that you had proxy node down?

Best regards,
Victor

You should set full path to log file in LogFile parameter in nxagentd.conf.

Best regards,
Victor

Hi,

what driver is selected for this Cisco switch (you can see it on object overview page)?

Best regards,
Victor

Hi,

I've fixed startup scripts, thank you!

Best regards,
Victor

Hi,

I suppose you mean NetXMS client (GUI application), not agent?

Best regards,
Victor

Hi!

Do you have zones and agent set as proxy for zone, or it is set as proxy for individual nodes?

Best regards,
Victor

Hi,

try to switch agent logging to file if it's not done already (by changing LogFile parameter in nxagentd.conf), set debug level to 6 (by adding DebugLevel = 6 to nxagentd.conf) and run agent for some time. After you got some agent unreachable errors, post your log file (or send it to [email protected]).

Best regards,
Victor

Hi,

in 2.0.1 you can configure numbering direction and rack height in rack object properties.

Best regards,
Victor

Пришлите config.log пожалуйста.

Hi,

load average 32 for a pool means that you have about 32 tasks running in parallel on this thread pool. You can check history for that parameter and set pool max size at a bit higher value then max for load average and min size to medium value for load average.

Best regards,
Victor

Hi,

such message is usual when log rotation occurs. To detect log rotation agent compares size returned by stat using file name, and size returned for currently open file descriptior. If first is smaller, it assumes that file was rotated, re-open it, and start reading from the beginning. How often you got this message and is this file actually rotated?

Best regards,
Victor

Hi,

actually currently the only possibility to display something in rack is to create node object for it. So you'll have to create nodes for each disk shelf and place them as needed. For controllers you'll need to set height 1 and rack position 1 and 2.

Best regards,
Victor

If you need to format date like this you can use strftime function:

return strftime("%d-%m-%Y %H:%M", $1);

This will convert UNIX time stamp from $1 into string of format DD-MM-YYYY HH:MM.

Alternatively, you can use string concatenation, like this:

t = gmtime($1);
return t->mday . "-" . t->mon . "-" . t->year;

Best regards,
Victor

Hi,

attached is patched server core (for 64 bit Windows).

Best regards,
Victor

Hi,

what database you are using?

Best regards,
Victor