NetXMS Support Forum

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

Hi,

readAgentList is a node object method, so if you were calling

AgentReadList($node, ...

(read agent parameter from node pointed by $node variable) you now should use

$node->readAgentList(...

to read list from agent on same node.

Best regards,
Victor

Those errors should be gone once you upgrade all agents. There were bug in agent that cause it to report identical entries in software list.

Best regards,
Victor

Hi,

event will still be generated but you can suppress creation of alarm from it (which I understood is what you want). You have two options here:

1. Use filtering script in EPP rule to check current time and ignore SYS_NODE_DOWN if it is during non-working hours.
2. Schedule recurring maintenance for workstations for night hours and weekends.

Best regards,
Victor

We will publish announcement as usual and update download page and Debian/Ubuntu repositories.

Best regards,
Victor

Hi,

just sent you upload link for logs in PM. We will take a look at this when logs will be available.

Best regards,
Victor

Hi,

I just fixed that. Fix will be included into next patch release.

Best regards,
Victor

Hi,

version 3.0 hides interfaces in object tree by default (this significantly improves UI performance on large number of nodes). You can switch back to old behavior by unchecking "hide node components" checkbox in object tree view menu.

Best regards,
Victor

Hi,

looks like a bug in UI. What version you are using? Is it web or desktop UI?

Best regards,
Victor

Hi,

is there some kind of deadlock logging in MariaDB? This can help if we can find out what transaction holds the lock. If it was not logged I think we have to wait for next occurrence and then if I understand correctly command SHOW ENGINE INNODB STATUS should show active transactions and their locks which can provide useful information.

Best regards,
Victor