NetXMS Support Forum

Na dannij moment suschestvuet tol'ko vozmoznos' nastroit' neskol'ko NetXMS serverov i peresilat' mezdu nimi sobitija. Obschej centralizovannoj konfiguracii poka net - k kazdomu serveru pridetsja podkljuchatsja otdel'no. Eto obsuzdalos' zdes' (v konce est' instrukcija po nastrojke event forwarding): https://www.netxms.org/forum/index.php/topic,256.0.html

Integracija s Google Maps - horoshaja misl', zapisal v TODO

Best regards,
Victor

Quote from: Anth0ny on January 13, 2009, 04:01:33 PM
это так, мысль на будущее.
кстати.. чем больше смотрю на Шаблоны, тем больше они мне по поведению напоминают Политики. всё таки шаблоны себя несколько иначе должны вести, а тут- вполне такие настоящие Policy.

Pohoze, nachat' nado s opredelenija chto takoe shablon i chto takoe politika

It's a bug Is it critical? If it's really critical, I can make a patch for 0.2.24, if not - please wait for next release.

Best regards,
Victor

Hello!

Below are some possible reasons:
1. Lost database connection.
2. Heavily corrupted database, where some tables for collected data (like idata_1734) does not exist.
3. Clock shift on server - if clock shifted back, server occasionally may try to write collected data with already existing timestamp.

You can try to run failed query in SQL query analyzer - it should give more diagnostic output.

Best regards,
Victor

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

Нельзя - в этом смысл шаблона. Можно вынести DCI Nr. 2 в отдельный шпблон и накладывать его только туда, где он нужен.

Quote from: possamai on January 12, 2009, 12:31:22 PM
Why?

Design flaw I agree that connections from agent to server can be very useful in many situations, especially for hosts with dynamic addresses or behind NAT. It is in my long to-do list, because it requires significant changes on server side, but eventually this feature will be available.


Best regards,
Victor

Удалять нельзяб это будет именно удаление ноды вообще. Надо выбрать шаблон, right click -> Unbind, и выбрать ноду которую хотим вывести.

Hi!

There are description of how to use ServiceCheck.HTTP(): https://www.netxms.org/forum/index.php/topic,28.msg87.html#msg87

Best regards,
Victor

Hello!

Here are translation of mentioned post, should be enough to setup shared resource monitoring.

It's an example of cluster monitoring configuration.

Case:
We have two cluster nodes: NODE_A and NODE_B. Cluster itself is called CLUSTER. Both nodes have NetXMS agents installed. Nodes are connected to public network 192.168.1.0/24, node A has address 192.168.1.11, node B - 192.168.1.12. Also, both nodes has private network 10.0.0.0/8, node A has address 10.0.0.1, node B - 10.0.0.2. There are 3 resource groups:
1. Cluster group, name: ClusterGroup, virtual IP 192.168.1.10
2. Shared disk, name SharedDisk, virtual IP 192.168.1.20. On active node seen as drive X:
3. Exchange server group, name: Exchange, virtual IP 192.168.1.30. On active node run Exchange services and drive E: contains shared Exchange data.


Requirement:
Monitoring service availability and disk space.


Configuration steps:

1. Create object of type "Cluster", call it CLUSTER (it is no necessary to match AD cluster object name)
2. In CLUSTER object properties add cluster interconnect network 10.0.0.0/8
3. In CLUSTER object properties on "Resources" page define resources (name - IP pairs):
    ClusterGroup 192.168.1.10
    SharedDisk 192.168.1.20
    Exchange 192.168.1.30
4. Now we can create nodes A and B. They should be created under CLUSTER object. As Ip addresses for new nodes should be used their fixed IP addressesd (192.168.1.11 and 192.168.1.12 in our example).
5. Check configuration of new nodes - virtual addresses of cluster resources should not appear as interfaces. If you select CLUSTER object in object browser, on "Cluster" page should be displayed correct position and status of cluster resources.
6. Now DCIs for cluster resources can be defined. Select "Data Collection" for CLUSTER object, and create DCIs as usual, except one: you should select correct cluster resource in "Associate with cluster resource" field. Fo example, for monitoring disk space on shared disk X:, you should set "Associate with cluster resource" to "SharedDisk" in our example. DCIs configured that way will be collected only from node which is current owner of associated resource.
7. All other configuration for cluster nodes can be done as usual.


There are also some predefined events related to cluster monitoring:

SYS_CLUSTER_DOWN
SYS_CLUSTER_UP
SYS_CLUSTER_RESOURCE_DOWN
SYS_CLUSTER_RESOURCE_UP
SYS_CLUSTER_RESOURCE_MOVED

You can process them as usual in event processing policy.

Best regards,
Victor

Hello!

Looks like compiler tries to use incorrect _CONTEXT definition from WinNT.h. Such result can occur if you have _M_X64 defined instead of _M_IX86 when compiling StackWalker.cpp. Maybe you have 64bit version of cl.exe first in your path?

Best regards,
Victor

1. Normal'no etogo sdelat' nel'zja. Ja podumaju nad patchem chtobi dobavit' takuju vozmoznost'.

2. V MasterServers nado ukazivat' IP proxy agenta, prichem tot adres, s kotorogo pridet connect. Naprimer, dlja shemi:

server --- (83.153.17.1) [fw + proxy agent] (192.168.1.1) --- (192.168.1.10) [remote agent]

so storoni servera dlja hosta 192.168.1.10 proxy budet vistavlen 83.153.17.1, a v konfige 192.168.1.10 MasterServers budet 192.168.1.1.

Best regards,
Victor

A mozno startanut' server s debug'om urovnja hotja-bi 7 (netxmsd -D 7) i prislat' log?

Sorry, https://www.netxms.org/download/rc/nxagent-0.9.0-rc1-x64.exe

Сразу нет. Но можно централизованно рестартить агентов через actions. Из консоли можно сделать рестарт агента через меню Tools -> Restart Agent, а с командной строки так:

nxaction <agent_address> Agent.Restart


Еще один вариант - использовать возможность агента принимать upgrade package. Можно сделать скрипт, который будет обновлять конфиг, npi файл для него, и сделать deploy как обычному upgrade package'у.