Domino on Linux/Unix, Troubleshooting, Best Practices, Tips and more ...

Domino Server Install on Linux Fails with Timing Issues

Daniel Nashed  22 May 2019 17:21:03
We ran into an interesting issue yesterday which almost made our Domino 10.0.1 on Linux with brand new RHEL 7.6 machines fail.

The installer always ended like this:

Initializing Wizard.....    
Extracting Bundled JRE.    
Verifying JVM      

No Java Runtime Environment (JRE) was found on this system.

A deeper tracing with debug settings lead us to those errors:

Verifying... /tmp/istemp30481141104256/_bundledJRE_/bin/java  -cp  /tmp/istemp30481141104256/Verify.jar Verify  java.vendor java.version
Verification failed for /tmp/istemp30481141104256/_bundledJRE_ using the JVM file /tmp/istemp30481141104256/_bundledJRE_/jvm

When it stops the temp-files remain on disk. Interestingly the manual check works afterwards.
I checked everything in the script which isn't just a normal script but also contains the installer code that is executed from there.

[root@host /]# /tmp/istemp30481141104256/_bundledJRE_/bin/java  -cp  /tmp/istemp30481141104256/Verify.jar Verify  java.vendor java.version

IBM Corporation


After testing all the debug options listed somewhere in the install scripts, I found one parameter that gave me one final idea.
"-is:jvmtimer" sounded like a delay that you can add during install.

After I found this parameter I checked for references. And the only  reference I found was an older IBM installer issue for another platform on another product where this parameter is documented.

It is needed for slower platforms where the extract and start of the JVM takes too long.
It's not in detail clear but maybe in this case maybe the machine was too fast and the check routine did not wait sufficient long. The machine had 4 Cores with 8 threads each.

So the solution was to give the JVM extract and verify.jar a couple of seconds more time. It worked with 2 seconds but 4 seconds might be a better bet.

I never ran into this before on any machine over the years. But I am documenting it not just for curiosity but also if someone might run into it.

Here is how you specify the parameter.

 ./install -is:jvmtimer 4

I think I will add the parameter to the Docker Domino install script as well, because it could hit uns there as well.

Install Shield multi platform is a quite old installer, which will be replaced by Install Anyware in Domino 11.

-- Daniel


1John Hoover  21.06.2019 1:02:19  Domino Server Install on Linux Fails with Timing Issues

We found that we had to give it even longer, and used jvmtimer 8.

Regardless, thank you for saving me a call!

2Frans  11.09.2019 0:19:13  Domino Server 10.0.1 Install on Linux CentOS 7.6 Fails

Following step by step, installation of Domino 10.0.1 into CentOS 7.6 kvm v82.0.14, after updating JRE and JSK. During running ./install at /home/itsupport/linux64/domino/

we always get error message:

"Bundled JRE is not binary compatible with host OS/Arch or it is corrupt. Testing bundled JRE failed"

Even though we tried to extend time delay more than 4 seconds..i.e. 8/9/10 etc.

./install -is:jvmtimer 4

The CPU use only 1 core, Intel Xeon

I am reach out for your advice.

Thank you,


3Mike Killoran  14.09.2019 22:46:46  Domino Server Install on Linux Fails with Timing Issues

Hi Frans,

Unfortunately, we do not support the Intel Xeon processor.

4Patrick Zarnikow  24.10.2019 13:04:32  Domino Server Install on Linux Fails with Timing Issues

Thank you Daniel for documenting this. I ran into exact this problem today. I updated my 10.0.0 test environment to 10.0.1 on my virtual machine. I had to set the jvmtimer to 100 so the JRE had enough time to initialize.


  • [IBM Lotus Domino]
  • [Domino on Linux]
  • [Nash!Com]
  • [Daniel Nashed]