NetXMS Support Forum

Hi Alex,

Thank you so much for your information.
It's very helpful for me.

mulder

Hi,

I would like to make a plan to deploy NetXMS.
Do you have any indications or examples (hardware spec of server, the number of agents, etc.)?

mulder

Hi Victor,

Thank you so much for your clarification 

Regards,
mulder

Hi folks,

There would be a monitored node having multiple interfaces.
And only an interface communicating with NetXMS would be down then the node would lose communication with NetXMS server.
Would NetXMS detect the node down in that case? Or just an interface down?
Are the results same if the node has netxms agentd or not?

Regards,
mulder

Hi Victor,

Thank you very much for your prompt response
I'll try.

Regards,
mulder

Hello,

I'm wondering if I could export DCI configurations including threshold settings per node or per server.
Is it possible?

mulder

Hi,

We are using NetXMS to monitor performances, events and so forth of Windows Server 2008.
Sometimes serveral kinds of application errors which source is 'Perflib' are logged on monitored Windows Servers.
Event IDs are 1008, 1010, 1017, 1021, 1022, 1023.
Does anyone see those errors on your Windows Servers?

mulder

Hi Victor,

Perfect
We're waiting for the next release.

Does an agent work fine with a server which has different core version from the agent?

Best regards,
mulder

Hi Victor,

Thank you for your suggestion.
Now we've seen that it stopped working after log rotation. Then we found that it's necessary to restart nxagentd after log rotation.
NetXMS version is 0.2.26.

Is it likely a bug?

Best regards,
mulder

Hello Victor,

Thank you for your prompt response
In the meantime we will extend the SessionIdleTimeout.

Best regards,
mulder

Dear all,

We're also monitoring Windows 2008 servers.
Sometimes NetXMS agents generate the following warning message.

NT: <NetXMS Win32 Agent;W14;> A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. group001

We do not understand what is the problem and why does it happen.
Would someone kindly advise me?

Hello,

We are monitoring /var/adm/messages of Solaris10 using nxagentd.
After rotating of messages every Sunday 3 AM, we need to restart nxagentd.
When we restart nxagentd by "nxagentd restart", it fails to restart with the following logs.

[13-Oct-2009 13:39:15] Log file opened
[13-Oct-2009 13:39:15] Subagent "/usr/local/lib/libnsm_sunos.so" loaded successfully
[13-Oct-2009 13:39:15] Subagent "/usr/local/lib/libnsm_logwatch.so" loaded successfully
[13-Oct-2009 13:39:16] Unable to bind socket: Address already in use

It doesn't accept "kill -HUP" as well.

So we are doing stop and start in 10 seconds in stead. The logs when stop and start are;

[25-Sep-2009 18:10:14] Log file opened
[25-Sep-2009 18:10:14] Subagent "/usr/local/lib/libnsm_sunos.so" loaded successfully
[25-Sep-2009 18:10:14] Subagent "/usr/local/lib/libnsm_logwatch.so" loaded successfully
[25-Sep-2009 18:10:15] Listening on socket 0.0.0.0:4700
[25-Sep-2009 18:10:16] NetXMS Agent started

But in this case NetXMS manager detects the agent not responding.

We just want to restart the daemon smoothly.
Does anyone have any suggestions?

Best regards,
mulder