This is pretty old installer, look for 4.0.8.4 on SLD site. You are running it under root ?

Hi - apologies I was not clear.  I have the latest 4.0.8 installer and that is the one I am trying to use but with no success.  Yes I am running the install as root.

Have you checked MD5 ? Your installation folder should look different

vibe4084 # ll
total 1249168
-rw-r--r--  1 spravce users    402934 Mar 28 14:14 MicroFocus-vibeonprem406-eula.pdf
drwxr-xr-x 18 spravce users      4096 Mar 28 14:14 docs
-rwxr-xr-x  1 spravce users 555502001 Mar 28 14:14 installer-teaming.linux
-rwxr-xr-x  1 spravce users  60883990 Mar 28 14:14 lucene-installer.linux
-rw-r--r--  1 spravce users     36591 Mar 28 14:14 sample-installer.xml
-rw-r--r--  1 spravce users   7817711 Mar 28 14:14 teaming-4.0.8.4-db.zip
-rw-r--r--  1 spravce users    879926 Mar 28 14:14 teaming-4.0.8.4-iis-plugin.zip
-rw-r--r--  1 spravce users  12440953 Mar 28 14:14 teaming-4.0.8.4-wsclient.zip
-rw-r--r--  1 root    root  641157120 Apr  5 17:50 vibe-4.0.8.4-linux.tar

After extracting TAR, installer-teaming.linux is already ready to install.


Hi - yes MD5 matches.  I've just downloaded again to make sure I have a fresh copy but still get the installer-teaming.linux not found error!

Something is going around in my head because I've been annoyed by it before.

The installation is an upgrade

 when upgrading the installer.xml must be taken from the "old" Vibe directory and the license-key.xml file should be present.

There are a few things to consider, such as mysqldump -uroot -pvibe4you sitescape > sitescape.sql, the dump must be named like this. If the certificates are invalid and the eDir certificate is also invalid, first fix everything in the old installation with the keytool. And another thing is it is not possible to go from a Vibe 4.04 or earlier directly to 4.08 if I remember correctly

George

Georg is right. You need both files.

However you need even more if you want to continue with your old data. You need to import a dump from your old database and a copy of your subdirectory filerepository ...

I hadn't thought about the repo. I have mounted many things with a bind mount, smb mount, nfs mount etc., regardless of which installations are involved, and can then always move or extend them quickly. Thanks Dithmar

Yes this will be an upgrade but I have not moved any of the files from the old (4.0.1) install yet.  I was to do a fresh install and then rename the database folder etc.

Will move over the folders you suggest and lets see if that sorts the issue.  

Always follow the prescribed upgrade path, it is impossible to go from a 4.0.1 to a 4.0.8x. It will crash in the gearbox.

Hi Marcus,

two things:

1) based on the files size it is clear you have the 4.0.8 installer, not the 4.0.8.4 one. To get the 4.0.8.4 it could be necessary to check if you can upgrade your entitlement/activation in SLD, or you may just need to chose the right version from the dropdown above the list. For a number of reasons you should definitely install 4.0.8.4!

2) the "No such file or directory" does not necessarily have to mean the installer. The installer has dependencies and starts several other binaries, especially zip. You should have at least the packages tcl, tcl-32bit, tk,tk-32bit, libstdc++-32bit, zip, and libzip installed for the installer to run.

The installer does not need an installer.xml or a license-key.xml to start. Until it starts, the issue is almost alwaays a dependency or rights (I don't know if you can run into issues with the installer being on NSS and the rights being funky). Without license-key.xml it will tell you it's missing the license, without installer.xml all values in the dialogs are be the default values and you have to set everything again, plus there may be issues when doing an upgrade installation, e.g. losing post-install customisations.
If you are missing your last installer.xml, you can find in at <teaming-base>/teaming-config or <teaming-bas>/install-config, depending on what version it was last (<teaming-base< by default being /opt/novell/teaming/. A "find -iname -type f installer.xml" in <teaming-base> should get it for you.

HTH!
Christian