NetXMS Support Forum

English Support => General Support => Topic started by: Benjamin Dill on September 06, 2024, 02:54:45 PM

Title: Server crash on "Supported actions"
Post by: Benjamin Dill on September 06, 2024, 02:54:45 PM
I'm getting a server crash on object tool "Supported actions". It is the pre-defined object tool.
I first noticed it in 5.0.7 and it still happens on 5.0.8. Server is running on Windows, agent is also on 5.0.8, but it seems the agent version does not make any difference.
Title: Re: Server crash on "Supported actions"
Post by: Filipp Sudanov on September 06, 2024, 03:24:23 PM
Please enable

CreateCrashDumps

in server config file and specify folder to store them by DumpDirectory parameter in config (Default is C:\)

Share the file somewhere and send me link to in in private message (or I can provide a place to upload it if needed)
Title: Re: Server crash on "Supported actions"
Post by: Benjamin Dill on September 10, 2024, 09:40:50 AM
I tried that but it seems there is no crash dump created. Is this possible or am I looking at the wrong place?
Title: Re: Server crash on "Supported actions"
Post by: Filipp Sudanov on September 10, 2024, 09:51:03 AM
Well, could be that something related to crash dumps is broken.

As additional check, can you stop NetXMS Core service and run server manually from Windows command line:

c:\NetXMS\bin\netxmsd -D 6

pls show last line of output, when it crashes.
Title: Re: Server crash on "Supported actions"
Post by: Benjamin Dill on September 10, 2024, 10:15:20 AM
I switched to DebugLevel = 7 before trying the crash dump, so I have this already:

Quote2024.09.10 08:35:09.059 *D* [db.cpool          ] Handle 00000217E16C5300 acquired (call from c:\jenkins\workspace\release-windows\src\server\core\objtools.cpp:86)
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 released
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 acquired (call from c:\jenkins\workspace\release-windows\src\server\core\objtools.cpp:120)
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 released
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 acquired (call from c:\jenkins\workspace\release-windows\src\server\core\objtools.cpp:561)
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 released
2024.09.10 08:35:09.060 *D* [client.session.0  ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.09.10 08:35:09.060 *D* [db.cpool          ] Handle 00000217E16C5300 acquired (call from c:\jenkins\workspace\release-windows\src\server\core\objtools.cpp:255)
2024.09.10 08:35:09.061 *D* [node.agent        ] Node::createAgentConnection(XXXX [46389]): using agent tunnel
2024.09.10 08:35:09.061 *D* [agent.conn.403    ] New connection created (address=UNSPEC port=0 compression=allowed)
2024.09.10 08:35:09.061 *D* [agent.tunnel.180  ] Sending message CMD_CREATE_CHANNEL (2)
2024.09.10 08:35:09.063 *D* [agent.tunnel.180  ] Received message CMD_REQUEST_COMPLETED (2)
2024.09.10 08:35:09.063 *D* [agent.tunnel.180  ] createChannel: new channel created (ID=290)
2024.09.10 08:35:09.064 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.064 *D* [agent.conn.403    ] Using NXCP version 5
2024.09.10 08:35:09.064 *D* [agent.conn.403    ] Sending message CMD_REQUEST_SESSION_KEY (1) to agent at UNSPEC
2024.09.10 08:35:09.066 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.066 *D* [agent.conn.403    ] Received message CMD_SESSION_KEY (1) from agent at UNSPEC
2024.09.10 08:35:09.079 *D* [agent.conn.403    ] Sending message CMD_AUTHENTICATE (2) to agent at UNSPEC
2024.09.10 08:35:09.080 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.080 *D* [agent.conn.403    ] Received message CMD_REQUEST_COMPLETED (2) from agent at UNSPEC
2024.09.10 08:35:09.080 *D* [agent.conn.403    ] Sending message CMD_SET_SERVER_CAPABILITIES (3) to agent at UNSPEC
2024.09.10 08:35:09.080 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.080 *D* [agent.conn.403    ] Received message CMD_REQUEST_COMPLETED (3) from agent at UNSPEC
2024.09.10 08:35:09.081 *D* [node.agent        ] Node::createAgentConnection(XXXX [46389]): conn=000002178265C090
2024.09.10 08:35:09.081 *D* [agent.conn.403    ] Sending message CMD_GET_LIST (4) to agent at UNSPEC
2024.09.10 08:35:09.081 *D* [agent.tunnel.180  ] Received message CMD_CHANNEL_DATA (290)
2024.09.10 08:35:09.081 *D* [agent.conn.403    ] Received message CMD_REQUEST_COMPLETED (4) from agent at UNSPEC
Title: Re: Server crash on "Supported actions"
Post by: Filipp Sudanov on September 10, 2024, 11:56:20 AM
Looks like DumpDirectory should be specified for dump collection to work. Pls create C:\NetXMS\crash
 folder and try the following in netxmsd.conf:

CreateCrashDumps=yes
DumpDirectory=C:\NetXMS\crash
Title: Re: Server crash on "Supported actions"
Post by: Benjamin Dill on September 10, 2024, 02:09:51 PM
I did that, I see there a log file created, but no dump files unfortunately.
Title: Re: Server crash on "Supported actions"
Post by: Filipp Sudanov on September 10, 2024, 02:15:56 PM
Log file in C:\NetXMS\crash ?
Pls share it
Title: Re: Server crash on "Supported actions"
Post by: Benjamin Dill on September 10, 2024, 02:18:45 PM
Attached.
Title: Re: Server crash on "Supported actions"
Post by: Filipp Sudanov on September 13, 2024, 12:29:08 PM
The crash collector service seems to be running fine, so seems that server is nor really crashing.

Can you stop netxms core service and run it from command line:

C:\NetXMS\bin\netxmsd -D 6

and once the issue occurs, pls share the screenshot of whole cmd window.
Title: Re: Server crash on "Supported actions"
Post by: Benjamin Dill on September 14, 2024, 11:34:15 AM
I just did an empty server installation for testing, it still happens. The server process just exits.
Title: Re: Server crash on "Supported actions"
Post by: Filipp Sudanov on September 16, 2024, 02:02:03 PM
Does it happen with some remote agent, or also with agent that runs along with the server?

For now the reason is not clear. Can you enable DebugLevel 8 on the server and that agent and share their logs?

Any chances we can remote access to this Windows system?
Title: Re: Server crash on "Supported actions"
Post by: Benjamin Dill on September 18, 2024, 07:24:55 PM
Ok, I did some further testing. As I said, I installed a blank server, but the agent had already some configuration pulled from our production server, and one setting trigged the crash apparently.
The issue seems to be an "Action" with long command:

Action = Test:echo abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890!@$%
Add this to the agent's configuration and the object tool "Supported actions" will crash the server process.
Title: Re: Server crash on "Supported actions"
Post by: Victor Kirhenshtein on September 19, 2024, 11:56:32 AM
Just fixed it. Fix will be included into next release. Thank you for debugging and providing steps to reproduce!

Best regards,
Victor