Re: New Client Reply - [AWIPS !GRI-490771]: CAVE 17.1.1-5 Installation problems

New Client Reply: CAVE 17.1.1-5 Installation problems

On Mon, Mar 12, 2018 at 2:41 PM, Unidata AWIPS Support <
address@hidden> wrote:

> Hi Bob,
>
> I thought this was resolved, sorry for not following up further.
>
> I'm still not sure how best to manage RPM installation on RHEL 7.  On RHEL
> 6 the groupinstall and groupupdate commands are executed as expected, but
> RHEL 7 uses markings for packages and groups and sometimes updates do not
> happen as they do on RHEL 6.  The "yum groupinstall ..." command in
> *install.sh* is intended to update any installed packages, or install
> freshly if nothing is installed (so a "yum groupremove" step is not
> necessary, at least on RHEL 6, and I thought on RHEL 7 as well), as long as
> the metadata has been refreshed (which can be done manually with "yum clean
> all").
>
> So a forced manual reinstall for CAVE is the best solution right now:
>
> yum remove awips2-cave awips2-cave-wrapper
> yum clean all
> yum install awips2-cave awip2-cave-wrapper
>

Hey Michael,

Thanks for the followup. Since we are now only running CAVE and EDEX on
RHEL 7 systems, I'll adopt your upgrade instructions for all of our CAVE
workstations. I did, however, want to alert you to one thing. When I used
your commands on one of our RHEL 7 CAVE client systems, after I did the
install I ran a yum update and there were further updates installed. See
the abridged console log from the upgrade here:

   http://www.cs.unca.edu/~benites/detached/awips.log

Some of the versions installed are 17.1.1-4, is that correct?

Would a group{install/remove] be the appropriate upgrade path for our EDEX
server, say:

   yum groupremove awips2-server
   yum clean all
   yum groupinstall awips2-server

In the recent past it's been necessary to use the parameter
--disablerepo=epel on the groupinstall, I didn't know if the new version
has resolved those dependency issues.

Thanks...

-- Bob



>
> Michael James
> Unidata Program Center
> Boulder, CO
>
> On Mon, Mar 12, 2018 at 11:18 AM, Bob Benites <address@hidden.
> edu> wrote:
>
> > New Client Reply: CAVE 17.1.1-5 Installation problems
> >
> > I submitted this case about a month ago -- see original problem
> > report/question below.
> >
> > I was curious if you had any comment, e.g. simply use yum update to
> > install the new version or do a yum group remove and yum group
> > install.
> >
> > Thanks...
> >
> > -- Bob
> >
> > ---------- Forwarded message ----------
> > From: Bob Benites <address@hidden>
> > Date: Sat, Feb 3, 2018 at 1:30 PM
> > Subject: CAVE 17.1.1-5 Installation problems
> > To: address@hidden
> > Cc: Chris Hennon <address@hidden>, Richard White <address@hidden>,
> > David Reynolds <address@hidden>
> >
> > Hi Michael,
> >
> > Happy New Year! I know it's a little late, but been a while since
> > you've heard from me.
> >
> > I was dipping our toes in the upgrade process, upgrading one Linux
> > CAVE client from 17.1.1-2 to 17.1.1-5. I downloaded the installCAVE.sh
> > file and upgrading one RHEL 7 system.
> >
> > Like I said, I was dipping our toe in the upgrade process so while I
> > didn't see a note that the new CAVE client could use the old EDEX
> > server, I just assumed it would be OK. Chris Hennon suggested that
> > even if there was an incompatibility, he could use the online data
> > sources for his testing till we upgraded our EDEX server.
> >
> > I was more than a little surprised that the installCAVE.sh script
> > didn't do a yum groupremove if it detected the CAVE client on the
> > system then doing a yum groupinstall. I recall in a previous email
> > that's what you suggested was your preferred installation method.
> >
> > Regardless I ran the installCAVE.sh script and it had a couple of
> > errors, you can see the install log here:
> >
> >    http://www.cs.unca.edu/~benites/cave18/cave-install-upgrade.log
> >
> > I was a little concerned about the errors so I went ahead and did a
> > groupremove followed by a groupinstall and still saw some errors:
> >
> >    http://www.cs.unca.edu/~benites/cave18/cave-install-only.log
> >
> > Comments?
> >
> > -- Bob
> >
> > P.S. to Chris Hennon: I have installed CAVE 17.1.1-5 on wwall. I
> > installed from home last night so I wasn't able to fire up the new
> > CAVE client and so I'm not sure what condition it is in based on the
> > errors I saw in the install.
> >
> >
> > On Sat, Feb 3, 2018 at 1:31 PM, Unidata AWIPS Support
> > <address@hidden.edu> wrote:
> > >
> > > Bob Benites,
> > >
> > > Your Ticket has been received, and a Unidata staff member will review
> it
> > and reply accordingly. Listed below are details of this new Ticket.
> Please
> > make sure the Ticket ID remains in the Subject: line on all
> correspondence
> > related to this Ticket.
> > >
> > > NOTE: All email exchanges with Unidata User Support are recorded in the
> > Unidata inquiry tracking system and then made publicly available through
> > the web.  If you do not want to have your interactions made available in
> > this way, you must let us know in each email you send to us.
> > >
> > >     Ticket ID: GRI-490771
> > >     Subject: CAVE 17.1.1-5 Installation problems
> > >     Department: Support AWIPS
> > >     Priority: Normal
> > >     Status: Open
> > >
> > >
> > >
> > > NOTE: All email exchanges with Unidata User Support are recorded in the
> > Unidata inquiry tracking system and then made publicly available through
> > the web.  If you do not want to have your interactions made available in
> > this way, you must let us know in each email you send to us.
> > >
> > > Please let us know how we can assist you further.
> > >
> > > Unidata User Support
> > >
> >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: GRI-490771
> > Department: Support AWIPS
> > Priority: Critical
> > Status: Open
> > Link:  https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=ti
> > ckets&_a=viewticket&ticketid=29069
> >
> >
>
>
>
> Ticket Details
> ===================
> Ticket ID: GRI-490771
> Department: Support AWIPS
> Priority: Critical
> Status: Open
> ===================
> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available through
> the web.  If you do not want to have your interactions made available in
> this way, you must let us know in each email you send to us.
>
>
>



Ticket Details
===================
Ticket ID: GRI-490771
Department: Support AWIPS
Priority: Critical
Status: Open
Link:  https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=29069