NetXMS Support Forum

Hello!

It's a bug in database initialization script. You can download fixed one at https://www.netxms.org/download/patches/003/dbinit_sqlite.sql and replace existing one in <install_dir>\lib\sql. Then, run nxconfig.exe to complete server's configuration.

We will also release fixed version shortly.

Best regards,
Victor

Hello!

I see only one solution - to use push DCI. You can define DCIs on web server's node object, set their source to "Push Agent", and then on management server (or any other machine) run your custom checks by cron and use nxpush command line utility to push new values to DCIs on web server's node object.

I also have a plans to implement "internal push" operation which will allow automatic copy of values from one DCI to another, but for current release the only way is through nxpush utility.

Best regards,
Victor

Hi!

Yes, content of config.log will be very helpful.

Best regards,
Victor

Hello!

It's a bug in FreeBSD subagent. Try to do the following: add the following lines to the end of src/agent/subagents/freebsd/freebsd.cpp:

extern "C" BOOL __NxSubAgentGetIfList(NETXMS_VALUES_LIST *pValue)
{
  return H_NetIfList("Net.InterfaceList", NULL, pValue) == SYSINFO_RC_SUCCESS;
}
extern "C" BOOL __NxSubAgentGetArpCache(NETXMS_VALUES_LIST *pValue)
{
  return H_NetArpCache("Net.ArpCache", NULL, pValue) == SYSINFO_RC_SUCCESS;
}

(it's a missing entry points caused message Cannot loads platform subagent "/usr/local/netxms/lib/libnsm_freebsd.so": Subagent doesn't provide any usable parameters) and recompile the agent. This should help.

Best regards,
Victor

Hello!

It's not possible now. But idea is very good, so I definitely will implement it.

Best regards,
Victor

Hello all!

NetXMS 0.2.17 is out. Changes from previous version:

- Implemented alarm timeouts
- ODBCQUERY subagent improved
- Web interface improved
- Object browser in Windows console improved
- Fixed issues: #122, #128, #130, #136, #138, #141, #156, #157, #158,
                #159, #161, #162

Best regards,
Victor

Hello!

I've never try to do anything with Windows Internal Database, but as far as I understand, it's just a variant of MSDE - so it may be possible to run NetXMS on it using SQL server driver (or via ODBC). You have to try.

Best regards,
Victor

Hello!

Looks like your MIB file refers to another MIB file which you don't include in your compilation. Look at the IMPORTS section in your MIB file - it should contain something like

IMPORTS
  .. some text ...
  BITS
  .. some text ..
  FROM another_mib_module

Try to find this additional module and include it in compilation. You can also post your MIB file here, then I'll take a look at it.

Best regards,
Victor

Hello!

It's not implemented yet, property page for object image is just a stub. It's already in our issue tracker, and I hope that I will have time to implement it in near releases.

Best regards,
Victor

Hello!

Most likely you have an old version of flex. You have to use version 2.5.33.

Best regards,
Victor

Hello all!

Finally, after long delay, version 0.2.16 is released! Changes from previous version are:

- Implemented user authentification by certificates
- Management packs fully functional - templates, events, and SNMP traps
  can be exported and imported
- Cluster monitoring improved
- Node names resolution working
- Implemented OCI based driver for Oracle database
- UPS subagent: added support for Microdowell devices
- Windows console:
  - Added layer 2 topology view for compatible switches
  - Object search improved
  - Graphs improved:
    - Area graphs
    - Predefined graphs
    - Minor UI improvements
  - Added possibility to manage/unmanage set of child objects
  - Added possibility to hide unmanaged leaf objects
  - Container objects can be placed above all others
  - Other small UI improvements
- Fixed issues: #90, #106, #120, #143, #147, #148, #149, #150, #152, #153, #155

I plan that next version will be focused on bugfixing and minor improvements and that it will be released in a month or so.

Best regards,
Victor

Hello!

Currently, you have only one way: define two DCIs for each port, and configure threshold for each DCI. Of course, it can be very time consuming for large number of ports. In one of the next versions (0.2.16 or 0.2.17, depending on my free time) we plan to implement "table" DCIs which will allow you to define parameters which differs only in instance only once, and system will automatically generate actual DCIs for each parameter's instance (for each port in your case).

Best regards,
Victor

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