Luminis 4.1.1 installation issue
Hi,
I'm in the process of upgrading from Luminis 4.1.1.51 to 4.2.2.34 on a Solaris 10 platform. I'm planning to do this on a new TEST environment - so, I need to install 4.1.1.51 on our new Solaris zone, replicate data from our PROD environment and then upgrade to 4.2.2.34. In order to get to 4.1.1.51, I need to install the following versions in the order shown below:
LP-4.0.0.0-solaris.iso
LP-4.0.1.0-solaris
LP-4.0.2.0-solaris
LP-4.1.0.0-solaris
LP-4.1.1.0-solaris and
LP-4.1.1.51-solaris
I'm having trouble installing the baseline 4.0.0.0 version. I get the following error on the console:
"
./LP-4.0.0.0-solaris /home/lumadmin/install/install.conf
[M902] checking prerequisites
[M903] creating backup file
[M905] installing luminis-4.0.0.0 build 3593
[M907] running the JES installer
Error: [E315] The 'installer' external program failed (exit code = 78):
"
Also, below is a snippet from the install.log file:
"2010-05-28 15:18 INFO install statistics:
product=luminis-4.0.0.0
build=3593
type=install
status=failure
duration=91
platform=S
tiers=CMPR
options=1
firststep=1
laststep=2054
sysinfo=SunOS lumtest 5.10 Generic_142900-09 sun4v
2010-05-28 15:18 HTTP_POST URL: http://slcbuildserver.sct.com/cgi-bin/install-feedback
2010-05-28 15:18 HTTP_POST HEADERS: []
2010-05-28 15:18 HTTP_POST BODY: status=failure&product=luminis-4.0.0.0&sysinfo=SunOS+lumtest+5.10+Generic_142900-09+sun4v&tiers=CMPR&firststep=1&platform=S&build=3593&duration=91&type=install&options=1&laststep=2054
2010-05-28 15:18 INFO Unable to post installation feedback to http://slcbuildserver.sct.com/cgi-bin/install-feedback
2010-05-28 15:18 ERROR Error: [E315] The 'installer' external program failed (exit code = 78):
Remedy: [F000] Contact Sungard Higher Education Support
Traceback (most recent call last):
File "/usr/cpsource/aurora/installer/_freeze/solaris.freeze/bin/main.py", line 317, in _install
loop.install( inst, ifile, propsfile )
File "/usr/cpsource/aurora/installer/_freeze/solaris.freeze/bin/loop.py", line 213, in install
_loop()
File "/usr/cpsource/aurora/installer/_freeze/solaris.freeze/bin/loop.py", line 415, in _loop
_event( EVENT_EXCEPTION )
File "/usr/cpsource/aurora/installer/_freeze/solaris.freeze/bin/loop.py", line 131, in _event
debugger.event( event )
File "/usr/cpsource/aurora/installer/_freeze/solaris.freeze/bin/loop.py", line 392, in _loop
iaction.do_action( _state.inst, _state.bak, _state.sect )
File "/usr/cpsource/aurora/installer/_freeze/solaris.freeze/bin/actions/install.py", line 116, in do_action
File "/usr/cpsource/aurora/installer/_freeze/solaris.freeze/bin/runutils.py", line 245, in run
[ progname, exitcode, result.stdout_and_stderr ] )
InstallError: Error: [E315] The 'installer' external program failed (exit code = 78):
Remedy: [F000] Contact Sungard Higher Education Support
2010-05-28 15:18 ERROR Error: [E315] The 'installer' external program failed (exit code = 78):
"
SungardHE hasn't been of much help in this regard. They suggested that I remove the 64-bit Java packages on the Solaris OS. I haven't been able to remove all packages due to dependencies with OS packages.
Has anybody encountered this error? If so, what is the solution/work-around ?
Any help/suggestions will be appreciated.
Thanks,
Shyam
re Luminis installation issue
It's been a while, but I seem to recall the Luminis 4 base install on solaris conflicted with many default solaris packages.
I think what I ended up doing was using pkginfo|grep mail (messaging, ldap, message, broker, calendar, Sun Java, communications, etc..) and removed any Sun package I could find that might be part of the Luminis install.
I had a list of conflicting packages at one point, but wasn't able to find the list, sorry.
I think you can also look through the *.py file (/actions/install.py" , line 245, etc..) and determine exactly what command was being run that failed.
Replicate Prod to test
Why not just clone your prod zone , reconfig to test before starting ? I'm considering re-doing my test environment exactly this way so it will be as close to prod as possible. That way you can save that snapshot and have a fallback during your upgrade testing as well.
And I can send you the list of packages I removed during my last successful install, if you still want it.
cheers
Howard
I did try cloning PROD first
Thanks to everybody for the responses. I wasn't successful using the clone method. The problem appears to have been with the LDAP settings - I didn't have a checklist of settings to change (couldn't find any SungardHE documentation) and our cloned environment was still connecting to our PROD system, causing some problems. I wasn't able to start the LDAP server on the cloned system after I made the changes. SungardHE doesn't support the clone method and they recommended using replication, which is what I intend to do.
Howard,
Can you provide the list of Solaris packages to be removed ? SungardHe gave the following list:
SUNWj5dmx SUNWj5dvx SUNWj5rtx SUNWjhdem SUNWjhdoc SUNWjhdev SUNWjhrt SUNWglow
I removed the above packages as well as some dependent ones, however, the installation error still occurs.
I noticed some debug options in the install.properties file - has anybody tried that?
I'm just stepping into the role of Luminis Sys Admin and struggling a little with my first installation! So, any help/suggestions would be appreciated.
Thanks,
Shyam
What we have done to get the
What we have done to get the systems installed is to remove the SUNWiq* packages as outlined in one of the documents. At one point we were also told that using the 1.5.0_10 JDK is the method to go so all instances of Luminis currently sit on top of that. You may want to check if the system has patch 119213-19 installed and if so, go through the initial installation of the Luminis installer then when it bombs, modify the /etc/init.d/directory script with
NSS_STRICT_NOFORK=DISABLED
export NSS_STRICT_NOFORK
then restart the directory server and start the installation process over again.
NSS_STRICT_NOFORK
I tried this but didn't work.
fake dns
When we clone a prod system to test, is setup test to point to a test dns. It points all the production names to test IP's. We back that up with hosts file changes on all the servers also.
cloning
Jason,
Can you elaborate a little more on the cloning procedure that you use? Do you have to manually change any LDAP settings? eg. luminis.database.name et al
Do you have any detailed instructions/checklist of settings to be changed ?
Thanks,
Shyam
cloning
I tried to make a blog post, but Lumdev thinks it's spam. I put detailed instructions on my site for now.
http://jasonwhitener.com/zfs.html
packages I removed in install
SUNWstadm
### imqbroker
SUNWiqdoc
SUNWiqfs
SUNWiqjx
SUNWiqr
SUNWiqu
SUNWiquc
SUNWiqum
### Java 64-bit
-n SUNWj5dmx
SUNWj5dvx
-n SUNWj5rtx
-n SUNWjhdem
-n SUNWjhdoc
SUNWjhdev
SUNWjhrt
-n SUNWglow
### others
-n SUNWiqlpl
-n SUNWiqlen
-n SUNWiqcrt
-n SUNWiqcdv
-n SUNWdsvx
-n SUNWdsvu
-n SUNWdsvr
-n SUNWdsvpl
-n SUNWdsvmn
-n SUNWdsvhx
-n SUNWdsvh
-n SUNWdsvcp
-n SUNWcomds
-n SUNWasvu
-n SUNWasvr
-n SUNWasvmn
-n SUNWasvcp
-n SUNWwbsvr
### Apache
-n SUNWapchd
-n SUNWapch2d
-n SUNWapchu
-n SUNWapch2u
SUNWapchr
-n SUNWapch2r
### Java System Application Server
-n SUNWasac
-n SUNWasdem
-n SUNWasjdoc
-n SUNWasman
SUNWasut
SUNWascmn
SUNWasr
SUNWasu
### Tomcat
SUNWtcatu
SUNWtcatr
I also removed the StarOffice packages, more to have a cleaner load than from any conflicts. and once you get a good install of 4.0.0.0 - Snapshot that baby !
good luck
Luminis 4.0.0.0 and ZFS file system
According to SungardHE, the Luminis 4.0.0.0 baseline installation doesn't work with the ZFS file system on
Solaris. Does anybody know of any work-around/solution to this issue?
Thanks,
Shyam
We currently are using ZFS
We currently are using ZFS and Luminis with no known issues. We have not released this for university-wide use though yet so results may vary.
We also have Luminis 4.1.1.51 working on ZFS
But the Luminis 4.0.0.0 baseline version was installed on our PROD system when it was using UFS. The switch to ZFS occurred after the Luminis installation and we don't have any issues with it. To clarify, the problem is with installing the baseline version on ZFS.
Shyam
ZFS and install dont work
my zones are running in ZFS just fine - I just couldnt get the Resource or Mail tier installs to work if LP-4.0.0.0-solaris is NFS mounted inside the zone (trying to save some space) - it had to be a "localFS". I forget where it bombed in the install process, but it did not like that at all. That may be what sghe is alluding to.
so in zonecfg:
fs:
dir: /mnt/zshared/luminis < path in the zone
special: /zfsdirs/lumload < path on host
type: lofs
then
zlp4 # /mnt/zshared/luminis/bin/LP-4.0.0.0-solaris .....
hw
Working on it...
Thanks to everyone for the replies. I'm not a Solaris Sys Admin - so, I don't understand all this 'adminspeak' :) Anyway, I've asked my Solaris admin to look into this - he said that he could temporarily move the Luminis files to a UFS system and see if the installation can be run that way.
Howard,
Are you suggesting something along those lines?
Thanks,
Shyam
zfs
Luminis installs on ZFS just fine. Unless there's a particular buggy combo of zfs/luminis versions that doesn't work well together that I have never experienced.
uname on one of our servers:
SunOS 5.10 Generic_142900-04 sun4v sparc SUNW,T5240
Size of our LP-4.0.0.0-solaris file:
275605757
Are you sure your admin created whole/full root zones (has an entire copy of the OS)?
Solaris specs
Jason,
Our Solaris specs are exactly the same:
uname
SunOS 5.10 Generic_142900-12 sun4v sparc SUNW,T5240
Size of LP-4.0.0.0-solaris: 275622261
We also have a whole root zone.
Our Solaris admin switched the file system temporarily to UFS and I'm getting a different error now:
"
[E000] An unexpected error has occurred. global name 'false' is not defined
See /opt/luminis/logs/install.log for details.
"
Any clues on what might be causing this? Is this installation file corrupted?
Thanks,
Shyam
global name false
Sorry, no, I've never seen "global name false" before.
It seems to be a python error:
http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=%22global+name+'false'+is+not+defined%22
But what the root cause of the error is, I'm not sure. If Sungard can't come up with anything, your probably going to need to go through the python install scripts, to the lines mentioned in the error, and see what step it is failing on.