Hi Kenneth and Inigo, sorry for slow reply.
@Inigo: yes, I installed the same toolchain and version. @Kenneth: I think you are right with "ACTIVATION_LICENSE_FILE=". I tried again the installation and this time I made sure that the only difference is which version of EasyBuild is loaded. When installing impi with EB 2.6.0, silent.cfg part of the log is the following: == 2016-05-18 17:08:08,778 runpy.EB_impi DEBUG Contents of /home/installer/eb/eb1/EM/test/intel_lic/EB_2.6.0/build/impi/ 5.1.2.150/iccifort-2016.1.150-GCC-4.9.3-2.25/l_mpi_p_5.1.2.150/silent.cfg: ACTIVATION_TYPE=license_server ACTIVATION_LICENSE_FILE=/home/installer/licenses/intel/license.lic PSET_INSTALL_DIR=/home/installer/eb/eb1/EM/test/intel_lic/EB_2.6.0/software/impi/5.1.2.150-iccifort-2016.1.150-GCC-4.9.3-2.25 ACCEPT_EULA=accept INSTALL_MODE=NONRPM CONTINUE_WITH_OPTIONAL_ERROR=yes == 2016-05-18 17:08:08,779 runpy.environment INFO Environment variable LOCAL_INSTALL_VERBOSE set to 1 (previously undefined) (It is later mentioned a few times with exitcode 0, but that's ok.) When doing exactly the same installation with EB 2.7.0, silent.cfg part is: == 2016-05-18 18:24:28,726 intelbase.py:313 DEBUG Contents of /home/installer/eb/eb1/EM/test/intel_lic/EB_2.7.0/build/impi/ 5.1.2.150/iccifort-2016.1.150-GCC-4.9.3-2.25/l_mpi_p_5.1.2.150/silent.cfg: ACTIVATION_TYPE=exist_lic PSET_INSTALL_DIR=/home/installer/eb/eb1/EM/test/intel_lic/EB_2.7.0/software/impi/5.1.2.150-iccifort-2016.1.150-GCC-4.9.3-2.25 ACCEPT_EULA=accept INSTALL_MODE=NONRPM CONTINUE_WITH_OPTIONAL_ERROR=yes == 2016-05-18 18:24:28,726 environment.py:97 INFO Environment variable LOCAL_INSTALL_VERBOSE set to 1 (previously undefined) And a short while later the installation crashes with == 2016-05-18 18:24:36,860 run.py:392 DEBUG cmd "./install.sh -s /home/installer/eb/eb1/EM/test/intel_lic/EB_2.7.0/build/impi/ 5.1.2.150/iccifort-2016.1.150-GCC-4.9.3-2.25/l_mpi_p_5.1.2.150/silent.cfg" exited with exitcode 2 and output: -------------------------------------------------------------------------------- Error during the silent install. ACTIVATION_TYPE=exist_lic specified although no existing license is found on the system. Please use other activation types. -------------------------------------------------------------------------------- I found another issue when using the "--module-only" flag, but I'll write a different email about it in order not to mix the topics. Hope this helps. All the best, Elena On Tue, May 10, 2016 at 2:43 PM, Kenneth Hoste <[email protected]> wrote: > Hi Elena & Inigo, > > We were just discussing a similar issue on IRC, although it was with icc > rather than impi. > > Can you look into generating a debug log for the failing impi installation > with EasyBuild 2.7.0 (eb --debug), > and hunt down the section that prints the contents on the silent.cfg > configuration file that is supplied to the installer? > > It should look something like: > > == 2016-05-10 14:22:47,380 easyblock.py:2067 INFO Running method > install_step part of step install > == 2016-05-10 14:22:47,381 intelbase.py:313 DEBUG Contents of > .../silent.cfg: > ACTIVATION_TYPE=exist_lic > ... > > The problem Pablo & I were looking into is that the > "ACTIVATION_LICENSE_FILE=" line is missing from the silent.cfg file, > because Pablo was specifying multiple license files rather than a single > one, triggering a (apparently long-standing) bug in the IntelBase generic > easyblock. > > I'd like to see if your situation is similar... > > Since you're not seeing this problem with EasyBuild v2.6.0, it's likely > you're hitting the same (or a related) bug, especially since quite a bit of > changes were made to IntelBase w.r.t. the license specs in EasyBuild > v2.7.0, cfr. https://github.com/hpcugent/easybuild-easyblocks/pull/839 . > > > regards, > > Kenneth > > > On 10/05/16 14:28, Elena Malkin wrote: > > Hi Inigo, > > thanks for the answer. Which version and main settings of EasyBuild were > you using? > > I ended up installing imkl and impi with EasyBuild 2.6.0 and the rest with > EasyBuild 2.7.0. If there was any other difference between the 2 > installations, I don't see it. Both used the same configuration file with > the default naming scheme, hidden=True and some packages listed on the > hidden list. We are also using an academic license. > > All the best, > Elena > > > On Tue, May 3, 2016 at 1:25 PM, Inigo Aldazabal Mensa < > [email protected]> wrote: > >> On Tue, 3 May 2016 12:34:13 +0200 >> Elena Malkin <[email protected]> wrote: >> >> > Hi easybuilders, >> > >> > first, let me thank you for the help I received last summer. I >> > realised I never answered that email. Sorry and thank you. :) >> > >> > Now to my new question: I ran into a problem installing the intel >> > 2016a bundle with EasyBuild 2.7.0 and I would like to figure out what >> > is going on. To be more precise: icc and ifort install without >> > problems, but impi stops because it can not find a license. >> > >> > We have played around with easybuild installations to find out which >> > configuration works best for us. During this time we also installed >> > intel 2016a with EasyBuild 2.6.0. This intel package works on our >> > system, so our license should be ok. I have now created a new >> > installation account, a new directory tree, installed EasyBuild >> > 2.7.0, and I am trying to reinstall everything in this directory >> > tree. I ran into the problem of icc and ifort being installed without >> > problems, and impi installation giving me the following error: >> > >> > Error during the silent install. ACTIVATION_TYPE=exist_lic specified >> > although no >> > existing license is found on the system. Please use other activation >> > types. >> > >> > When I load the old installation of EasyBuild - that is 2.6.0 - the >> > impi installation completes without problems. I am using the same >> > account for both tries and I didn't specify explicitly the config >> > file, so I expect the easybuild to use the same >> > $HOME/.config/easybuild/config.cfg in both cases. >> > >> > What could be the problem? Let me know if you need more information. >> >> The same thing happened to me, but with intel/2015a: icc and ifort >> installing without problems and impi failing with same error you >> mention. >> >> After a few tries I went back to install impi with its own installer, >> and although there you explicitly specify the license file, it failed >> with "The license file(s) you provided is not valid for this product." >> >> This is strange as the full Intel Parallel Studio XE Cluster Edition, >> impi included, installed without problems. Only the isolated impi >> installation failed. >> >> This was using an academic license. >> >> I didn't sort this out yet. >> >> >> https://software.intel.com/en-us/forums/intel-clusters-and-hpc-technology/topic/624867 >> >> >> Bests, >> >> Inigo >> >> >> >> > >> > All the best, >> > Elena >> > > >
