Archive

Tips for Installing eHealth 6.3.2.09 on RHEL6.7 

09-03-2015 04:03 PM

Since RHEL6.7 was not fully certified with eHealth 6.3.2.09, you will need to do the following prior to installing eHealth 6.3.2.09 on RHEL6.7:

 

There are a few lines (line 19141, 19146 and 19150)  in INSTALL.NH that use egrep command. In order to successfully install eJealth 6.3.2.09, you need to first run ENU_632_LNX_00_PLUS.sh to extract INSTALL.NH; then backup INSTALL>NH to INSTALL.NH.orig; followed by changing 'egrep -v egrep'  in those lines to 'egrep -v grep', then you can start the installation by typing INSTALL.NH.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

12-02-2015 09:06 AM

Recently I did a fresh installation on CentOS 6.7 w/ the new grep in place. I noticed that it went fine w/o any modifications. Today I had a closer look and found that Redhat reverted that change somehow. So even w/ newer grep installed the following works as expected:

 

[ehealth@ehealthcentos62 ehealth63]$ ps axo "pid comm"|egrep egrep

32080 egrep

 

Asking Google for this I found "RHBA-2015:2011-1". This update fixes the following bug:

 

* Previously, the "egrep" and "fgrep" shell wrappers were incorrectly displayed as "grep" and not as "egrep" and "fgrep" respectively in the output of the "ps" command. This update replaces "egrep" and "fgrep" shell wrappers by symlinks, and "egrep" and "fgrep" are now listed correctly in the "ps" output.

(BZ#1263252)

 

So, simply make sure you have grep last upgraded after 18th of November and you should not have any problem. I have grep-2.20-3.el6_7.1.x86_64 installed

09-23-2015 02:31 PM

RHSA-2015:1447-2: due to a security issue in grep RH simply decided to update grep to 2.20. The advisory is dated 07.08.2015, so if you run updates regularly you should have the newer grep version on your system even if you run still 6.6.

09-18-2015 03:10 PM

And here is the changelog of grep:

 

2014-05-22  Jim Meyering  <meyering@fb.com>

 

        version 2.19

        * NEWS: Record release date.

 

2014-03-23  Paul Eggert  <eggert@cs.ucla.edu>

 

        egrep, fgrep: go back to shell scripts

        Although egrep's and fgrep's switch from shell scripts to

        executables may have made sense in 2005, it complicated

        maintenance and recently has caused subtle performance bugs.

        Go back to the old way of doing things, as it's simpler and more

        easily separated from the mainstream implementation.  This should

        be good enough nowadays, as POSIX has withdrawn egrep/fgrep and

        portable applications should be using -E/-F anyway.

09-18-2015 02:38 PM

OK, and here is the explanation:

 

Redhat 5:

[ehealth@ehealth63 ehealth]$ ps ax|egrep egrep

21496 pts/1    R+     0:00 egrep egrep

 

Redhat 6.7:

[ehealth@centos6-ehealth ehealth]$ ps ax|egrep egrep

11433 pts/0    S+     0:00 grep -E egrep

 

egrep is a synonym for "grep -E".

 

In RH 5 egrep was a symlink to grep, In Redhat 6.6 egrep is a script, which calls grep -E instead. This breaks every script in eHealth doing a "...grep egrep", not just the installer!!! I'd rather try to re-instantiate the old sym link until CA fixed all scripts, which might take a while. ;-)

09-18-2015 11:29 AM

Interestingly I run into a problem when installing eH 6.3.2.06 on RH 6.6. I could fix it (see my last post), well the line numbers of course differed. Not sure why the problem was invisible before. Di Redhat break something?

09-04-2015 06:38 AM

Hmm, line 19141 & line 19150 are only executed on Solaris (AFAICT). Line 19145 & line 19146 read:

 

                    ps axo "pid,${psArg}" |
                    egrep "$1" | egrep -v "egrep" | awk '{print $1 " " $2}' > ${tmpfile}

 

I guess the purpose of that egrep -v is to filter out the egrep process before the | . And no I don't see why the original line should not work.

Related Entries and Links

No Related Resource entered.