NetXMS Support Forum

Hi,

is it that b.b.b.b/24 is actually 10.b.b.b/24 (i.e. within 10.0.0.0/8)? If not, could it be that those nodes actually have other interface with address in 10.0.0.0/8 subnet?

Best regards,
Victor

Hi,

when XMPP action is triggered but you do not see messages please try to capture state of netxmsd threads using attached script (you will need to install gdb and appropriate -dbg packages if you have installed server from deb repository). Also please try to set debug level to 6 and extract lines with text XMPP from server log when XMPP action is triggered.

Best regards,
Victor

Hi,

please also send walk output for .1.3.6.1.2.1.2.2.1.

Best regards,
Victor

Could you please provide SNMP walk output for OID .1.3.6.1.4.1.14988.1.1.1.3.1 on this Mikrotik device? Also, what NetXMS version you are using?

Best regards,
Victor

Yes, it's possible.

Best regards,
Victor

Update: version updated to 3.0.2357 to include small fix for regexp matching in network service checks.

Best regards,
Victor

Hi,

we just published server version 3.0.2355 - it has additional LDAP related debug output that can help in debugging.

Best regards,
Victor

Hi all!

NetXMS 3.0 patch release 5 (version 3.0.2355) is available. Only server component is affected. Changes since patch release 4:

- Fixed server crash after debug console command "show objects"
- Fixed server memory leak when exporting configuration
- Fixed server memory leak when creating ad-hoc summary tables
- Fixed bug in log writer
- Agent policies correctly uninstalled when node is deleted
- Fixed bugs in zone change operation for node
- Fixed bug in duplicate node detection
- Improved server debug output

Best regards,
Victor

Hi,

source address for connection is determined only by routing. NetXMS server itself does not specifically select source IP address. If routing is correct then it should work. For network service checks to work you should have "portcheck" sub-agent loaded in local agent (the one running on NetXMS server itself). Make sure that it is loaded. Also you may increase debug level for agent and check what is going on when server requests service check.

Best regards,
Victor

Hi,

icon represents object status, which is calculated not only from alarms but also from underlying objects (so interface in critical state will still make node critical even if alarm is terminated). Maybe we can introduce additional indicator to show outstanding alarms. This will preserve current logic and give clear indication that something new was happened.

Best regards,
Victor

Logging in with system user will help in that situation as well - it always has all access rights.

Best regards,
Victor

It looks very strange. Null pointer exception happens within tokenizer, that means that content getText() method returns null. If you can modify source and add additional logging for entity and entity.getText() that could help.

Best regards,
Victor

Also there should be some debug output. If possible attach full log for request.

I just tested on my build system and it seems to work. This is Jetty log:


2019-10-18 18:03:01,532 DEBUG | qtp635934462-14 | org.netxms.websvc.handlers.AbstractHandler              | POST: data = {"columns":[{"isRegexp":false,"dciName":"System.CPU.Usage","columnName":"System.CPU.Usage"}],"baseObject":"2"}
2019-10-18 18:03:01,533 DEBUG | qtp635934462-14 | org.netxms.websvc.handlers.AbstractHandler              | session_handle: f5b2061a-92f2-439e-b971-8769e7d85fd0
2019-10-18 18:03:01,533 DEBUG | qtp635934462-14 | org.netxms.websvc.handlers.AbstractHandler              | Handler attached to session f5b2061a-92f2-439e-b971-8769e7d85fd0
2019-10-18 18:03:01,533 DEBUG | qtp635934462-14 | org.netxms.websvc.handlers.AbstractHandler              | POST adhoc summaryTable: baseObject = 2
Oct 18, 2019 6:03:01 PM org.restlet.engine.log.LogFilter afterHandle
INFO: 2019-10-18 18:03:01 127.0.0.1 admin 127.0.0.1 8000 POST /summaryTable/adHoc - 200 115 130 12 http://127.0.0.1:8000 Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0 -


and request screenshot attached.

Best regards,
Victor

Hi,

do you have stack trace below "caused by"? Because this is seems to be root cause.

Best regards,
Victor

In version 3.0 you can set interface as related object for DCI and then access it via DCI object.

Best regards,
Victor