NetXMS Support Forum

Hi,

you probably should check database health and performance first - it could be that for some reason database is unable to handle INSERTs for collected data. Also, check that database connection pool is not exhausted (you can check log file for DB connection pool related errors as well as check active pool connections with show dbcp command in server debug console). You may also try to increase value of server configuration parameter DBWriter.DataQueues.

Best regards,
Victor

Hi,

yes, it was fixed in 2.2.13. We also plan release 2.2.14 next week.

Best regards,
Victor

Hi,

after you unpack archive you should have nxmc (or nxmc.exe on Windows) executable inside whatever target directory you were using for extraction. Just run it.

Best regards,
Victor

Right click on node, select Tools->Info->Agent->Subagent list

To load subagent add

SubAgent = name.nsm


to your nxagentd.conf.

Best regards,
Victor

"Access denied" error means that current user has no access to user database. Also, before creating user you have to lock user database, like this:


s.lockUserDatabase()
s.createUser("new_user")
s.unlockUserDatabase()


Best regards,
Victor

Did you install openssl-devel package?

This is from my RHEL 7 system:

build-rhel-7-x64:~$ rpm -qa | grep openssl
openssl-libs-1.0.2k-16.el7_6.1.x86_64
openssl-devel-1.0.2k-16.el7_6.1.x86_64
openssl-1.0.2k-16.el7_6.1.x86_64

Best regards,
Victor

Can you provide more details on in what form you have utilization data?

Best regards,
Victor

Actual failure related to OpenSSL libraries:

./conftest: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Make sure you have matching libssl development and binary packages and that correct libssl.so is in library path.

Best regards,
Victor

Hi,

NetXMS comes with some VMWare MIBs pre-packed:

VMWARE-AGENTCAP-MIB.txt
VMWARE-CIMOM-MIB.txt
VMWARE-ENV-MIB.txt
VMWARE-OBSOLETE-MIB.txt
VMWARE-PRODUCTS-MIB.txt
VMWARE-RESOURCES-MIB.txt
VMWARE-ROOT-MIB.txt
VMWARE-SRM-EVENT-MIB.txt
VMWARE-SYSTEM-MIB.txt
VMWARE-TC-MIB.txt
VMWARE-VC-EVENT-MIB.txt
VMWARE-VCOPS-EVENT-MIB.txt
VMWARE-VMINFO-MIB.txt

If you add same MIBs them may be just redundant. If you add new MIB files to MIB directory, make sure they have .txt extension - directory compile option only reads txt files.

Best regards,
Victor

Hi,

could you please provide full config.log?

Best regards,
Victor

Custom templates should not be affected by that setting. If they do it likely means that template is not saved to database. Check that you do not have any SQL errors in server log and if database table "items" contains changes for your custom template.

Best regards,
Victor

Hi,

if those were standard templates then likely they were re-imported on startup. If this is the case set server configuration variable ImportConfigurationOnStartup to false. In 2.2.14 we changed that logic to only import missing templates and events by default.

Best regards,
Victor

Hi,

from configuration poll output it looks like SNMP is not detected on the node. Make sure that community string is correct and SNMP requests from NetXMS serever are allowed on device. You can use command line tools nxsnmpget and nxsnmpwalk to check if SNMP requests are going through.

Best regards,
Victor

Yes, this is normal. On startup agent logs unexpanded file name. You should also see something like this when file is found:

2019.04.12 12:03:13.608 *D* [logwatch           ] File "/tmp/test-20190412.log" (pattern "/tmp/test-`date +%Y%m%d`.log") successfully opened

Are you sure your commands return correct values? You may also try to use cmd /c "command" within backticks (because echo for example is not an external executable but cmd's internal command).

Also, if you only need current date/time you may use date/time macros without external commands, like this:

<file>C:\inetpub\wwwroot\website\logs\Log_%Y_%m_%d.txt</file>

Best regards,
Victor

А, до меня дошло ПОка что ничего не приходит в голову кроме как добавить опцию создания виртуальной ID колонкиу на основе OID. Подумаю еще над этим.