You are here

Installing from scratch on new server: RedHat 5 and the 4.0 install file?

Submitted by Christine on Thu, 09/29/2011 - 14:55

Hey all,

We're looking to migrate our current 4.2 Luminis installation to squeaky clean Red Hat 5.7 machines (and upgrade later to 4.3). I contacted SunGard about how we go about installing 4.2, and they told me I need to first install 4.0, then upgrade up to 4.2.

Here's my problem: The 4.0 ISO file is from 2007. It wants me to have all this old stuff on the machine, and I'm wondering if it'll even work with this new version of RedHat.

Has anyone gone through this process yet? How have you gone about getting Luminis installed from scratch on a RedHat 5 machine?


Luminis Version:

Wow, I'm actually doing the exact same thing! Here's the thing though, I've been working on the installation for 2 weeks straight, and I have faced error after error. I still haven't been able to perform a successful installation, but here are some of the things Sungard has been telling me to do when I get certain errors:

The following packages must be installed:

 compat-gcc 7.3
 compat-gcc-c++ 7.3
 compat-libstdc++ 7.3
 compat-libstdc++-296-2.96.138.i386
 compat-libgcc-296-2.96.138.i386

The directory server doesn't seem to like some characters, so either do away with them on the lumadmin password if you're using the same, or use a different password for the directory server. I know it does accept underscores (_) but I'm not sure which one's it was having a problem with. I for instance had a $!-, and it must have not liked some of them.

When you get the dba to setup your database make sure they have the following grants:

Because the required compat packages are now a lot newer, you must remove any calls for old compat packages in the script prior to running the installation, otherwise the installation will fail. Perform the following steps as noted in the Luminis Platform on Red Hat Linux 4: Support and Installation Supplement (April 2009; Revised) manual.

When you get to the step where it asks you to run the "which xdpyinfo" command, if you get one of the 2 results that it asks for that's great (I haven't been able to), if you don't follow the steps provided on that manual. I still had an issue with this afterwards, so Action Line asked me to create a symbolic link from where the current xdpyinfo file resided to the place the installation script wants it at (either /usr/openwin/bin/xdpyinfo or /usr/X11R6/bin/xdpyinfo). Do this by using the following: ls -s
/xdpyinfo /usr/X11R6/bin/xdpyinfo. Make sure xdpyinfo has execute permissions.

If you do follow the extra steps in the manual, you also want to make sure the the /tmp/explode and the /jes folders have execute permissions! Especially:

(Note that the .install directory is hidden; use ls -a).

Make sure the “DISPLAY” variable is not set in profiles (.bashrc) for either root or the lumadmin user. You can do this by entering env on the command line for each user.

I've gone through craziness! I just want everyone else to have a smoother ride :/

We are also doing this on a virtual environment. If you are doing the same, then I recommend you have your fresh copy of Linux installed and get a snapshot, because Action Line has also told me that since I've been trying the Luminis installation over and over, it might also be causing some issues since some remnants may be there. They've asked me to setup a new clean environment, and so now I regret not taking a snapshot. Now I have to wait to get our server manager to create a new environment for me. Just a tip :)

YUP! We're on VMWare. And YES, I made snapshots of both my dev luminis server and the DB before I attempted install. It makes it much easier to go back.

My first install attempt was just successful. This is the stuff that we put on the server:

rpm -ivh compat-gcc-7.3-2.96.128.i386.rpm
rpm -ivh compat-gcc-c++-7.3-2.96.128.i386.rpm
rpm -ivh compat-libstdc++-7.3-2.96.128.i386.rpm
rpm -ivh compat-libstdc++-devel-7.3-2.96.128.i386.rpm

We also initially put these, but I think we probably didn't need em:

yum install gcc
yum install compat-db
yum install compat-libgcc
yum install cpmpat-libstdc
yum install compat-libstdc++-33

Also, when we installed Luminis 4 the first time around I learned that we couldn't have any special characters in the password, so yea... don't do that

So have you been successful yet in getting a successful install? Mine just worked so I'd be happy to help. We're running RedHat 5.7 64bit.

:) Christine

I haven't actually! I've been running into issues, those that I listed. Right now I'm getting a new error in regards to the web server. By this point, though, I think a clean environment would be best, so our team is working on getting that going. We are actually running on a 32-bit and our RH is 5.5. Is there anything else that's not on the manual that you all did? Did you have to go in and modify the installer file and such?

Darn, OK well here's a few things to note:

1. This install is for my dev system, so everything is on 1 machine, minus the DB.

2. I did not make any modifications to the install file.

3. Since I've installed Luminis many times in the past, I have my own installation documentation that has the gotchas that I've encountered:

- In /etc/hosts make sure the IP and hostname of the machine is on the first line, eg: machinename localhost.localdomain localhost

- Verify that your install.conf isnt missing anything. I remember this got me once, but the error noted what the problem was.

- Make sure that you have a luminis admin user on the server in a group

- If you have multiple machines, make sure there's no firewall issues that might be blocking communication

I think that's really it for my Pre-Install notes. I'd be interested to know if you're successful after trying again from a fresh install.

Good Luck!

I forgot to update this, but yes I was able to install the system successfully after a fresh OS install...I guess there were some remnants messing up the installation. Thanks for your help! :D

I am trying to accomplish this same task (install Luminis 4.0 on RHEL 5.7 64-bit as the prereq for installing Luminis 4.3). I have completed all of the steps in these posts, but I still get an error during the JES installation:

*** glibc detected *** ./ds_create: munmap_chunk(): invalid pointer: 0x08079d71 ***

followed by a long backtrace and memory map. Has anyone else experienced this issue, what was the fix?



I'm finally getting around to test installs for our LP4.3 migration from RH4 to RH5 and I'm getting the 'glibc detected' error too:

*** glibc detected *** ./ds_create: munmap_chunk(): invalid pointer: 0x08079d71 ***

Did you ever figure out what the problem was?

Off to submit to Ellucian...

--Ginny Lee/Colorado School of Mines
(AKA Evil Dagger Danielle ... it's International Talk Like A Pirate Day)


Are you installing on a 64 bit platform? Does the install successfully finish if you let it keep running?


Hi Tom,

Yes, I'm installing on 64-bit RH5.

Turns out that the glibc 'error' is not an error. The LP4.0.0 install does complete. The reason I thought that it wasn't properly installing is because I was getting .cprc source/environment errors when I tried to startcp afterwards. It turns out that sudo has changed enough between RH4 and RH5 that I needed additional lines in our /etc/sudoers file. (See Ellucian FAQ#1-28QBD.) ...well, it still may not be installing properly, but I don't know that yet.

Now I've got to see why startcp doesn't really start luminis. I think I've reverted our VMs about 10 times so far with testing... and I haven't even gotten LP4 running once on RH5. Apparently I still have a long way to go until I even start trying to migrate our LP install from our old RH4 boxes to the new RH5 boxes.

Thanks and Wish me luck!