News:

We really need your input in this questionnaire

Main Menu

NetXMS 2.0-RC1 released

Started by Victor Kirhenshtein, August 08, 2015, 10:30:11 PM

Previous topic - Next topic

Victor Kirhenshtein

Hi all!

NetXMS 2.0-RC1 is out! Changes since previous release:

- Fixed LDAP authentication issues with Active Directory
- Fixed character encoding issues in LDAP user data
- Java subagent improved
- Fixed multiple issues with agent side data caching
- Hash maps implemented in NXSL
- Improved array implementation in NXSL
- New NXSL function ArrayToString
- New OS parameters and tables: System.HandleCount, System.OpenFiles, Process.Handles
- Unified macros in all types of object tools
- Server can be switched to case-insensitive login names mode
- Implemented support of "command generates output" option for server commands
- Network device driver for TelcoBridges gateways
- Fixed memory leak in Qtech OLT driver
- Java subagent plugin for Ubiquity/LigoWave device monitoring
- Management console:
   - Default object display mode can be set in map properties
   - Map drill-down can be enabled in dashboard map elements
   - Input fields in object tools
   - Improved script editor for script library
   - Interface speed displayed in interface object details and in "Interfaces" tab
   - Symbolic name of interface type displayed when known
- Fixed issues: #38, #55, #741, #818, #829, #830, #836, #838, #840, #843, #844, #845, #846, #848, #850, #853, #855, #856, #857, #862, #866

Best regards,
Victor

multix

#1
I was waiting this version for nearly 2 weeks.  First of all, I want to say "thank you"  :)

Is there any problem with
return %(true, $1, stringvariable_for_instance-name); command line ?
I have an instance discovery script, and it was working good in prior versions. But now, It is not doing instance discovering. I tried to debug with trace commands, and saw that everything is ok except this line.

Script returns true but instance discovery is not adding necessary DCIs

In network maps, there was a problem when network map imported to a dashboard (about show objects as icons). Now, There is a problem with network maps, too. When I open network map, property is settled to show objects as status icons, but objects are shown as their images. I am changing to show objects as icons, it is ok. but when I close and re open, it is same again ( showing as images)

multix

I solved network map section.

Network map must be closed before any change made in network map preferences. If I do so, it is ok.

brettmilfos

Hi,

Thanks for the new release looks good.

I have encountered one issue. While upgrading from 2.0M5 all the mibs from var/mibs dis-appeared. This is on win2k8r2.

Restored mibs from a backup and re-built. But now when I run the 32bit console on win7 I get the following error after logging in:
"Cannot load MIB file from server: File I/O operation failed"

There was no issues before the upgrade.

Also, do not know if this is related to the upgrade, before upgrading I stopped the Core, Agent & WebGUI services, but there was still a lock on the MySQL DB which prevented DB upgrade.

Victor Kirhenshtein

Quote from: brettmilfos on August 11, 2015, 12:53:50 AM
I have encountered one issue. While upgrading from 2.0M5 all the mibs from var/mibs dis-appeared. This is on win2k8r2.

Restored mibs from a backup and re-built. But now when I run the 32bit console on win7 I get the following error after logging in:
"Cannot load MIB file from server: File I/O operation failed"

MIB locations was changed in 2.0-RC1. Source MIBs now are in <install_path>\share\mibs and compiled MIB file in <install_path>\var. Installer was supposed to move any non-standard MIBs from var\mibs to share\mibs. If you compile MIBs manually, you should set output file to be <install_path>\var\netxms.mib.

Quote from: brettmilfos on August 11, 2015, 12:53:50 AM
Also, do not know if this is related to the upgrade, before upgrading I stopped the Core, Agent & WebGUI services, but there was still a lock on the MySQL DB which prevented DB upgrade.

That means that core service didn't stop normally and was forcibly terminated by service manager. It's not related to upgrade, but rather indicates some problem with previous version.

Best regards,
Victor

multix

#5
Hi, again.

Perhaps I could not explain my problem.
I added screensohts for template DCI. Instance discovery is working for first OID.
In fact, it is walking for all OIDs, but return %(true,$1,ifName3); command line is not working properly (or, function that calling this script is not working properly)

There must be at least 30 (for each In_ and Out_) DCIs in this node's DCI config section

I set debug level to 6. and here is log:  It seems all discovery is returning first interface's script result.


