NetXMS Support Forum

Hello!

By default, NetXMS server will run active discovery every 2 hours, and passive discovery polls every 15 minutes. You can change this by changing appropriate server parameters: ActiveDiscoveryInterval and DiscoveryPollingInterval (both in seconds). Also, if you have large subnet with a lot of unused addresses, it can take significant amount of time to scan it using active discovery: because for each unused address server will wait for a response until timeout expires, and because timeout is ~6 seconds, if you have /24 subnet with most addresses unused, it will take ~20 minutes to scan them. Firewall between NetXMS server and scanned subnet may also affect discovery time (for example, if firewall blocks TCP connections to port 4700 which NetXMS server will check to determine if agent is running on the host).

Best regards,
Victor

Hello!

I've never seen such error messages, but I'm still using version 167. Also, I recompile Scintilla from source before using it.

Best regards,
Victor

Hello!

Oops, I forgot to add it to the CVS. It will be fixed in next release. For now, you can download it from https://netxms.org/download/patches/002.

Best regards,
Victor

Hello!

The main problem is that PostgreSQL database driver was not linked correctly. This is already known bug, which will be fixed in 0.2.16. For now, you can use workaround described here:

https://www.netxms.org/cgi-bin/mwf/topic_show.pl?tid=29;sid=b7dca035f7436b0605f5ff0d9de0937b

Best regards,
Victor

Hello!

The problem is that libtool cannot find command g++ - which is GNU C++ compiler. Looks like you don't have installed C++ compiler package or it is not in the search path.

Best regards,
Victor

Hello!

It's an error in configure script (reference to libpq missing in libnxddr_pgsql.so because of incorrect link options), I'll fix it in the next release. For now you can use the following workaround:

In the file src/server/dbdrv/pgsql/Makefile find line starting with LDFLAGS = and append -lpq to it. You should get something like this:

LDFLAGS =  -L/usr/local/lib -lpthread -lpq

Then run make clean ; make ; make install in src/server/dbdrv/pgsql directory. This should create correct libnxddr_pgsql.so.

Hope this helps!

Best regards,
Victor

Hello again!

Please note that starting from version 0.2.15, you can also calculate checksum of web pages - this gives you an ability to detect page changes. To get web page checksum, you should load ECS (Extended Checksum) subagent on the node from which you wish to control web page, and then add DCI like below to that node:

ECS.HttpSHA1(URL)

for example, to calculate checksum of www.netxms.org main page, use

ECS.HttpSHA1(https://www.netxms.org)

You will get SHA1 hash for page as a string. You can set threshold on DCI to detect changes in a checksum and process raised events.

Best regards,
Victor

Hello!

To monitor web services, you have two options, depending on your installation:

First option - if you have added machine hosting web server in question to NetXMS as node object.

1) Create "Service" object under your web server's node object
2) Select service type "HTTP"
3) As a request, enter HOST_HEADER:REQUEST_URI, for example, to test URL https://www.netxms.org/index.html enter www.netxms.org:/index.html
4) In a response field, enter regular expression to match server's answer. Below are some examples:
4.1) Just test for code 200 (OK):

^HTTP/1\.[01] 200.*

4.2) To test that server returns code 200 and that page's content has word "netxms":

^HTTP/1\.[01] 200.*netxms.*

Second option - if you don't enter your web server as a node into NetXMS (for example, you wish to check www.ibm.com without creating a node object in your NetXMS database)

1) For the node object representing your NetXMS server, add the following DCI (source - NetXMS agent):

ServiceCheck.HTTP(server_ip_address,port,uri,host_header,response)

For example, to check https://www.netxms.org/index.html just to code 200, use

ServiceCheck.HTTP(159.148.208.90,80,/index.html,www.netxms.org,"^HTTP/1\.[01] 200.*")

This parameter will return the following values:

0 - success (server was connected and return expected response)
1 - invalid arguments was passed (most likely regular expression has incorrect syntax)
2 - cannot connect to server
3 - bad server's response

So you can set threshold for non-zero values and process it.

Please node that you need portchecker subagent to be loaded on machine running NetXMS server. On Windows installation this is default, but on UNIX you should ensure that you have something like

