Topic
  • 4 replies
  • Latest Post - ‏2014-04-03T21:27:28Z by mcottam
SystemAdmin
SystemAdmin
13279 Posts

Pinned topic Managed DB2 install fails to install

‏2013-03-16T00:09:38Z |
Hi,

I'm installing Systems Director 6.3.2 on a HS20-8832 with RHEL5. I have some warns on the pre-reqs, I'm 1gb short on swap and IPMI isn't available, apart from that it's all ok. When I go to install I get the following:
DB2 pre-req check completed successfully
CMD: /mnt/SysDir/server/packages/db2/prereqcheckdb2.sh RC: 0
Managed DB2 is supported and it's prereqs are met.
Preparing packages for installation...
Log file: /tmp/installdb2.log
Installing 64-bit DB2
kernel.shmmax = 268435456
WARNING:
The 32-bit library file libpam.so is not found on the system.
DBI1191I db2setup is installing and configuring DB2 according to the
response file provided. Please wait.
/mnt/SysDir/server/packages/db2/x64/db2/linuxamd64/install/db2setup: /tmp/db2.tmp.18354/db2/linuxamd64/install//db2chgpath: /bin/sh: bad interpreter: Permission denied
/mnt/SysDir/server/packages/db2/x64/db2/linuxamd64/install/db2setup: /tmp/db2.tmp.18354/db2/linuxamd64/install//db2setup_exec: /bin/sh: bad interpreter: Permission denied
/mnt/SysDir/server/packages/db2/x64/db2/linuxamd64/install/db2setup: line 822: /tmp/db2.tmp.18354/db2/linuxamd64/install//db2setup_exec: Success
DB2 failed to install.
error rc 1
Log file: /tmp/uninstalldb2.log
DB2 is not installed in /opt/ibm/director/db2. Exiting the uninstallation process.
CMD: /mnt/SysDir/server/packages/db2/installdb2.sh -dbInstall true RC: 1
IBM Systems Director managed DB2 server or client failed to install
with RC=1. Check the database installation logs
located at /tmp/installdb2.log and /tmp/db2setup.log.
And in the /tmp/installdb2.log log:

Installing 64-bit DB2
64-bit RedHat. Setting kernel.shmmax to 268435456
DB2 install ERRORRC 1
Received DB2 RC=1. Checking if DB2 install was successful.
DB2 failed to install.
ERRORRC= 1
Attempting to cleanup up...
Copying unix_db2uninstall.rsp to /opt/ibm/director/db2
Setting permissions for unix_db2uninstall.rsp
Copying uninstalldb2.sh to /opt/ibm/director/db2
Setting permissions for uninstalldb2.sh
Backing up DB2 log files to /tmp/installdb2f
Calling uninstalldb2.sh
Removing temporary files and directories

I have the 32-bit pam libs installed, but I don't think that's the issue, as it's just a warn.

has anyone come across this one before? I can't find anything on this one.

Cheers,

Anton
Updated on 2013-03-19T15:15:32Z at 2013-03-19T15:15:32Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: Managed DB2 install fails to install

    ‏2013-03-18T16:19:46Z  
    I managed to get around this one.

    I noticed I was getting some "permission denied" errors when running db2chgpath (Example: /tmp/db2.tmp.2195/db2/linuxamd64/install/db2chgpath). What this really meant was "I don't have enough space to write in /tmp", so I resized that and the installation went ahead.
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: Managed DB2 install fails to install

    ‏2013-03-19T15:01:16Z  
    I managed to get around this one.

    I noticed I was getting some "permission denied" errors when running db2chgpath (Example: /tmp/db2.tmp.2195/db2/linuxamd64/install/db2chgpath). What this really meant was "I don't have enough space to write in /tmp", so I resized that and the installation went ahead.
    Now getting this:

    Install logging started at Tue Mar 19 16:05:48 GMT 2013
    bitness: 64
    platform: Linux
    machine: x86_64
    db2 host: c4p-director01.prod.channel4.com
    Host c4p-director01.prod.channel4.com has been successfully pinged.
    Checking if dirinst1 exists...
    id: dirinst1: No such user
    Creating test user ID...
    uid=502(dirinst2) gid=502(dirinst2) groups=502(dirinst2)
    A test user ID was created okay.
    Checking /root/lrb/tuser/user...
    /root/lrb/tuser/user does not exist.
    Pre-req check on 64-bit Linux
    Any warning message about libpam.so can be ignored as this is not required by Director Server
    Current disk space:
    /dev/mapper/base-root 32487280K 1368904K 29441576K 5% /
    DB2 pre-req check failed
    WHAT THE HELL DOES THIS MEAN!!???
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: Managed DB2 install fails to install

    ‏2013-03-19T15:15:32Z  
    Now getting this:

    Install logging started at Tue Mar 19 16:05:48 GMT 2013
    bitness: 64
    platform: Linux
    machine: x86_64
    db2 host: c4p-director01.prod.channel4.com
    Host c4p-director01.prod.channel4.com has been successfully pinged.
    Checking if dirinst1 exists...
    id: dirinst1: No such user
    Creating test user ID...
    uid=502(dirinst2) gid=502(dirinst2) groups=502(dirinst2)
    A test user ID was created okay.
    Checking /root/lrb/tuser/user...
    /root/lrb/tuser/user does not exist.
    Pre-req check on 64-bit Linux
    Any warning message about libpam.so can be ignored as this is not required by Director Server
    Current disk space:
    /dev/mapper/base-root 32487280K 1368904K 29441576K 5% /
    DB2 pre-req check failed
    WHAT THE HELL DOES THIS MEAN!!???
    Just to expand on this, I adjusted root so that it was 32gb instead of 14 gb and it's now seemingly complaining about not having enough space on / ! I really am losing patience with this software now. Is there a way to ignore pre-reqs?
  • mcottam
    mcottam
    1 Post

    Re: Managed DB2 install fails to install

    ‏2014-04-03T21:27:28Z  
    Just to expand on this, I adjusted root so that it was 32gb instead of 14 gb and it's now seemingly complaining about not having enough space on / ! I really am losing patience with this software now. Is there a way to ignore pre-reqs?

    Old thread, but posting this here in case anyone else needs it.  Installing Systems Director 6.3.2 on RHEL 6.4 (64-bit) on PowerLinux hardware.

    I had to perform one additional configuration step to get past this. RHEL 6 (and I believe 5) has a security feature called Address Space Layout Randomization (ASLR). Apparently this causes some issues with the Managed DB/2 that Systems Director wants to use (default database for ISD). ASLR must be disabled for DB2 to work.

    Fortunately, ASLR is easy to disable:

    1. See if it is enabled: # cat /proc/sys/kernel/randomize_va_space
    2. If it returns a 1 or 2, ASLR is enabled and must be disabled
    3. Edit /etc/sysctl.conf
    4. Add these lines to the end and save/quit:
     
    # Disable ASLR Address Space Layout Randomization (req'd for DB2)
    kernel.randomize_va_space = 0
     
    5. Load the new configuration: # /sbin/sysctl -p
    6. Verify ASLR is disabled (should return zero): # cat /proc/sys/kernel/randomize_va_space
     

    Systems Director installed successfully for me after I did this.