NetXMS Support Forum

Hi,

At first, thanks for the great software! I have been using NetXMS version 1.2.3 for a long time. Our network is not connected to Internet so the upgrade is a bit complicated task. Now i finally desided to upgrade to the current version 1.2.16. I can configure and make the new version just fine, but when I try to install it, 'make install' gives me this error:

HP-ICF-IPCONFIG: ERROR 001: Import symbol "ipv4InterfaceEntry" unresolved

My system is type is Linux, distribution is Centos 6.3. I understand this is a problem with compiling one of the MIBs in "contrib" directory? My biggest problem was that this happened in 'make install' instead of 'make', so some of the binaries had already been installed and some not. I had to compile the old version again in order to get the old system back online.

For some beculiar reason, I got the same error when compiling the old version also! But fortunately the old version binaries which were not installed because of this error, where in place already, so the system is working now with version 1.2.3.

I'm a bit confused, what can cause this error? Does the installation rely on some external package which has possibly broken down in my system since the original v1.2.3 install? Can I somehow exclude the 'contrib' MIBs being installed alltogether in order to avoid this error?

Hi,

I'll check this. Anyway, MIB compilation is a last step, so even if it fails, all new binaries are already in place. You can delete offending MIB file and run MIB compiler manually. You got same error after building 1.2.3 because this MIB file was already copied into MIB directory by 1.2.16 installer.

Best regards,
Victor

Quote from: Victor Kirhenshtein on September 06, 2014, 12:03:59 PM
Anyway, MIB compilation is a last step, so even if it fails, all new binaries are already in place.

It seems that in this case, maybe they are not? Looking the time stamps of the binaries in /usr/local/bin, I can see that four binaries (nxalarm, nxevent, nxpush and nxsms) still have the October 2012 timestamp from my original 1.2.3 build. All the others have new timestamps, so they were replaced on my unsuccessful upgrade test. But not those four?

Those for binaries are from client component. Are you sure you specify --with-client command line option when do 1.2.16 build?

Best regards,
Victor

Quote from: Victor Kirhenshtein on September 15, 2014, 08:54:01 AM
Those for binaries are from client component. Are you sure you specify --with-client command line option when do 1.2.16 build?

Oh, you are right, my bad. I forgot what options I had used on the original build. With the "--with-client" option everything seems to build. The original problem still existed, but after deleting the offending mib, I managed to get everything compiled.

Then, the new problem struck. During database upgrade, the nxdbmgr crashed to segmentation fault. Checking the system logs, I found out that there had been another segfault (probably on configure script, the crashed binary was "conftest"?) which I had missed. So again I had to compile the old version, and also restore the database from backup. As before, I managed the get 1.2.3 version back online.

I think I give up for now. My main reason for the upgrade was, that I wanted to see if the current version of nxmibc could compile the mibs for Cisco Small Business switches (the official ones, released by Cisco) as the 1.2.3 version could not. I tested it and the answer was no - nxmibc still thinks that the CiscoSB mibs have errors. So I think I stick with the 1.2.3 for the time being.

Hi,

can you provide a link to those MIBs that cannot be compiled? Also, do you have core file from nxdbmgr crsh? It can help fixing the issue.

Best regards,
Victor