NetXMS 2.0-RC1 released

[victor]

Hi,

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

Best regards,
Victor

[brettmilfos]

@victor said in NetXMS 2.0-RC1 released:

@brettmilfos said in NetXMS 2.0-RC1 released:

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.

@brettmilfos said in NetXMS 2.0-RC1 released:

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.

[alk]

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

[mkemerci]

Hi. Is there any news about instance discovery error ?

Thanks.

[victor]

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

[alk]

Debian packages updated to 2.0-RC1-2

[user54119]

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]

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

[user54119]

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.

[victor]

Basically everything that can be changed moved to <install-prefix>/var/lib/netxms (directories images, files, packages, backgrounds). Compiled MIB file now is <install-prefix>/var/lib/netxms/netxms.mib (but source MIBs keep location).

Best regards,
Victor

[user54119]

ok, so I moved the content of these folders manually:

• images
• files
• packages
• backgrounds

and removed the old folders in 'share'. Maybe that helps others

[mkemerci]

instance discovery bug has been corrected.

Thank you.

[sharpspro]

@victor said in NetXMS 2.0-RC1 released:

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

I'm running on version 2.0 RC-1 8035 and I am trying to get the server to version 8036 as mentioned above. Is there another download spot that this is stored? I went to https://www.netxms.org/download/ - SERVER BINARIES and downloaded the file with the same name "netxms-2.0-RC1-x64.exe"

After I run that install again it still shows 8035 when starting the management console. What am I doing wrong?

[a4katapz]

I am not able to save layout on a network map in the new version.
Is there any way to do it?

And just to inform the users:
I also noticed that the macros %OBJECT_IP_ADDR% and %USERNAME% don't work either.But I found a solution : Use %a% for the primary ip and %u% for the username.

[brettmilfos]

Hi,

Just noticed that this problem has come back again for the agent:

DB Library: Unable to load database driver module "sqlite.ddr": The specified module could not be found.

Odd thing, the file is in the bin folder.

Cheers, Brett.

[mkemerci]

Hi.
You said

• Unified macros in all types of object tools
  in 2.0.RC1.

Can you write an explanation for actual macros (or give a link) ? I found ALARM_ID macro for sending alarm id to object tool (trying to send alarm id to server command), bur could not use it. I think perhaps something changed.

Thanks.

[victor]

Hi,

object tools of type "server command" had always expanded macros on server side, and use event processing macros (https://www.netxms.org/documentation/adminguide/event-processing.html#macros-for-event-processing). Starting with 2.0-RC1, all other object tools with macros (local command, agent action, URL) uses as close as possible macros, with the following exceptions:

%A and %m expands to alarm message when tool executed from alarm;
%c expands to source event code when tool executed from alarm;
%N expands to source event name when tool executed from alarm;
%s expands to alarm's severity when tool executed from alarm;
%S expands to alarm's severity as text when tool executed from alarm;
%U expands to user name (of currently logged in user);
%y expands to alarm state code when tool executed from alarm;
%Y expands to alarm ID when tool executed from alarm;
%(...) expands to value of appropriate input field

Macros %u, %t, %T, %M, %, %{...}, %1...%99 are not supported.

Best regards,
Victor