Question & Answer
Question
Guardium GIM install can fail with "GIM installation directory not found : /usr/local/guardium/modules"
Cause
There have been cases where GIM installation can fail as follows For example consider the following installation attempt :- $ /tmp/xxxx/xxxxx/guard-bundle-GIM-10.1.4_r103106_v10_1_4_1-rhel-6-linux-x86_64.gim.sh -- --dir /usr/local/guardium --sqlguardip xx.x.xx.xxx --tapip xx.x.xx.xxx --perl /usr/bin -q Verifying archive integrity... All good. Uncompressing Guard BUNDLE-GIM Installer.... Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes. Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly. Ifconfig is obsolete! For replacement check ip. Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes. Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly. Ifconfig is obsolete! For replacement check ip. Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes. Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly. Ifconfig is obsolete! For replacement check ip. Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes. Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly. Ifconfig is obsolete! For replacement check ip. GIM installation directory not found : /usr/local/guardium/modules
Answer
In fact the initial message :-
Ifconfig is obsolete! For replacement check ip.
is not a problem and is an INFO message only.
The real problem was identified via the next message :-
GIM installation directory not found : /usr/local/guardium/modules
such that a previous install of the GIM has not uninstalled correctly and left some files that still need to be removed manually.
In this case the GIM was attempted on a on RedHat Linux system :-the following needed to be removed before the above was attempted again /etc/init/gsvr_* /etc/init/upguard.conf
A similar example on a Solaris system meant that the following was needed in order to remove all traces of previous GIM
svcadm -v disable guard_gim svccfg delete guard_gim rm -f /lib/svc/method/guard_gim_svc svcadm -v disable guard_gsvr_svc svccfg delete guard_gsvr_svc rm -f /lib/svc/method/guard_gsvr_svc
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Component":"","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
07 September 2018
UID
ibm10730839