1-Aug-2015 13:30:06.444] [DEBUG] Node::doInstanceDiscovery(AnaBinaKat2Sw1 [29910]): Updating instances for instance discovery DCI .1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]
[11-Aug-2015 13:30:06.444] [DEBUG] [CLSN-0] Sending message CMD_POLLING_INFO
[11-Aug-2015 13:30:06.563] [DEBUG] Node::doInstanceDiscovery(AnaBinaKat2Sw1 [29910]): read 29 values
[11-Aug-2015 13:30:06.566] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "1" removed by filtering script
[11-Aug-2015 13:30:06.582] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" replaced by "132"
[11-Aug-2015 13:30:06.583] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.592] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "600" replaced by "132"
[11-Aug-2015 13:30:06.593] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.596] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10001" removed by filtering script
[11-Aug-2015 13:30:06.598] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10002" removed by filtering script
[11-Aug-2015 13:30:06.611] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10003" replaced by "132"
[11-Aug-2015 13:30:06.611] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.621] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10004" removed by filtering script
[11-Aug-2015 13:30:06.624] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10005" removed by filtering script
[11-Aug-2015 13:30:06.637] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10006" replaced by "132"
[11-Aug-2015 13:30:06.637] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.639] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10007" removed by filtering script
[11-Aug-2015 13:30:06.644] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10008" removed by filtering script
[11-Aug-2015 13:30:06.653] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10009" replaced by "132"
[11-Aug-2015 13:30:06.653] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.668] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10010" replaced by "132"
[11-Aug-2015 13:30:06.668] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.670] [DEBUG] StatusPoll(GEVAS_VAN.yourdomain.com): bAllDown=false, dynFlags=0x00001001
[11-Aug-2015 13:30:06.677] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10011" replaced by "132"
[11-Aug-2015 13:30:06.677] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.680] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10012" removed by filtering script
[11-Aug-2015 13:30:06.688] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10013" replaced by "132"
[11-Aug-2015 13:30:06.688] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.696] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10014" replaced by "132"
[11-Aug-2015 13:30:06.697] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.697] [DEBUG] StatusPoll(GEVAS_VAN.yourdomain.com [18592]): boot time set to 1439179618 from SNMP
[11-Aug-2015 13:30:06.697] [DEBUG] StatusPoll(GEVAS_VAN.yourdomain.com [18592]): unable to get agent uptime
[11-Aug-2015 13:30:06.697] [DEBUG] Finished status poll for node GEVAS_VAN.yourdomain.com (ID: 18592)
[11-Aug-2015 13:30:06.709] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10015" replaced by "132"
[11-Aug-2015 13:30:06.709] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.716] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10016" replaced by "132"
[11-Aug-2015 13:30:06.716] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.726] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10017" replaced by "132"
[11-Aug-2015 13:30:06.726] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.734] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10018" replaced by "132"
[11-Aug-2015 13:30:06.734] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.749] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10019" replaced by "132"
[11-Aug-2015 13:30:06.749] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.752] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10020" removed by filtering script
[11-Aug-2015 13:30:06.754] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10021" removed by filtering script
[11-Aug-2015 13:30:06.767] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10022" replaced by "132"
[11-Aug-2015 13:30:06.767] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.775] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10023" replaced by "132"
[11-Aug-2015 13:30:06.775] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"
[11-Aug-2015 13:30:06.789] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "10024" replaced by "132"
[11-Aug-2015 13:30:06.789] [DEBUG] DCItem::filterInstanceList(.1.3.6.1.2.1.31.1.1.1.6.{instance} [19365]): instance "132" name set to "132_Vlan132__Vl132"

.

Victor Kirhenshtein

Hi,

I was able to reproduce this problem on my test system. I'll provide fix soon.

Best regards,
Victor

brettmilfos

Quote from: Victor Kirhenshtein on August 11, 2015, 08:52:14 AM
Quote from: brettmilfos on August 11, 2015, 12:53:50 AM
I have encountered one issue. While upgrading from 2.0M5 all the mibs from var/mibs dis-appeared. This is on win2k8r2.

Restored mibs from a backup and re-built. But now when I run the 32bit console on win7 I get the following error after logging in:
"Cannot load MIB file from server: File I/O operation failed"

MIB locations was changed in 2.0-RC1. Source MIBs now are in <install_path>\share\mibs and compiled MIB file in <install_path>\var. Installer was supposed to move any non-standard MIBs from var\mibs to share\mibs. If you compile MIBs manually, you should set output file to be <install_path>\var\netxms.mib.

Quote from: brettmilfos on August 11, 2015, 12:53:50 AM
Also, do not know if this is related to the upgrade, before upgrading I stopped the Core, Agent & WebGUI services, but there was still a lock on the MySQL DB which prevented DB upgrade.

That means that core service didn't stop normally and was forcibly terminated by service manager. It's not related to upgrade, but rather indicates some problem with previous version.

Best regards,
Victor

Many thanks, I had seen the new folder for the mibs, but could not see where the compiled file was meant to go.

Also, in my attempts to sort this out I may have noticed an issue with one of the mibs, that I suspect prevented the installer from generating the compiled output?
HH3C-LICENSE-MIB: ERROR 001: Import symbol "PhysicalIndexOrZero" unresolved

Searching does not find a definition for the symbol.

Sadly, I have made a big mess of things now and was wondering where I could find all the "deafault" mibs?

Thanks, Brett.

Alex Kirhenshtein

PhysicalIndexOrZero is defined in ENITY-MIB.

You can get correct MIBs from git: https://git.netxms.org/public/netxms.git (it's in contrib/mibs, branch develop), or download this archive: https://www.dropbox.com/s/tt1r7ygc1eyyh05/mibs.tar.gz?dl=0

multix

Hi. Is there any news about instance discovery error ?

Thanks.

Victor Kirhenshtein

Hi,

we just updated Windows installers and source package with new build that contain a fix. File names are the same, but after install you should see build number 8036 for server binaries. Debian repository will be updated in a few hours.

Best regards,
Victor

Alex Kirhenshtein

Debian packages updated to 2.0-RC1-2

Dani@M3T

Thanks for the new release.
We just updated this morning from V2.0-M5 to V2.0-RC1 on Linux x64 from sources.
After the update, all custom Images in Image Library are lost. They all have a 'broken image' icon (of course also in all maps). The image files are still existing in the 'image' folder on the server. There must be a problem with the references. How can this be fixed?

Victor Kirhenshtein

Hi,

directory structure was changed in RC1 to match recommended layout for Linux systems. Try to move all files from <install-prefix>/share/netxms/images to <install-prefix>/var/lib/netxms/images.

Best regards,
Victor

Dani@M3T

#14
Thanks Victor for your fast reply. That fixed it!
Are there other changes in directory structure? And are they documented anywhere?
Maybe I can delete some old dirs not used anymore.

edit1:
I see that Server File Manager files are not moved to the new directory too.