SubAgent = /usr/local/lib/libnsm_portCheck.so

in your agent's configuration file.

Hope this helps!

Best regards,
Victor

Hello!

Yes, there are plans for such compound DCIs - most likely I will implement it in one of the nearest releases.

Best regards,
Victor

Good that you found a workaround In case you'll need it, you can get a patch to the server. With this patch, configuration poll initiated from console will reset "unreachable" flag and recheck node capabilities, as "Change IP address" do. To apply the patch, just replace two files:

src/server/include/nms_objects.h
src/server/core/session.cpp

with files from

https://www.netxms.org/download/patches/001/

and recompile server.

Best regards,
Victor

Hello!

It's a misleading field "Proxy" in node creation dialog - it only sets agent proxy. Node object has two different properties - agent proxy and SNMP proxy, and SNMP proxy can be set only after node object creation in object's properties (my mistake, will correct it in next release). Now, you have to set "SNMP proxy" attribute in node's D properties correctly and try to re-poll it. If system will reject configuration polls because node is down (another problem which needs to be solved) you will have to restart the NetXMS server. This should clear "node unreachable" flag and allow you to do a configuration poll. If this will not help, I'll send you a patch for server that will fix this problem with configuration poll. Are you running NetXMS server on Windows or UNIX (so do you need updated Windows installation or updated source code)?

Best regards,
Victor

Hello all!

Version 0.2.15 is out. Changes from previous release:

- Added initial support for cluster monitoring
- Added preliminary support for management packs
- Added SNMP proxy functionality to agent
- IPSO agent improved
- Added Extended Checksum subagent
- Added ODBC Query subagent
- New agent parameters: Process.CountEx(), File.Time.Access(),
  File.Time.Change(), and File.Time.Modify()
- Parameters File.Size() and File.Count() improved
- Parameters Process.XXX improved
- NXSL improved: implemented switch ... case statement and break statement
- Windows console:
  - Now able to download and install update from web server pointed
    by NetXMS management server
  - Object browser improved
  - Graphs improved: implemented printing and "copy to clipboard"
    function
  - Added server history in login dialog
  - Added option "hide empty values" in last DCI values view
- Fixed issues: #105, #123, #131, #135, #140, #142, #145

There are many bugs still open in bugtracker, and some features requires enchancements, so I hope that we will release 0.2.16 with fixes/small improvements shortly (not after 2 month as for last few versions).

Best regards,
Victor

Hello!

Just implemented SNMP proxy functionality, so you will find it in 0.2.15

Best regards,
Victor

Very strange... Another option left - setup connetion to MS SQL via ODBC. To do this, follow these steps:

1. Create appropriate data source via Administartive Tools -> Data Sources (ODBC). You must create System DSN. Call this DSN NETXMS.
2. Change netxmsd.conf file:

DBDriver = odbc.ddr
DBServer = NETXMS

Note that DBServer now is the name of ODBC DSN.

After that, try to run nxdbmgr init again.

Also, what database rights assigned to the database user you are using?

Best regards,
Victor

Hello,

I think that problem is that you use an account with Windows authentication. Now you have two ways - create an account with SQL authentication (it's an easier way), or configure NetXMS for Windows authentication.

If you decide way 1:

1. Create new standard SQL account, let's say netxms_user, set it's authentication mode to SQL authentication, and set it's password (for example, NetXMSPass).
2. Modify your netxmsd.conf accordingly:

DBLogin = netxms_user
DBPassword = NetXMSPass

3. Run nxdbmgr init again, and ensure that tables was created (you should have ~50 tables).

NetXMS server should start.

If you decide way 2:

1. Change netxmsd.conf:

DBLogin = *

2. Change settings for "NetXMS Core" service - by default, it is running as "Local System" account, you should change it to your domain account which have access to SQL database (in service properties on "Log On" tab).
3. Run nxdbmgr init again, and ensure that tables was created (you should have ~50 tables). Please note that because of Windows authentication, account you will be logged in at the time you will run nxdbmgr should also have access to SQL database.

Hope this helps!

Best regards,
Victor