NetXMS Support Forum

Hi,

you may set node ID to 0, then server will find actual node by source IP address.

Best regards,
Victor

Hi all!

NetXMS 2.0-RC2 is out. It is last RC before final 2.0 release. Changes since previous release are following:


- Maintenance mode for nodes, clusters, and mobile devices (manual and scheduled)
- Fixed broken instance discovery filters
- Fixed agent crash when collecting SNMP data in cached mode
- Agent returns correct OS version on Windows 10
- New NXSL "Node" class attribute: bridgeBaseAddress
- One LDAP attribute can be used in multiple mappings
- Fied deadlock on LDAP user deletion while LDAP synchronization
- Add option to use encrypted password in password fileds in configuration files and in the server configuration parameters.
- Added SMS driver for web service text2reach.com
- SNMP sysContact and sysLocation collected and stored
- Server can accept traps and syslog messages from nodes in all zones (controlled by TrapSourcesInAllZones configuration option)
- On instance discovery pool instance name is updated if it has changed
- New SMS driver - slack.com
- IPv6 support in built-in syslog server
- Fixed event processing policy export/import issues
- Global default retention time and polling interval for data collection
- Initial support for scheduled tasks within system
- Scheduled file upload
- Management console:
   - Object context menu available on geo map
   - Filter in event template configurator
   - Web console use client time zone to display time
   - Added option to use server time zone to display time in console
   - Access to event log, SNMP trap log, and syslog from object context menu
   - Dashboards can be associated with other objects (nodes, containers, etc.) and opened from object's context menu
   - Forced DCI polls from summary tables
   - Script hints
- Fixed issues: #786, #831, #841, #852, #864, #878, #883, #890, #891, #892, #896, #897, #898, #900, #902, #903, #905, #907, #910, #913, #917, #919, #921, #928, #933, #937, #943, #945, #947

Best regards,
Victor

Hi,

there are even issue for that (quite old): https://dev.raden.solutions/issues/147. I'll try to make it into 2.0 release.

Best regards,
Victor

Hi,

I recommend to try out 2.0-RC1 (or wait for 2.0-RC2 to come out) - we fix a lot of bugs since 1.2.17 and 2.0 branch is always stable enough.

Best regards,
Victor

Hi!

Could you please try to install this agent: https://www.dropbox.com/s/da2omgyrhja6dtj/RADnxagent.2.0-RC2.sparc.pkg.gz?dl=0?

It is 2.0-RC2 that will be officially released in a few days. I fixed errors in package so it should contain correct libraries now. I recommend to uninstall previous version and make sure that /opt/netxms/lib directory is empty before installing this version.

Best regards,
Victor

Hi,

not yet. But it can be easily implemented, Il registered it as a feature request (https://dev.raden.solutions/issues/941).

Best regards,
Victor

Hi,

most likely something in event processing policy cause slow processing. Can you enable debug level 6 for some time and trace processing of few events? Also, you can try to disable all rules in event processing policy and see if it helps. If it will, try to re-enable them one by one to catch what rule causing delay.

Best regards,
Victor

I've fixed this bug. Fix will be included in 2.0-RC2.

Best regards,
Victor

Hi,

I've made some checks and was unable to detect memory leak when agent cannot connect to database. What Oracle client you are using?

Best regards,
Victor

Hi,

what NetXMS version you are using?

Best regards,
Victor

Hi,

operation and value are ignored for data collection error thresholds.

Best regards,
Victor

Hi,

what version of agent you are running and on what OS? Could you run agent for some time with debug level 6 and send me log file?

Best regards,
Victor

Hi,

in most cases it is hold by mmc.exe because it contains message catalog that is used by event log viewer. Try to ensure that all mmc instances (or any other process that possibly reading event log) are stopped.

Best regards,
Victor

Hi,

try to create database and user for NetXMS using MySQL management tools and in server installer select "use existing database" and specify user and database you created.

Best regards,
Victor

Hi,

for monitoring network service object server just reads ServiceCheck.* parameters from appropriate node, so basically there are no difference in monitoring method, only in result presentation. For SMTP check you should enter valid email address in request field, response is ignored. Checker will try to send email to that address.

Best regards,
Victor