NetXMS Support Forum

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

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

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

Самое простое - увеличить размер колонки vendor в таблице node_components. Например так:

ALTER TABLE node_components MODIFY COLUMN vendor varchar(127) NULL;

Увеличит размер до 127 с текущих 63.

Или подождать до следующего патч релиза - я добавил контроль длины значения при записи в эту таблицу, слишком длинные значения будут обрезаться.

Hi,

log file just states that service cannot be started. Is there any other log files?

Best regards,
Victor

Hi,

it should work, although we didn't test it specifically on that version. Just report here if you will encounter any issues.

Best regards,
Victor

Hi,

it was supposed to be in separate deb package, but it was not published. We will publish it in a few days.

Best regards,
Victor

Hi all!

We just published new patch release for version 3.8 (3.8.267). Only server and web API are affected. Changes since release 3.8.262:

- Fixed server crash during scheduled task processing
- Fixed issues:
        NX-2009 (Add notification channel driver "Shell command")
        NX-2035 (Instance discovery using ICMP.Targets list crashes server)
        NX-2037 (Save IP address of client connecting via WebAPI to audit log)

Best regards,
Victor

Hi,

most likely you have hit RAM limit when allow thread pool to grow to 4000 threads. Could also be other memory-related issue (memory leak in server, slow database causing DB writer queues to grow, etc. Do you have pre-crash data on number of threads, queues, and memory consumption?

Also, 4000 nodes is not that much, it is quite strange that 500 threads is not enough. Such high load on poller pool indicates that there are lot of polls taking long time to complete.  Could it be that you have many nodes that timeout when polled?

Best regards,
Victor

Hi all!

New patch release for version 3.8 - 3.8.262 - is just published. Changes since version 3.8.250:

- Fixed server crash when accessing NXSL class metadata
- Fixed agent crash when parsing log files
- Fixed file handle leak in log parser subagent
- DCI Editor filter now search by description, parameter, and DCI ID
- Long polling can be disabled in Telegram driver
- Fixed Log Parser Policy save with empty agent action field
- Fixed issues:
        NX-1770 (Add ability to filter by DCI name in DCI list)
        NX-2033 (Incorrect interface name displayed in MAC address table for Mikrotik routers)
        NX-2036 (Filter in DCI editor should search both description and parameter)

Best regards,
Victor

Hi,

we likely found the issue. New patch release will be available in a next few days, please re-test this issue then.

Best regards,
Victor

В списке файлов очень много раз встречается /var/log/auth.log.1, /var/log/mail.log.1, и /var/log/apcupsd.events. На агенте не настроен мониторинг этих файлов через logwatch?

Hi,

that one looks like PostgreSQL problem - server drops connection for some reason. Check in Postgres or system log if it was restarted.

Best regards,
Victor

Hi,

looks like bug in nxdbmgr. Somebody from dev team will check.

Best regards,
Victor

Default path for source install is /usr/local/bin and /use/local/lib. It looks like old version is in your path, so command

which nxdbmgr

should show it's location.

Best regards,
Victor