NetXMS Support Forum

Quote from: jeffreyz on March 23, 2014, 08:15:13 PM
I upgraded from 1.2.12 to 1.2.13 and now I cannot start the server because the server cannot log into the database.  Here is the output from the server log file (DebugLevel = 9):

1. Try to change "localhost" to "127.0.0.1"
2. Please show your pg_hba.conf

Encryption is used by default, however it's a subject to supported ciphers and negotiation during initial handshake — with plain text fallback. To ensure that network traffic is always encrypted (or connection is rejected), add "RequireEncryption=yes" to nxagentd.conf.

Починил, http://git.netxms.org/netxms-snapshot-develop.tar.gz теперь тоже работает.

Но если у вас нет необходимости использовать именно снапшот — я советую использовать git напрямую: git clone https://git.netxms.org/public/netxms.git

Спасибо, я проверю.

Попробуйте пока вот этот снапшот: http://git.netxms.org/public/netxms.git/snapshot/HEAD.tar.gz?js=1

Только что проверил версию 1.2.12 — есть опция "-a". Какую сборку вы используете?

По логину — agent shared secret использует логин "netxms" для обфускации, "-a" сделано для удобства: AirAlk:nxencpasswd(develop) $ ./nxencpasswd -a test1
nyQyxaEwZRbCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=
AirAlk:nxencpasswd(develop) $ ./nxencpasswd netxms test1
nyQyxaEwZRbCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=

Добавим, спасибо за репорт.

Мы используем flex и bison.

Точно работающие версии:AirAlk:~() $ flex -V
flex 2.5.35 Apple(flex-31)
AirAlk:~() $ bison -V
bison (GNU Bison) 2.3
Written by Robert Corbett and Richard Stallman.

Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

alk@debian6 in ~
$ flex -V
flex 2.5.35
alk@debian6 in ~
$ bison -V
bison (GNU Bison) 2.4.1


Use "host:port" in login dialog

А что именно нужно мониторить?

Without agent server can check server presence on the network using ICMP ping or using SNMP (if available).
If that's sufficient (e.g. you don't need CPU or memory metrics from these servers) — you do not need to install agent.

Seems fine. Make sure you have "LogFailedSQLQueries=yes" in netxmsd.conf (it's enabled by default) and check log file for failed queries.

Выложил ipk: https://www.netxms.org/download/ar71xx/, проверьте пожалуйста.

Выложил ipk: https://www.netxms.org/download/ar71xx/, проверьте пожалуйста.

It should save in both cases. All data is saved into DB by separate thread (so server can collect and process data) — check value of "Database writer's ..." DCIs on the server node, if it's too high — your DB can' handle load.

Hello.

No, you need to restore DB from backup.

It's generated internally, when server can't reach node via any allowed channel (ICMP, Agent, SNMP)

Easiest way is to have a rule in a event processing policy which silently ignores SYS_NODE_DOWN during off-hours.
Check attached screenshot for sample configuration.

Please note that this EPP is processed from top to bottom and by default all rules are processed (unlike "first-match-win" in thresholds), so this rule should be above any other SYS_NODE_DOWN related rules.

Description of "TIME" structure (returned by localtime()): http://wiki.netxms.org/wiki/NXSL:TIME

Update: script should be like "if (now->hour >= 20 || now->hour <= 8) ..."

Quote from: Dani@M3T on January 27, 2014, 01:48:55 PM
For me the question is, what triggers the SYS_NODE_DOWN event. The default DCI 'status' has no threshold configured.