Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#571
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
#572
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
#573
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
#574
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
#575
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
#576
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
#577
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
#578
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
#579
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
#580
Изменилось ли что-нибудь после обновления на 3.8.262?
#581
Did you change service to run under "Local System" after clean install?

Best regards,
Victor
#582
General Support / Re: Daylight savings time issue
April 13, 2021, 08:37:50 PM
Hi,

it seems to be related to how underlying framework (Eclipse RAP) handles time zone settings provided by browser. I will investigate it further.

Did you tried connecting from different browser? If you set workstation to other UTC-7 time zone without DST, will both desktop and web client show correct time?

Best regards,
Victor
#583
Hi,

attached is corrected MIB file. Problem was with some object identifiers starting with capital letter. Standard does not allow object identifiers to start with capital letter, but many vendors does this anyway.

Best regards,
Victor
#584
Did you install it on top of old version? If yes, try to remove it and do clean install (make sure to manually delete all remaining work directories after uninstall). Select bundled JVM when installing.

Best regards,
Victor
#585
Не совсем понятно о чем именно идет речь. Можно поподробнее описать где что было до того как пропало?