NetXMS Support Forum

Thank you for your help.

Kindest regards.

I know how to configure the number of polls needed for an activation event in THRESHOLD configuration. This is the 'samples' field.


Can this also be done for the number of polls needed for a deactivation event in THRESHOLD configuration.


At the moment when i have a look at the logging values of  a DCI with a threshold set i can see that a deactivation event already occurs after 1 poll with a value below the set threshold.
I would like to set the number of polls needed for a deactivation event  (rearm-event) to for example 5.

Anyone any suggestions?
Thanks in advance.

This issue has been solved by installing the pre-release of the next version.
NetXMS servers have been running for more than a week without any form of crashing.

Thanks Victor and others for your support with this matter.

Unfortunately the configuration mentioned in my last post (Statuspollerinterval 600, DefaultDCIPollingInterval 600, ConditionPollingInterval 600) did not last.

Server just logged the error "Thread "Item Poller" does not respond to watchdog thread" and does not poll new values anymore and displays empty graphs again.

FYI
For one location i configured the following settings on a NetXMS server:

Statuspollerinterval          600
DefaultDCIPollingInterval   600
ConditionPollingInterval     600

Although there are unrealistic values for daily operations the server has been running for more than one day now without crashing.

Still crashing.

Added some screenshots in this reply post of situation after the issue has occurred.

This issue has not been solved.

Have done some new troubleshooting.

-MySQL logging enabled and reviewed logging.
Maybe someone can tell me what to look for besides the usual error search.

-Changed some server configuration parameters, for example in one troubleshooting 'run':  increased the StatusPollingInterval from 60 seconds to 300 seconds.
and in another troubleshooting 'run' : increased PollerThreadPoolMaxSize from 250 to 500, PollerThreadPoolBaseSize from 10 to 20 and NumberOfDataCollectors from 25 to 50.

Unfortunately until now the server keeps on 'crashing' daily.

Hope there is a solution for solving this issue.

Different location. Different network. Different NetXMS server, (software new version 2.0.2)

same issue : daily server crash - Thread "Item Poller" does not respond to watchdog thread, empty graphs, no polling values

created DUMP file and log files. Attached in this reply.

Hope you can find some leads within the new information regarding this issue.

Another crash.

More log and dump files attached in this reply :  (zipped)log file and dump files

Again I hope this addition to the troubleshooting log and dump files can help in solving the issue.

Thanks in advance.

Kind regards,

Mark

From a more recent crash attached in this reply :  (zipped)log file and dump files

Hope this addition to the troubleshooting log and dump files can help in solving the issue.

Server crashed again, graphs empty and no values. NetXMS core service still appears to be running.

Executed command line : nxadm -c "raise access"
dump files were created

Attached in this reply the most recent (zipped) log file.
Also attached in this reply the 2 dump files.

Hope the team can solve this issue with the new information (logs and dumpfiles)

Thanks in advance.
Kind regards,
Mark

Server crashed again, graphs empty and no values. NetXMS core service still appears to be running.

Executed command line : nxadm -c "raise access"
dump files were created

Attached in this reply the most recent (zipped) log file.
Also attached in this reply the 2 dump files.

Awaiting your response.
Thanks in advance.
Kind regards,
Mark

Replaced the mssql.ddr file with the new mssql.ddr file, provided by you.

NetXMS Core service starting and running OK now.
Login to console also working.

It seems that the issue has been resolved.
Thank you for your help.

Kindest regards,

Mark

Hi,

Output sql queries as requested attached in this reply post.

Followed instructions.

Server is running again. Waiting for the next crash. Then i will run : nxadm -c "raise access"

I will sent log and dumpfiles after.