NetXMS Support Forum

I'll try to find what can cause this error. Never seen it before. However, it is not related to the fact that you don't see any nodes in console. If this is a fresh installation, you should either add nodes manually or turn on network discovery (it is turned off by default). Network discovery options can be set in console via Configuration -> Network Discovery menu.

Best regards,
Victor

Also, if it is from deb package, correct path to driver will be /usr/lib/libnxddr_mysql.so.

Best regards,
Victor

It's available on NetXMS download page. But I made an assumption that you was using deb packages. If you was building from source, then you have to run configure with --with-mysql command line option to build MySQL driver.

Best regards,
Victor

Sejchas nikak. Ja dobavlju feature request na dopolnitel'nie tipi dlja kolonok v SNMP tablice.

Na pervij vzgljad vse v konfige vigljadit pravil'no. A mogli bi prislat' sami skripti?

Viktor

How these subnets are connected to each other? Can it be that there is firewall in between which blocks connections between NetXMS server and workstation subnet?

Best regards,
Victor

Hi!

Is netxms-server-mysql package installed? If yes, what is output of


ldd /usr/local/lib/libnxddr_mysql.so


?

Also, we will build Debian packages for version 1.2.0 in few days.

Best regards,
Victor

Hello all!

NetXMS version 1.2.0 is released! Changes since version 1.1.10:

- Number of polls required for status change can be set individually for each interface
- New NXSL functions and object properties for accessing topology information
- New NXSL function FindObject
- New NXSL functions for object creation and binding
- Added option to set native agent port on node creation
- Added support for INFORM messages in SNMP trap receiver
- Implemented automatic creation of ChildStatus DCI when Network Service object created for Node
- Implemented concept of "expected" interface state
- Added option to use DNS names instead of IP addresses as primary host name for discovered nodes
- Added possibility to add parameters and/or specify entry point in scripts called via %[] macro
- Implemented alarm comments
- Initial support for multi-valued (tabular) DCI
- Java console:
   - Added alarm history log viewer
   - Time interval for line charts on dashboards made configurable
   - Dashboard configuration improved; all dashboard elements now can be configured from GUI
   - New tab for container objectss where threshold violations for underlying nodes are shown
   - Multiple dashboards can be displayed in a loop (like slide show)
   - Fixed problems with line chart configuration saving in perspective
   - Resolved issue: Reports not working on Windows
   - Resolved issue: Cannot delete non-existent object from event processing policy
   - Resolved issue: No confirmation shown for object tools with "confirm before execution" flag
   - Resolved issue: EPP editor do not support 'Negate cell'
- Web UI:
   - All functionality from Java console implemented
   - Windows installer for web interface
   - Resolved issue: NetXMS session not closed when web session is expired
- Resolved issue: Internal libexpat failed to compile on debian5
- Resolved issue: Build failed on Solaris 11
- Resolved issue: Incorrect interface status reported by agent on FreeBSD
- Resolved issue: Database upgrade problems if SQLite used as backend database

Best regards,
Victor

Hi!

Good idea. I have added it as new feature for release 1.2.2.

Best regards,
Victor

Hi!

Active discovery means that system will ping each address in given subnet(s) and add each which responds (if node passes discovery filters).

Best regards,
Victor

Looks like bug in agent to me. Can you please post here or send to [email protected] your log file?

Best regards,
Victor

Hi!

We are in process of building version 1.2.0. It will be available later today.

Best regards,
Victor

Hi!

Currently it's not possible. I'll add this as feature request for 1.2.1 version.

Best regards,
Victor

Hi!

In 1.1.x version, all Disk.* parameters was renamed to FileSystem.* parameters. Agent still understand old names, so you can use old templates for example, but they are not shown in the list of supported parameters anymore. If adding new DCI, just use appropriate FileSystem.* parameters.

Best regards,
Victor

Hi!

Server sends notification to client when new event created. Client must be subscribed to event notifications. Simple code for receive event notifications can looks like this:



// subscribe
session.subscribe(CHANNEL_EVENTS);

// add notification handler
session.addListener(new SessionListener() {
@Override
public void notificationHandler(final SessionNotification n)
{
if (n.getCode() == NXCNotification.NEW_EVENTLOG_RECORD)
{
Event e = (Event)n.getObject();
// do what you need with event object
}
}
});


Remember that notification handler called in background communication thread and should not perform any long-running tasks.

Best regards,
Victor