NetXMS Support Forum

Похоже что war файл запаковали с ошибками. Подождите несколько дней до выпуска 1.2.12, там будет корректный war.

Проверьте еще лог самого приложения. Он называется .log и находится в work каталоге приложения под eclipse/workspace/.metadata. На моей системе полный путь к логу такой: /var/lib/tomcat6/work/Catalina/localhost/nxmc/eclipse/workspace/.metadata/.log

Hi!

Currently no. Goes to feature requests

Best regards,
Victor

Больше похоже на баг. А можно более детальное описание ситуации?

Добрый день! Похоже что часть плагинов по каким-то причинам не стартует. В логах сервера (имеется в виду application server) есть какие-нибудь ошибки?

Язык похоже определяется через браузер. Можно выставить английский принудительно добавив ?lang=en к URL'у.

Nice to hear! This crash was one of the strangest problems I had to debug with NetXMS - different platforms, crashes differently, only one thing in common - MySQL backend...
As for what I've fixed - I add a mutex around calls to mysql_stmt_data_seek and mysql_stmt_fetch. Under some conditions two threads call them on different statements, but same MySQL connection. I was thinking that because I'm using mysql_stmt_store_result to cache statement result locally, they are independent, but seems they are not.

Best regards,
Victor

Everything seems correct. Can you set debug level to 6 and check server log? There should be messages about business service polling.

Best regards,
Victor

Hi!

My console normally uses around 100MB, but my MIB file is much smaller. I agree with you that MIB file can be loaded into memory on first access, not after start. Will change it.

Best regards,
Victor

It is possible to add threshold to status DCI and generate some custom event instead of SYS_NODE_DOWN, and do all processing for this custom event. But status and SYS_NODE_DOWN have one important difference - status also takes current alarms into consideration. So, if there is active critical alarm, status will be 4 (critical), but SYS_NODE_DOWN will not be generated, because node itself is reachable. Starting from upcoming 1.2.12 release, it is also possible to create DCI which will check node down flag. If you put threshold on such DCI and will generate some custom node down event, you'll get exactly what you need. To create such DCI, create new DCI with source "Internal" and parameter name "Dummy", and use the following transformation script:


return ($node->runtimeFlags & 0x04) ? 1 : 0;


This DCI will return 1 if node is down and 0 otherwise.

Best regards,
Victor

Access to real equipment can really help. Can you contact me directly so we can organize it?

NetXMS server uses IP address resolved from host name (or IP address) specified as "primary host name" in node properties. You can see it in overview page as "Primary IP".

Best regards,
Victor

Hi!

All ServiceCheck parameters just connects over TCP to target and do some handshaking. If I understand correctly you need to monitor local processes? Then you can just use Process.Count to check that required processes are running.

Best regards,
Victor

Hi!

You can check that current string value differs from previous value by using "diff" threshold. But this will not work as you need - you won't be able to check what part of string was changed and so identify what service is not running. Better solution here would be instance discovery or tables - but this requires list or table DCI with all services, which is not available either. My recomendation is to wait for 1.2.12 release - I will add Service list and table support to agent and you'll be able to configure what you need without additional workarounds.

Best regards,
Victor

Thanks for nailing it, I'll include fix in next release.

Best regards,
Victor

Hi!

Can you please send me core file (to [email protected])?

Best regards,
Victor