Lots of Java Errors during Installation

[email protected]
Newsgroups gmane.linux.suse.domino
Message-ID <OF629E35FC.97F9F838-ONC1256C0E.00443A67-C1256C0E.00456EC3@intern.nimbus.at>
Hi There!

I just tried to install Domino 5.0.8 on my SuSE 8.0 Prof. I followed the
installation - Instructions, but when I tried to start the configuration, I
got some strange messages. I hope anybody here can help.

That´s what I did:

I extracted the linux - directory to my ~
then I executed the isntall - script.
I decided to install an application - server
I left the standard - installation paths.

then I added the user notes, who is member of the group notes.

I logged in as "notes" and changed to the directory /local/notesdata/
Then I set the Paths as mentioned in the documentation (usr/...)
I then executed /opt/lotus/bin/http httpsetup

The banner said:
Lotus Domino Server Setup
To setup ...

And then that message was displayed:
libjitc.so: cannot open shared object file: file not found (libjitc.so)
SIGSEGV received at bfffd098 in /opt/lotus/notes/latest/linux/libjava.so
Processing terminated
Writing stack trace to javacore4822.txt ... 08/07/2002 02:28:50 PM Addin:
Agent error message: jni full version "JDK 1.1.8 IBM build l118-20000325
(JIT enabled: jitc)

After that, many Agent error messages occured
for example "java.lang.System.initializeSystemClass(System.java)

and many messages about hte threads, one about the garbage collector, ...


Thanks in advance,
Andy

----------------------------------------------------------------------------

| nimbus Development IT Consulting GmbH
| we unleash the power of domino
|
| Annenstrasse 30/1
| 8020 Graz
| Tel.: +43 (0) 316 714 255 -> DW 18
| Fax: +43 (0) 316 714 255 -> DW 4
| http://www.nimbus.at/
----------------------------------------------------------------------------



-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.