You are here

Luminis 4 Installation : server.xml is missing

Submitted by bnason on Mon, 03/31/2014 - 15:47

I'm attempting to setup a dev box using CentoS 6.5 32bit and was wondering if anyone could shed some light. The installation is getting stuck on step 2053 with the error "/u01/luminis/products/ws/https-admserv/config/server.xml is missing"

The full output is below:

/bin/sh -c /u01/lmadmin/luminis_setup/LP-4.0.0.0-linux/jes/Linux_x86/installer -nodisplay -noconsole -state /tmp/luminis-install/jes.state

In reset. Key value is now /u01/luminis/products/ws
installer exit code = 0
installing ... 24% (step 2053 of 8518)rule=13 uid=501 gid=502 mode=0600 /u01/luminis/install/backup-luminis-4.0.0.0.zip
install statistics:
product=luminis-4.0.0.0
build=3593
type=install
status=failure
duration=25
platform=L
tiers=PR
options=1
firststep=2053
laststep=2053
Error: [E379] The JES installer didn't complete successfully:
/u01/luminis/products/ws/https-admserv/config/server.xml is missing:
Look through the JES install logs in /var/opt/sun/install/logs

Remedy: [F000] Contact Sungard Higher Education Support
Error: [E379] The JES installer didn't complete successfully:
/u01/luminis/products/ws/https-admserv/config/server.xml is missing:
Look through the JES install logs in /var/opt/sun/install/logs

Remedy: [F000] Contact Sungard Higher Education Support
Error: [E379] The JES installer didn't complete successfully:
/u01/luminis/products/ws/https-admserv/config/server.xml is missing:
Look through the JES install logs in /var/opt/sun/install/logs Remedy: [F000]
Contact Sungard Higher Education Support

Thanks!

Luminis Version:

Hi,

You may have already been through this but...
I can't tell from your output, are you familiar with the RHEL supplemental install guide?
There are some additional steps required which I believe apply to CentOS.

Thanks,
Tom

Thanks for the reply,

I have followed the "Luminis Platform on Red Hat Linux 4 - Support and Installation Supplement" April 2009 (Revised) document. Is there a more recent version you know of?

Thanks,
Brandon

Brandon,

It looks like that is the most recent copy I have which I've used several times.
This may seem somewhat obvious but I've made mistakes performing the edits, have you tried making the edits multiple times/carefully reviewed your work and it still fails?
The only difference I've noticed between what you're doing and what I normally do is the directory you're executing from. I usually go with /tmp to avoid permissions issues but that's a shot in the dark not knowing much about your server configuration.

Thanks,
Tom

I actually just got past this error! It seems when they say if the install fails you and must start over, they aren't lying. I re-setup the vm and got to right before the install point and made a snapshot and that has been helping me get further. The current error i'm seeing is

Error: [E379] The JES installer didn't complete successfully:
/u01/luminis/products/ds/slapd-cp/start-slapd is missing: Look through
the JES install logs in /var/opt/sun/install/logs

With the last bit of that log file being:

Command /opt/sun/directory-server/5.2/sbin/directoryserver configure -f /tmp/ds.statefile generated the follwing outputs :
|#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|
Output Log:|#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log||#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|The reference basedir ({0}) could not be identified.Please Exit and check your|#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|installed packages.|#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log||#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|Directory Server Configuration Failed ...|#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|Configuration failed for : DSConfigurator|#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|*** End configuring DSConfigurator***
|#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|
*** Start configuring ASConfigurator... ***
|#]
[#|2014-04-01T09:27:17-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|AdminServConfigurator::configure() called ...|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|

Command /opt/sun/admin-server/5.2/sbin/mpsadmserver configure -f /tmp/adminserv.statefile generated the follwing outputs :
|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|
Output Log:|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|Error: The following packages are not installed:|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|sun-admin-server|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log||#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|
Error Log:|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|error: incorrect format: unknown tag|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|Admin Server Configuration Failed ...|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|Configuration failed for : ASConfigurator|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|*** End configuring ASConfigurator***
|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|Error in executing command : /u01/luminis/products/ds/slapd-cp/stop-slapd|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|Error in executing command : /u01/luminis/products/ds/slapd-cp/stop-slapd|#]
[#|2014-04-01T09:27:18-06:00|CONFIG|JavaES|Config|_versionID=1.0;_threadID=11;_SourceJavaFile=JDKLogger;_SourceMethodName=log|Error in executing command : /u01/luminis/products/ds/stop-admin|#]

Thanks,
Brandon

Brandon,

Yes - you definitely want to start fresh each time.
I usually take a snapshot of the fresh OS and then once I have a good 4.0 install I take another snapshot before applying patches.

As far as troubleshooting the LDAP component, I'm not familiar with that exact error message. I wonder if it's possible there is an issue with the CentOS release you're on...

That being said, have you confirmed whether or not the LDAP directory/utilities exist or not?
Basically have you confirmed whether the message that is output in the error is correct?

Thanks,
Tom

Yea I've been taking snapshots this whole time, made it MUCH easier. In good news, I did manage to get my resource tier and portal tier setup. The problem: using CentoS 6.5, I needed to go down to CentOS 5.10. Once I did a fresh install of that it went smoothly.

Thanks for you help!
Brandon

Brandon,

That's great news, I'm happy to hear that you were able to get through the installation.
I thought there might be an issue with the CentOS release but didn't have anything official to point to.

Good luck patching! :)

Thanks,
Tom