NetXMS Support Forum

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

Hi,

this is because ~= operation now returns array of capture groups instead of boolean value. It works as expected in "if" statement and other places where logical expression is expected, but "return" statement just returns array, which is ignored by poller code. This is bug in a poller which we will fix. As a workaround you can use expression like this:

return ($node->sysDescription ~= "CSS") ? true : false;

Best regards,
Victor

Hi,

could you show dependency walker output?

Best regards,
Victor

Hi,

what version you are using? Did you use minimal or full installer? If minimal, what is PostgreSQL client version? Could it be that libpq.dll in your PATH is 32 bit executable?

Best regards,
Victor

Hi all!

NetXMS 3.0 patch release 4 (version number 3.0.2329) is available. Changes since patch release 3:

- Fixed bug in SMS driver to notification channel conversion
- Fixed bug in GSM notification channel driver
- Fixed bug in server that can cause netxmsd crash
- Fixed bug in Megatec UPS driver
- Improved access to collected performance data on Timescale DB
- Minor UI bug fixes

Best regards,
Victor