NetXMS Support Forum

Очень интересный креш, деление на ноль в глубине 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.

127 is mostly "command not found", check paths inside of /etc/init.d/netxms script

You can copy database (dump / restore) to a new host, it should work just fine.

Hello all!

NetXMS version 0.2.24 is released.

Changes from previous release:

- Broken DB Schema fixed

Version 0.2.23 removed from downloads.

Short answer - yes, you can.

NetXMS gathers data in multiple ways:

• Common ways - initiated by server (NetXMS agent build-in checks, SNMP, WMI, etc.)
• External application can push data (and events) into NetXMS from external source using nxpush / nxevent tools. We use for integration with HP ServiceDesk, for example
• "External Parameter" can be defined for NetXMS agent. Basically, it just an application / script which output some value. This method commonly used for parameters not provided by core agent and subagents.

Solution depends on integration level you want to achieve.
If you need only events in NetXMS (e.g. "Out of disk space", "Node Down", etc.) - you can setup Nagios to execute nxevent when something happens to push event into NetXMS. This can be done with little effort.

If you want to have not only events but data too (e.g. amount of free space for every minute), you can use two ways:

• Use nxpush and execute it periodically by Nagios / cron.
• Create script(s) which extract data from Nagius and configure agent to run this script as "external parameter"

This should work, but I should warn you that this way can require a lot of effort to make it work (depends on the size of your network). If you want to see all collected in NetXMS - I'd suggest to install our agent on each node.

На даный момент - внешними скриптами.  Я бы сделал простенькую обвязку вокруг dig.

Hello.

No, NetXMS server doest not provide such functionality (at least now). However, it can probable be done using standalone snmp server and some scripts for passing data between netxms and snmp servers. I never tryed it myself, but I'm pretty sure it can be done quite easily.

Yes, you can use external application / script:

Sample from nxagentd.conf:

Quote#
# ExternalParameter
#
# Add parameter handled by external command. To add multiple parameters, you
# should use multiple ExternalParameter entries. Please note that on Windows
# agent uses system process execution API for execution of specified
# command, so you cannot use pipes or shell commands. If you need to
# execute command via shell, use ExternalParameterShellExec instead.
#
# Syntax:
# ExternalParameter = <parameter_name>:<command_line>
# If you specify parameter name as "name(*)", then you can use $1 .. $9 in
# command line to substitute actual arguments passed from server.
#
# Examples:
# ExternalParameter = Test:echo test
# ExternalParameter = LineCount(*):cat $1 | wc -l
# ExternalParameter = Test2(*):myprog $1 $2

Also you can use nxpush/nxevent to push data to the monitoring server directly from your application.