NetXMS Support Forum

Thanks for report, I'll check this issue.

Looks like agent is rejecting connections.

Check "Servers", "InstallationServers", "ControlServers", or "MasterServers" section in nxagentd.conf, one of this sections should contain IP address of your netxms server. For more information take a look at nxagentd.conf-dist

If nxagentd.conf is correct, verify that you can connect from your windows machine to linux server on port 4700 — if you can't, check firewall settings.

If both are correct, you can stop agent and start it with "-D" argument, this will enable debug output.

Try this:
LDFLAGS=-lm ./configure  --with-server --with-mysql --with-agent

Можно попробовать использовать какой-либо програмный коммутатор для порта. Я знаю про Xport, наверняка есть и другие варианты.

Дубовое решение:

@echo off

set server=%1
set target=%2

nslookup %target% %server% 2>&1 | find /i "can't find %target%:" >nul: && echo 1 || echo 0
[code]

принимает два параметра, dns server и hostname для проверки.[/code]

Thanks for report, patch attached to this message.

To apply:

cd netxms-0.2.26/src/agent/subagents/freebsd
patch -p0 < /some/where/system.diff

Ага, замечательно. Будем смотреть.

Quote from: Akira on May 17, 2009, 04:45:20 PM
Проблему локализовал косвенно.

Очень интересный креш, деление на ноль в глубине WinSock (при том, что в socket() сложно передать некорректные данные):

[WS2HELP:71BF17F4]: WahInsertHandleContext
  [mswsock:71B24A16]: (function-name not available)
  [mswsock:71B24608]: (function-name not available)
  [WS2_32:71C03FD5]: WSASocketW
  [WS2_32:71C0416E]: socket
...

А за железом, на котором сервер работает, никаких странностей не наблюдалось?

Quote from: Akira on May 10, 2009, 06:25:49 AM
У меня и на 2.25 и на 2.26 сервис падает каждые 2-5 часов.

А была ли версия, которая не падала?
Если да — я попробую поймать проблему, просмотрев изменениях между версиями.

Quote from: testos on May 12, 2009, 12:53:46 PM
Any news about this?. Some information was certainly valuable.

Looks like we are out of luck on this, DB files are completely messed up (we lost most of the files open for writing after file system was screwed up in memory — and unfortunately, in case of forum it was messages table).

However, we learned our lesson and will copy significant answers to documentation draft (as well as already double-checked backup safety and integrity).

Встроенного нету, можно сделать через внешний скрипт.

Например так:
@echo off

set ret=0
dir %1: 2>NUL >NUL
IF ERRORLEVEL 1 SET ret=1

echo %ret%

Если диск есть — вернет 0, нету — 0.

В nxagentd.conf добавить примерно такое:
ExternalParameter = CheckDiskExist(*):c:\check.cmd $1

После этого можно мониторить параметр CheckDiskExist(G)

Hello.

Please check your mail now.

Hello.

Sorry for delayed answer, I'll check records and answer you today.

Hello.

Recently, we experienced severe server crash (file system was messed up — exact case when hardware redundancy do not work), now it's reinstalled and restored — partially. Unfortunately, in a process of restore we found issues with latest database backup, therefore forum and bugtracker data are partially lost. However, we are working on recovering rest of the data (mostly forum)

Current situation is:

• Bugtracker — all issues are available, user registrations lost
• Forum — restored from backup dated 07 Feb 2009; messages are lost after this date, user registrations are intact

wbr, alex.

Download page

*
* 0.2.26
*

- Fixed compilation problems on some UNIX platforms
- Fixed incorrect behaviour of Disk.Free parameter on some Windows systems
- Fixed broken Windows 2000 support (issue #248)


*
* 0.2.25
*

- Implemented automatic template application based on filters
- Implemented automatic node binding to containers based on filters
- Implemented database export and import
- Database checking tool (nxdbmgr) improved
- More standard parameters inplemented in Linux, FreeBSD, and Solaris subagents
- Removed inconsistencies in some parameters' behavior on different platforms
- DCI transformation scripts now can be tested from console
- Network maps improved
- Added support for matching Windows event log records by event source,
  severity, and event code
- Fixed issues: #197, #217, #239, #240, #241, #242, #243, #244, #245

в control panel -> server settings указать smtp server
в control panel -> actions добавить "send email"
в control panel -> event processing policy добавить в конец правило для нужных событий и указать ему action из второго шага.

Больше про обработку событий - https://www.netxms.org/documentation/netxms_user_manual.pdf , глава 6.