NetXMS Support Forum

Hi,

we do not recommend to use SQLite in production environment. Due to very limited SQLite capability for changing schema (basically you can only add new column) upgrade procedures often file. We do create workarounds for this, but sometimes (as now) SQLite versions of upgrade procedures are not ready. I recommend to limit SQLite use to proof of concept systems and migrate to other supported DB when possible.

Best regards,
Victor

Hi,

seems to be a bug in server. What version you are running and on what OS? Do you have crash dumps?

Best regards,
Victor

Hi,

there are no separate parameters for that, but you can use transformation script to extract needed part from System.Uname (likely using regular expressions).

Best regards,
Victor

Hi,

you have to pass some valid email address as request. Rest of parameters are the same as for all other ServiceCheck.* parameters. Response field is ignored. Checker will send test email and return 0 if it was successfully sent. More information here: https://netxms.org/documentation/adminguide/service-monitoring.html#network-service

Best regards,
Victor

Hi,

in 2.2.3 we have added fix for incorrect value type in transformation script. If you are running older version, try to change transformation script to


return uint64($1) * 8;


Best regards,
Victor

Hi,

NetXMS has "helpdesk links" - loadable modules that provide interface to ticketing system. If ticketing system supports it, this module can provide two-way integration (as done for Jira). Currently such modules exists only for Jira and RedMine. Unfortunately they are not scripts, but shared libraries written in C++. If you have C++ developers you can build your own link using Jira as example. For 3.0 branch we are considering Python and/or JavaScript extension support, but that's long way ahead anyway. You can also order custom development from our company.

Best regards,
Victor

Hi,

did you unpack UI over previous version? Sometimes it keeps some components in the cache. Try to unpack into empty directory and run from there.

Best regards,
Victor

Hi,

we will release 2.2.4 with a fix this week.

Best regards,
Victor

Hi,

so far the only option is to write nxshell script.

Best regards,
Victor

Release 2.2.4 will contain improved Portech driver that should work with newer gateway versions.

Best regards,
Victor

Hi,

yes, that's definitely an issue. Check that you have NetXMS server's external address in MasterServers on local agent.

Best regards,
Victor

Hi,

you can use instance discovery to create same counters for each pool. You should be able to use agent list

PDH.ObjectInstances(ASP.NET Apps v2.0.50727)

Best regards,
Victor

Changed it (only for new nodes - because property page shows what is set for node). Change will be included into 2.2.4 release.

Best regards,
Victor

Hi,

please try to upgrade agent to this version: https://cloud.netxms.org/index.php/s/6AhhFsSt8hKTXbW

Best regards,
Victor

Hi,

will fix it tomorrow.

Best regards,
Victor