NetXMS Support Forum

Раз в час по умолчанию стартует housekeeper - он удаляет из базы устаревшие записи (из логов и собранных данных). Возможно есть смысл увеличить интервал между запусками - это регулируется параметром HouseKeepingInterval.

Finally I've found a problem. Syslog parser is really broken in 1.2.5. I've fixed it, so 1.2.6 will work again. I plan to release 1.2.6 somewhere next week. It will be mostly bugfix release, which will address some important issues in 1.2.5.

Best regards,
Victor

Hi!

It will poll all of the configured addresses. When it's done, server will wait for time specified in ActiveDiscoveryInterval and then repeat the process.

Best regards,
Victor

Hi!

Custom logo must be available for application server (not the client!) via URL http://127.0.0.1/netxms_login.dat. So, if you are running NetXMS UI on application server at address 192.168.1.1, request for http://192.168.1.1/netxms_login.dat must give you the logo (assuming web server listen on all interfaces).

Best regards,
Victor

Как правило это означает, что нет данных в выбранном промежутке времени. Проверьте, когда последний раз собирались данные для этих DCI. Еще бывает из-за расхождения времени на сервере и рабочей станции.

Hi!

Currently certificate authentication is only supported in legacy Windows console. We will add certificate authentication to the web and Java UI in near future (probably in 1.2.7 or 1.2.8 release).

Best regards,
Victor

Hi!

Looks like MySQL issue. You should try to run REPAIR TABLE on all reported tables: http://dev.mysql.com/doc/refman/5.0/en/repair-table.html. Probably there also should be a tool to repair all of them.

If you decide to re-create database, you can try to do export and then import into empty database with nxdbmgr export and import commands. I also suggest to try out PostgreSQL as backend database.

Best regards,
Victor

Hi!

Make sure that console version match your server's version.

Best regards,
Victor

could you run server with debug level 5 for some time and send me the log? Preferrably with screenshot of network discovery configuration?

Best regards,
Victor

Hi!

Is it possible to send me diagram of how nodes and management server are connected? You can send it to my e-mail to avoid posting on the forum.

Best regards,
Victor

Hi!

I suppose it's a UNICODE issue. Can you try to downgrade agent on one of the servers to 1.2.2 and see if problem disappears?

Best regards,
Victor

Then it looks strange. Can you run server for some time with debug level 5 and send me the log after you got unexpected SYS_NODE_UNREACHABLE?

Best regards,
Victor

Hi!

Yes, it should work. You should get SYS_NODE_UNREACHABLE instead of SYS_NODE_DOWN, and node should go to UNKNOWN state instead of CRITICAL. It then become NORMAL again when connectivity restored.

Best regards,
Victor

Автобинд скрипт - это атрибут контейнера, и всегда выполняется только для того контейнера, в котором определен. Если вы используете общий скрипт из библиотеки, то при вызове из каждого конкретного контейнера можно передавать его имя или идентификатор как параметр. Перебрать все custom attributes нельзя, надо знать их имена.

Hi!

This is due to topology-based event correlation. Idea is to suppress multiple SYS_NODE_DOWN events if they are caused by intermediate router failure. If only end node was disconnected and still server generates SYS_NODE_UNREACHABLE instead of SYS_NODE_DOWN, then this is a bug. Unfortunately this feature cannot be turned off. I'll add appropriate option in 1.2.6. As a workaround, you can disable routing table polls on intermediate routers - if NetXMS server will not know full route to the node, it will not try to do such correlation.

Best regards,
Victor