NetXMS Support Forum

There was no changes connected with beacon between this versions.

What is result of resolving DNS google.com from NetXMS server computer? Host may be not accepted if its IP is a wildcard address or a loopback address or a multicast address or a broadcast address or a link local address or if NetXMS server failed to resolve DNS.

Events that are generated: SYS_NETWORK_CONN_LOST and SYS_NETWORK_CONN_RESTORED.

There is screenshot of NetXMS configuration and netxms log.

Everything works for me with latest server(from development branch):
[25-Jun-2016 17:37:04.267] [DEBUG] Beacon host 195.13.231.157 added
[25-Jun-2016 17:37:04.267] [DEBUG] Beacon host 8.8.8.8 added
[25-Jun-2016 17:37:04.267] [DEBUG] Beacon poller thread started

Host configuration: "google.com,8.8.8.8"

What version do you use? May it happen that there were some DNS problems?

Can you specify which field or fields are not updated.

OS names can be checked in "Object Details" view on "Overview" tab. It is shown like "Platform Name". For filtering can be used Java regexp.

I found problem. It's bad class declaration. You want function "public ColumnFilter(int type, long value)" to be used, but both values are counted like long and class is created like: "public ColumnFilter(long rangeFrom, long rangeTo)". So your values were counted like a range. Type should be change to Enum type. I have created bug on it: https://dev.raden.solutions/issues/1245.
Temporary solution:
import java.lang.Integer
eventLog = session.openServerLog("EventLog")

columnFilter = ColumnFilter(java.lang.Integer(ColumnFilter.EQUALS),363)
logFilter = LogFilter()
logFilter.setColumnFilter("event_id",columnFilter)
...

There is server configuration parameter that defines what to do with events of deleted object: "DeleteEventsOfDeletedObject". By default it is 1(delete them). In case if it is set to 0, then events are not deleted, but you can't find them by node name(as this node is already deleted). You can find them by object id of deleted object. As event source will be displayed object id in square braces(like this: "[100]").

Please check DeleteEventsOfDeletedObject server configuration parameter.

The name is "event_source". UI is hiding column real names. You should use names that are defined in database.

Optimal log level for debugging problems is 6.

Check "LogFile" parameter in server config(NETXMSHOME/etc/netxmsd.conf or /etc/netxmsd.conf). If it is not defined try to check something like /var/log/netxmsd.

Check your server log on debug level 4. There should be something like: "LOG QUERY: %s"

There are names: "AlarmLog", "AuditLog", "EventLog", "SnmpTrapLog", "syslog".
final Log handle = session.openServerLog("EventLog");

If you need exactly summary e-mails, then it can be good solution. Other solutions is to generate alarms and check alarms in the morning.

Чтобы в лог писались сообщения "Connection from 10.5.0.112 rejected" DebugLevel должен быть 5 или выше. А у вас он 0: "Debug level set to 0". Уровень дебага можно выставить при запуске демона параметром -D5(уровень дебага)  или параметром в конфиге: DebugLevel=5

Проверять следующее:
- Сервер не может подключиться к агенту(данные о фозможностях агента сервер получает во время Configuration poll)

Проверить:
- Агент запущен
- У агента в конфиге прописан IP сервера
- Проверить лог агента на строчки вроде: "Connection from 10.5.0.112 rejected"
- Проверить Firewall

To check versions you can run excutables with "-v" option: "netxmsd -v" and "nxagentd -v" it will return the version. "nxdbmgr upgrade" will aknowlage if there were some errors while upgrade and netxmsd just will not start if database upgrade failed.