[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #CWA-506895]: Bug in LDM 6.13.7

Hi Gilbert,

So, I logged in as you on weather, and verified your observations about
'ldmadmin watch' generating a Segmentation fault message.  I got Steve
on the phone, and he guided me through a series of tests in an attempt
to try and understand what was going on.  At some point, the system was
rebooted, and our tests stopped for a couple of minutes.  Before the
reboot, I did a 'cat /etc/centos-release' and saw that your system was
OR was in the process of being upgraded to CentOS 6.8.

After the reboot, I quickly logged back in as you and low and behold
'ldmadmin watch' now runs correctly from your account!

The question for you now is:

- where has weather been in the process of upgrading to CentOS 6.8
  when 'ldmadmin watch' was not running from your account?

  I upgraded my McIDAS development VMware VM from CentOS 6.7 to 6.8
  last Friday afternoon, but that 'yum update' was the second part
  of the upgrade process the first of which took part a few days
  before.

  The question (in my mind, at least) is if your machine was in
  a bit of a weird state after one of two 'yum update's that were
  aimed at upgrading from CentOS 6.7 to 6.8?

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: CWA-506895
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.