NetXMS Support Forum

There is issue registered for incorrect Hyper-V host detection: https://track.radensolutions.com/issue/NX-1472. Possible reason is that we are using CPUID "hypervisor" bit to detect if agent is running within a VM, and I suppose that Hyper-V host OS is in fact privileged VM, so agent runs inside virtual environment anyway. We will add additional checks in 2.2.8 to report host as physical machine.

Best regards,
Victor

This is download link for both minimal and full installers: https://cloud.netxms.org/index.php/s/yWU2wcC3c4WO2Y6

Best regards,
Victor

Would you like to test build with experimental patch that changes some internal synchronization mechanism?

Best regards,
Victor

Hi,

these tasks created as system tasks, and in 2.2.7 system tasks are hidden by default. You can make them visible in view menu (top right corner of scheduled task list).

Best regards,
Victor

Проще сделать не через condition, а как DCI на каждом узле.

return $1 - time();

идет в trаnsformation script. Тогда значением DCI будет расхождение времени. Затем на закладке "Thresholds" добавляются нужные пороговые значения.

Если делать таким образом, то можно создать шаблон и накладывать его на те узлы, где требуется контроль за расхождением времени. Источником события при такой конфигурации всегда будет узел с проблемой.

I doubt it's Windows bug, more likely just lucky timing. I checked provided process dump - it is deadlocked in a code related to applying templates and sending events. There were execution errors for template auto apply scripts - in that case server generates event - and this event generation from within auto apply code somehow caused deadlock. I will investigate it further. As a workaround I suggest to check auto-apply scripts for possible errors.

Best regards,
Victor

Yes, my mistake - method is correct. Still seems to be a typo in list name: it is "Phonelisa.Processes" in script and "Phonalisa.Processes" in DCI configuration.

Best regards,
Victor

Hi,

you have wrong discovery method - it should be "Script", not "Agent List" if you are using script from script library for discovery.

Best regards,
Victor

Quote from: StanHubble on July 23, 2018, 02:07:02 PM
I created the process dump but it is almost 10GB.  Will this forum accept an upload that big?

I don't think so. I'll send you upload link via PM.

Best regards,
Victor

Я обычно делаю мониторинг разницы с сервером. Можно сделать DCI на параметр System.CurrentTime со скриптом трансформации


return $1 - time();


Он будет возвращать разницу во времени в секундах. Значение приблизительное, но сильное расхождение будет видно. Из практики можно ставить пороговое значение > -2 или < 2 - при нормальной синхронизации оно не сработает, только если расхождение действительно есть.

Hi,

so "show watchdog" actually shows empty list? Can you enter any command in nxadm after that?
Could you please create process dump for netxmsd.exe (using Task Manager) and provide it to us for debug?

Best regards,
Victor

Hi,

it's known issue (https://track.radensolutions.com/issue/NX-1463), not fixed yet. In the meantime you should use Tomcat 8 or Jetty.

Best regards,
Victor

Just added new hook "DiscoveryPoll" - it will be available in 2.2.8.

Best regards,
Victor

Поведение системы действительно изменилось в версии 2.2.5 - до этого configuration poll на unmanaged нодах работал. Я проверил историю изменений - это было исправление для https://track.radensolutions.com/issue/NX-1420 - теперь сервер не пытается коммуницировать с нодами в состоянии unmanaged. Я думаю будет логично добавить в принудительный poll сообщение о невозможности опроса в таком состоянии чтобы исключить странное с точки зрения пользователя поведение системы.

Currently it is only possible if you use "umatched trap" event. You can create event processing rule for that event and use the following script as action to generate new event with necessary data:


if (($event->parameters[1] == '.1.3.6.1.2.1.15.7.2') &&
    ($event->parameters[2] ~= "\\.1\\.3\\.6\\.1\\.2\\.1\\.15\\.3\\.1\\.14\\.([0-9]+\\.[0-9]+\\.[0-9]+\\.[0-9]+)"))
{
   PostEvent($node, "BGP_PEER_DOWN", null, $1);
}


This will generate event BGP_PEER_DOWN (you have to define it) with peer address passed as parameter 1 (you can access it in message text via %1).

Best regards,
Victor