NetXMS Support Forum

Добрый день!

Это баг в сервере, только что исправил. В релизе 2.0.3 будет работать как надо. Если срочно, то могу собрать бинарник сервера с патчем.

Hi,

could you please send me list of switch interfaces with IP addresses (as shown on "Interfaces" tab) and screenshot of "Overview" tab?

Best regards,
Victor

Hi,

can you please add the following to netxmsd.conf:

DebugLevel = 7
CreateCrashDumps = yes

as well as ensure that LogFile points to some file, not {syslog}, and restart it. When server hangs, run

nxadm -c "raise access"

server process will crash and dump will be generated. Send dump file and log file to us for analyze.

Best regards,
Victor

Hi,

you should compile it from MIB files using MIB compiler, like this:

nxmibc -z -d /usr/local/share/netxms/mibs -o /usr/local/var/lib/netxms/netxms.mib

(replace /usr/local with actual installation prefix).

Best regards,
Victor

Hi,

looks like server is crashing on startup. Can you please enable crash dump generation by adding

CreateCrashDumps = yes
DumpDirectory = some existing directory

to netxmsd.conf, star tserver again, and sent info and mdmp file to us?

Best regards,
Victor

Hi,

I've found bug in server code that is causing this. It will be fixed in release 2.0.3. If this is urgent I can build patched server binary for you.

Best regards,
Victor

Hi,

seems to be a bug in a server. What version you are using?

Best regards,
Victor

Activity looks strange actually. There are multiple occurences of this pattern:

[27-Jan-2016 09:19:38.747] [DEBUG] [session:1] Session disconnected by timeout (last activity timestamp is 1453882717)
[27-Jan-2016 09:19:38.747] [DEBUG] [session:1] Session with 192.168.25.17 closed
[27-Jan-2016 09:19:42.835] [DEBUG] Incoming connection from 192.168.25.17
[27-Jan-2016 09:19:42.835] [DEBUG] Connection from 192.168.25.17 accepted

then normal session init, parameter queries, and suddenly again session disconnect by timeout and almost immediate reconnect:

[27-Jan-2016 09:19:42.850] [DEBUG] [session:1] Requesting parameter "Agent.Uptime"
[27-Jan-2016 09:19:42.850] [DEBUG] [session:1] Sending message CMD_REQUEST_COMPLETED (size 56)
[27-Jan-2016 09:20:43.861] [DEBUG] [session:1] Session disconnected by timeout (last activity timestamp is 1453882782)
[27-Jan-2016 09:20:43.861] [DEBUG] [session:1] Session with 192.168.25.17 closed

and inactivity timeout seems to be very short. Could it be that you have agent configuration parameter SessionIdleTimeout set to 0?

Best regards,
Victor

Hi,

could you please describe problem in more details, or maybe show a screenshot?

Best regards,
Victor

Hi,

there is a tutorial on sending notification: https://wiki.netxms.org/wiki/How_to_send_e-mail_notification_when_disk_space_is_low - just skip data collection and threshold part and use SYS_NODE_DOWN event in event processing policy.

Best regards,
Victor

Hi,

in 2.0.3 we have added GPS subagent that is capable of providing location information using NMEA compatible GPS receivers. Location information for nodes with GPS subagent will be updated during status polls.

Best regards,
Victor

Hi,

currently action execution requires direct connection to agent (when zoning was implemented we just forgot about that). I've added it as feature request (https://dev.raden.solutions/issues/1154).

Best regards,
Victor

Hi,

that likely means that you don't have netxms.mib in right place on server. It should be in <install_prefix>/var/lib/netxms (or in /var/lib/netxms if you install server from deb package). There was other topics on forum on MIB compilation and location, you can check them as well.

Best regards,
Victor

Hi,

you have to load portcheck.nsm subagent on proxy agent and specify proxy node as poller node either for network service or for it's node.

Best regards,
Victor

Hi,

currently there are no easy way to do what you want except for nxshell scripts. As you have access to full client API in nxshell you can do anything that can be done from management console.

I see two easy to implement options to simplify things in future versions:

1. add "non-inheritable" option to ACL entries;
2. Option to add ACLs to multiple selected objects. While adding can be implemented easily, mass edit could be quite complicated because objects may already have different access right assignments.

Best regards,
Victor