NetXMS Support Forum

Hi!

Try to add the following option to netxmsd.conf:

DBCacheConfigurationTables = no

Best regards,
Victor

Повторил у себя. Похоже по умолчанию в агенте слишком маленький таймаут на выполнение внешних процессов. Добавил в конфиг

ExecTimeout = 30000

и рестарт сервисов заработал.

Скорее всего у текущего пользователя нет прав на шаблоны. Попробуйте зайти пользователем system, у него всегда есть все права, и проверьте права доступа в свойствах объекта Templates.

Hi,

the tricky part is what to consider uptime. If purely time when node was unreachable (like 100 - (intervals between SYS_NODE_DOWN and SYS_NODE_UP) / period length) then it is quite simple. In fact it can be done on current version with reporting. If uptime should include more conditions, like that all services are running on the node, then it became more complicated. This is what business services were meant for, but they are very hard to configure and definitely need rework.

Best regards,
Victor

Save the date – April 29, 2021 at 5pm CET (11am EST).

We will organize online Q&A session with NetXMS developers. Please contact @moshenska in our Telegram support channel or at [email protected] to sign up.

Settings are correct, but are server really listen on that port? You can check with command

netstat -aunp | grep 514

you should see netxmsd process listening on that port.

Best regards,
Victor

Please show screenshot of DCI configuratio and agent config file. Also, set agent debug level to 6, start agent, do force DCI poll on one of problematic DCIs, and show agent log file.

Best regards,
Victor

Hi,

when using agent table for instance discovery instance names are taken from instance column in the table, in case of System.Services it will be service name. So $1 in filter script is always instance, you have no access to actual table row. I suggest to use script as instance discovery method instead of agent table, and process table i that script instead. It could looks like following:


services = $node->readAgentTable("System.Services");
if (services == null)
   return null;

instances = %();
for(r : services->rows)
{
   name = r->get(0);
   startup = r->get(4);
   if (name like "3CX*" and startup == "Auto")
      instances->append(name);
}

return instances;


Best regards,
Victor

From nxmc you see syslog records received by NetXMS server process. Check that uinternal syslog receiver is enabled and listening on correct port, and that you forward syslog messages to correct port. As you can see messages from external nodes in /var/log/messages on NetXMS server I suspect that system syslog daemon receives them, not netxmsd process.

Best regards,
Victor

Hi,

it's hard to tell from provided information. How do you collect those metrics? It looks like something custom. If those are external parameters on agent, check that agent is up and running, and check agent log for possible errors.

Best regards,
Victor

Hi,

problem is definitely with pollers pool usage, rest looks fine. I would suggest gradually increasing size of pollers pool, probably start with 750/1500 from current 250/500.

Do you use hook scripts?

Do you have routers with huge routing tables? If yes, you could try to disable routing table poll for such devices.

If netxmsd is crashing, does system generates core file? If sould be really helpful for debugging the issue.

Best regards,
Victor

Hi,

yes, I think you can delete c:\netxms\bin\jre. I have no idea why it was not working when installed into same directory. But we are going to merge server ad web UI installers into one anyway in version 4, so it should not be an issue after that.

Best regards,
Victor

Also found this thread: https://stackoverflow.com/questions/63012015/jni-createjavavm-fails-with-adopt-openjdk-11-0-8. Do you have JAVA_HOME environment set? If yes, try to remove it completely (preferred) or point to C:\NetXMS\bin\jre.

Best regards,
Victor

Very strange, I just did the same and service started correctly, so it somehow related to environment. Try to install Java 11 from AdoptOpenJDK separately - maybe we miss something when pack embedded JRE. Those are log lines that are most suspicious:

[2021-04-14 09:41:19] [error] ( javajni.c:828 ) [10492] CreateJavaVM Failed with error [-1]
[2021-04-14 09:41:19] [error] ( javajni.c:828 ) [10492] Das System kann die angegebene Datei nicht finden.

Best regards,
Victor

Изменилось ли что-нибудь после обновления на 3.8.262?