NetXMS Support Forum

Hi,

Hopping over from https://www.netxms.org/forum/general-support/netxmsd-hangs-during-startup/ to say thanks for the pointer towards alarm_events which solved my issue!

I also had a huge number of rows in this table, and found the culprit in a misconfigured event processing policy which was catching too many events. You may also have something similar.

In my case I discovered it by looking at alarms with very high repeat counts. If you open the alarm details it will show the EPP rule which created it.

I found the cause, someone had checked the "inverse rule" checkbox on the event condition of the "show alarm when node is down" EPP rule.
This caused every event except the actual node down one to trigger and be correlated to a NODE_DOWN_%i alarm per node.

I've corrected this and will monitor the table growth.
We probably will have to do some alarm cleanup as well.

After looking at https://www.netxms.org/forum/general-support/the-table-alarm_event-is-full-in-netxms-4-5-3-1-version/ I checked the alarm_event table and found it contained 52 million rows and took up most of the database size.

I truncated this table, and the NetXMS Core service started right back up, so it appears this was the cause of the issue!
Unfortunately I didn't have an error message to point in that direction.

I have Alarms.HistoryRetentionTime and Events.LogRetentionTimeon 15 days, is there another server parameter relevant for the alarm_event table?

Hi,

We have NetXMS 4.4.2 running on a Windows 2019 server for a few months, however after the server was restarted yesterday we are no longer able to connect. The netxmsd.exe process is running and taking ~50% CPU, but looking at the netxmsd.log it appears to freeze mid startup. (see attached)

I ran nxdbmgr check and check-data-tables with clean results, tried reinstalling NetXMS, installed on a different machine and pointed to same database, but all with the same results.
I suspect something got corrupted in the database and is causing the server to lock up.

We're using MSSQL Server 2016 and the ODBC driver. The database is accessible through SQL management studio and appears to be otherwise healthy (as also attested by nxdbmgr)

Are there any further troubleshooting steps I can take?
I can provide debuglevel 9 logging or other detailed information via private message if needed. I haven't found any "smoking gun" error messages so far, unfortunately.

Should I try an update to a later version?

Thanks in advance!

Hi,

Has the problem with saving SNMP community/authentication settings in node properties been resolved? (https://www.netxms.org/forum/announcements/netxms-3-0-patch-release-5-(version-3-0-2355)/msg26998/#msg26998)
I couldn't find it in the change log, but it's troubling us a bit too.

Thanks for the great work!

Hi,

We had some problems after upgrading to v2.0.8 from v2.0.2 on Windows 2008 R2. (DB: SQL Server Express 2012)
After the upgrade, we would get an error message "the connection timed out" when trying to connect with the NetXMS Console.

After setting DebugLevel in netxmsd.conf to 7 and restarting the NetXMS Core service, the following  error message started appearing in the log:
[16-May-2017 14:49:38.523] [DEBUG] Database Connection Pool exhausted (call from .\config.cpp:344)

I stopped the service, increased DBConnectionPoolMaxSize in the config table of the database from 40 to 100 and restarted it after which the problem appears to be solved.
Posted here for reference for other users and any suggestions.

Server statistics:
Total number of objects: 53241
Number of monitored nodes: 1016
Number of collectable DCIs: 6447

Hi,

Our NetXMS v2.0.2 server on Windows 2008 R2 stopped working today and kept crashing on startup. The event log showed
[ERROR] EXCEPTION 0xC0000005 (Access violation) at 0x00659F20 (crash dump was generated);
From the crash dump I found it was caused by nxcore!ScheduledMaintenance+0x150, which appears to have something to do with nodes that have been set to maintenance mode.

I checked the database and found that there were some entries in the scheduled_tasks table pointing to IDs of nodes that have been deleted meanwhile. Unfortunately, running "nxdbmgr check" did not clean these up, so I deleted them manually and the problem was gone.

Not sure if this is something already solved in a later version or not, but thought I'd let everyone know in any case!

Hi,

Is there any news on this? Has anyone else been able to check this in the Windows console?

We have the same upload dialog and problem when installing the 2.0.3 console from scratch.

Thanks!

Kind regards,
Bastiaan Defloo

Hi,

Yes, we upgraded both the server and console to v2.0.2, from v1.2.16. See attached screenshot from the console that was installed by the server installer on the same machine, we have the same issue and file upload dialog there as well.

Maybe it's a problem in the console package for Windows?
I've uploaded the output from the "installation details" button as well, maybe you can find something in the version numbers of the org.netxms.ui.* plugins.

Thanks for the help!

Hi,

As a test, I've uploaded a test file to the server using the console, and attempted to upload it from the server to a node.
Clicking OK in the window shown in "start upload.png" does nothing, the window remains open.

I've also tried setting the debug level to 9 on the server, but I don't find anything in the resulting log about a file upload.
I wonder if there is some way we can determine if it's a bug in the console? (eg command not being sent to server)

(There's also a small bug in the Server File Manager, if you freshly upload a file it always shows the File Size as 0)

Kind regards,
Bastiaan Defloo

Hi,

We're trying to upload a file from the server to the agent, using the desktop console.

Hi,

Since upgrading to v2.0.2 the "upload file" tool in the console no longer seems to work. (server, console and node all running on Windows Server 2008 R2)

The upload file dialog opens when clicking "upload file" in the context menu of a node with the agent installed, and we can select a file from the list of files available on the server, but nothing happens when we click OK. The dialog simply remains open.
I tried this on nodes with various agent versions (2.0.2, 1.2.13)

We're uploading the files manually as workaround for now.

Kind regards,
Bastiaan Defloo

Thanks for the fast reply and excellent software and support!

Kind regards,
Bastiaan Defloo

Hi,

After upgrading to v2.0.2 on Win2008R2 x64 we're having an issue in the NetXMS Console:
We can no longer select, right click or drag and drop objects in network maps, if the map has an image as background.

Also, with the "display objects as -> small labels" option, the text is now very hard to read against the background, because the label background is now transparent rather than opaque. Can this be configured somewhere?

Thanks!

Hi,

Just a quick heads up. We just upgraded from v1.2.16 to v2.0.2 and the nxdbmgr.exe tool crashed when trying to upgrade from database version 383. Also using SQL Express 2012.

After replacing the mssql.ddr file with the one from this forum thread this was successful.

Thanks!