Issue:
After performing Traveler 10.0 server update following the Domino 10.0 upgrade, the Traveler task didn't autostart with the Domino service.
The log contained the following error message indicating an issue loading the Java JVM via the libjvm.so file:
10/30/2018 05:28:07 PM Traveler: Failed to load JVM library from (/opt/ibm/domino/notes/10000000/linuxx/jvm/bin/classic/libjvm.so). Validate that this file exists and that NotesProgram in notes.ini is set correctly.
10/30/2018 05:28:07 PM Traveler: Cannot create Java VM, result=-999
Update 2022/08:
Our update from HCL Traveler 12.0 on Domino 12.0 to Traveler 12.01 on Domino 12.01 enjoyed the same bug. The solution was exactly the same, an extra x at the end of the NotesProgram line.
8/23/2022 01:21:27 PM Traveler: Failed to load JVM library from (/opt/ibm/domino/notes/12000100/linuxx/jvm/bin/classic/libjvm.so). Validate that this file exists and that NotesProgram in notes.ini is set correctly.
Solution:
It took a bit to notice the extra "X" in linuxx. As expected, the folder path to libjvm.so file did exist at: "/opt/ibm/domino/notes/10000000/linux/jvm/bin/classic/libjvm.so".
Rather than adding the path to the .profile, I looked at the notes.ini. Sure enough the notes.ini was incorrect.
$ sudo vi /local/notesdata/notes.ini
[Notes]
Directory=/local/notesdata
NotesProgram=/opt/ibm/domino/notes/10000000/linuxx
I edited the notes.ini and removed the extra "x" in the path, saved the new file, and restarted the domino service.
<esc><wq>
$ sudo systemctl stop domino
$ sudo systemctl start domino
previous page
|