NetXMS Support Forum

Some information on internals is available in user manual, check following pages:
http://wiki.netxms.org/wiki/UM:Basic_Concepts
http://wiki.netxms.org/wiki/UM:Data_Collection
http://wiki.netxms.org/wiki/UM:Event_Processing

Check "/tmp/nxagentupdate.log" for more details

It's build around Jython which is 2.5.4 right now (not CPython, which is 3.3.0 right now), 2.7 is in beta stage.
I've did couple of quick tests with 2.7-beta1 version and it seems to work fine. You can try this jar: https://netxms.org/nxshell-1.2.5_jython27.jar.

Just realized – you running "netxmsd", but topic is about agent.

netxmsd - server binary
nxagentd - agent binary

There should be much more output with debug (-D) enabled, please post complete output and attach configuration files.

Download https://www.netxms.org/download/nxmc/nxmc-1.2.5-linux-gtk-x86.tar.gz
Unpack it: tar zxf nxmc-1.2.5-linux-gtk-x86.tar.gz
Run nxmc/nxmc

We will probably change this feature.
Right now WebUI tries to get image at http://127.0.0.1/, port 80 - regardless the application server port.
You can either drop file into existing web server root if you are running one, or setup reverse proxy and keep file in application server's ROOT.

Sure. I've put sample script here: http://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations#List_free.28administratively_down.29_ethernet_ports_on_switches

Quote from: yshiro on February 12, 2013, 12:50:26 PM
It´s possible to make the same question, with scripting ?

I´m trying to make an script, for free ports on my switches.

Check that you have "LogFile" parameter in file /etc/netxmsd.conf

Сейчас нет явной привязки контактов к юзеру, каждый номер/мейл создается как отдельный Action, который потом можно использовать в Event Processing Policy.

EPP обрабатывается целиком (если не отработает правило с условием "stop processing"), что позволяет делать достаточно гибкую систему нотификаций, от более общих (e.g. "все NODE_DOWN" уходят админу"), к детальным правилам ("NODE_DOWN для конкретных серверов уходят еще кому-то).

Сейчас обычный подход - создавать EPP вида:
Souce: Node1, Node2, Node3
Events: SYS_NODE_DOWN, SYS_NODE_UP, etc.
Action: SMSToUser1, SMSToUser2

Можно сделать более сложную схему с одним Action, и использовать макрос %[script_name] – вызывая скрипт из Sctipt Library, который на основе какой-то своей логики вернет контакты (например вычитывая Custom Attributes у ноды), но это уже больше костыль (хотя я такое использую у клиента, где много контактов отвечающих за один-два банкомата, для них даже нет юзеров в системе мониторинга).


У нас в есть в планах добавить в профиль юзера каналы оповещения (email, sms, xmpp, etc.) – но сейчас это не сделано.
Идея с указанием "responsible person" для сервера / контейнера мне нравится, зарегистрировал ее как feature request (#235)

Try to remove ~/.fontconfig (or just rename it for testing)

See also: https://bugzilla.redhat.com/show_bug.cgi?id=532718
http://lists.freedesktop.org/archives/fontconfig/2009-June/003168.html

Not right now. You can only disable it in the code and then rebuild server.
diff --git a/src/server/core/interface.cpp b/src/server/core/interface.cpp
index 0436baa..6f95b42 100644
--- a/src/server/core/interface.cpp
+++ b/src/server/core/interface.cpp
@@ -504,6 +504,7 @@ void Interface::StatusPoll(ClientSession *pSession, DWORD dwRqId,   Queue *pEventQ
                        break;
        }

+  /*
        // Check 802.1x state
        if ((pNode->getFlags() & NF_IS_8021X) && isPhysicalPort())
        {
@@ -512,6 +513,7 @@ void Interface::StatusPoll(ClientSession *pSession, DWORD dwRqId,   Queue *pEventQ
                if ((m_dot1xPaeAuthState == PAE_STATE_FORCE_UNAUTH) && (newStatus < STATUS_MAJOR))
                        newStatus = STATUS_MAJOR;
        }
+  */

        // Reset status to unknown if node has known network connectivity problems
        if ((newStatus == STATUS_CRITICAL) && (pNode->getRuntimeFlags() & NDF_NETWORK_PATH_PROBLEM))


Unfortunately, there nothing related to your issue in this log.
Could you please change 1Gb limit to 2Gb in the script and rerun it?

Quote from: millerpaint on February 07, 2013, 06:57:38 PM
OK, good news Alex.  The script you provided shut down NetXMS gracefully after it reached the 1GB of RAM threshold.  It took 12-15 minutes running under valgrind before it crashed.  I have attached the valgrind log.

Пример настройки: http://wiki.netxms.org/wiki/How_to_send_e-mail_notification_when_disk_space_is_low
Список макросов, которые можно использовать: http://wiki.netxms.org/wiki/UM:Event_Processing#Macros_for_Event_Processing

Quote from: testos on February 07, 2013, 12:51:25 PM
Centos kernel is not supposed to panic under any circumstance.

That's pretty much standard trace issued by oomkiller.

Kevin: try to use attached script to get proper valgrind output. Script idea is that it monitors RSS used by netxmsd, and if it's greater than 1Gb, script try to do graceful shutdown using nxadm – before netxmsd is killed by OOMKiller.
You need to change NXADM variable in the script according to your installation prefix.
Start script, then start netxmsd under valgrind.

Yes, there should be no output with '-d', it's daemon mode - it should silently detach and go to background.
Before running it as daemon, you can check that config files are good and agent is working properly by running it with '-D3' (3 - debug level, can be from 0 to 9)