NetXMS Support Forum

Thank you, appreciate it. 

It is an address range of 10.0.140.1 - 10.0.140.30.  Maybe it is not catching the end IP's properly?

Actually, that is exactly it.  Changed my address range to 10.0.104.0 - 10.0.140.30 and it detected the router.  Either it needs fixing or we need to adjust all of our ranges?  Can you also tell if the upper end of the range has the same issue?

For us all of the queues are empty:

netxmsd: show queues
Data collector                   : 0
DCI cache loader                 : 0
Database writer                  : 0
Database writer (IData)          : 0
Database writer (raw DCI values) : 0
Event processor                  : 0
Node poller                      : 0
Syslog processing                : 0
Syslog writer                    : 0


Here is all of the debug output for one of the nodes not being rediscovered:


[25-Jul-2017 07:43:35.010] [DEBUG] DiscoveryPoller(): checking potential node 10.0.140.1 at shf00-pdu-00:1
[25-Jul-2017 07:43:35.011] [DEBUG] DiscoveryPoller(): new node queued: 10.0.140.1/22
[25-Jul-2017 07:43:35.011] [DEBUG] NodePoller: processing node 10.0.140.1/22 in zone 0
[25-Jul-2017 07:43:35.011] [DEBUG] GetOldNodeWithNewIP: ip=10.0.140.1 mac=E4:8D:8C:25:49:78
[25-Jul-2017 07:43:35.012] [DEBUG] AcceptNewNode(10.0.140.1): auto filter, flags=0004
[25-Jul-2017 07:43:35.012] [DEBUG] AcceptNewNode(10.0.140.1): auto filter - checking range
[25-Jul-2017 07:43:35.012] [DEBUG] AcceptNewNode(10.0.140.1): auto filter - range check result is 0
[25-Jul-2017 07:43:35.124] [DEBUG] DiscoveryPoller(): checking potential node 10.0.140.1 at shf00-pdu-00:1
[25-Jul-2017 07:43:35.128] [DEBUG] DiscoveryPoller(): new node queued: 10.0.140.1/22
[25-Jul-2017 07:43:35.128] [DEBUG] NodePoller: processing node 10.0.140.1/22 in zone 0
[25-Jul-2017 07:43:35.128] [DEBUG] GetOldNodeWithNewIP: ip=10.0.140.1 mac=00:00:00:00:00:00
[25-Jul-2017 07:43:35.129] [DEBUG] AcceptNewNode(10.0.140.1): auto filter, flags=0004
[25-Jul-2017 07:43:35.129] [DEBUG] AcceptNewNode(10.0.140.1): auto filter - checking range
[25-Jul-2017 07:43:35.132] [DEBUG] AcceptNewNode(10.0.140.1): auto filter - range check result is 0


But still the node is never getting added.  Also, both the Active Discovery Targets and Address Filters sections of the Network Discovery Configuration contain the address range for this IP.

There is nothing for these nodes when logged in under system or using nxadm -c "show objects".  I have also as the other person tried restarting the server to see if they will get automatically discovered again and no luck with that.

I had a number of nodes that I had significantly changed the templates for and thought it would be a great idea to delete the nodes and let them get discovered again.  I has been past an activediscoveryinterval (900s) and they are not coming back.  Wondering if there is something I need to do to get them to come back or if I will just need to add them all manually.  This is on a 2.1 server.

Marco:

Does the 2.1 mobile agent address this issue?

Any ETA on the packages for this release?

Thanks for the update, please post about the console as well once that has been resolved.  Looking forward to the next release!

Thanks for the update, hope the issues get resolved in the released version as they are pretty critical to our being able to use it.

This did indeed resolve the issue.  Thanks!

Any ETA on 2.1RC2?  I have at least three major issues posted to the forums that have no response / resolution. 

Might want to consider editing your post and removing passwords!  Also centos7 user why not delete your repost.

Installed the 2.1RC1 mobile agent APK on a Galaxy S7 (model: SM-G30R4) running Android 7.0.  As soon as I enabled Location Strategy of Network & GPS the app started crashing (and wanting to e-mail crash reports) - CONTINUALLY!!!!  Could not really do anything as it just kept opening the mail window wanting to send another crash report.  Finally, was able to reboot phone and uninstall Agent before it started the crash loop.  Did try to restart before that and see if that would resolve but it kept on crash looping as previouly.

The client needs to crash and stay crashed, this was really annoying and I suspect a typical user would have had no idea how to get out of it.  I am perfectly fine wanting to e-mail a crash dump and hopefully you have a few from me, but the crash / e-mail loop needs immediate resolution. 

Seems 2.1 has a way to go from what we are seeing from a stability and functionality standpoint.  It is a great product and I am sure it can be overcome, thanks!

We are running Ubuntu 16.04 from packages.  The agent running on the server will NOT however connect to the server itself.  Running the agent with -D 9 -f we only see:

[19-May-2017 13:35:09.775] [DEBUG] Incoming connection from <serverIp>
[19-May-2017 13:35:09.776] [DEBUG] Connection from <serverIp> rejected

The nxagentd.conf file is very basic:

MasterServers = 127.0.0.1
FileStore = /tmp
StartupDelay = 30
EnableActions = yes
SubAgent = portcheck.nsm
*portCheck
Timeout = 5000
*ping
Timeout = 5000

I see the modules all loading and things seem fine.  Have tried using the real IP for the MasterServers and no help.  Tried also debugging the server and did not get anything that helped from that either.

Resolved this on my own, by specifying the character set on the DB create:

QuoteCREATE DATABASE netxms CHARACTER SET utf8;