[CentOS] System Start-Up Issue Progress

2017-07-04 Thread Chris Olson
My thanks to all that responded to my posting about our virtual machine CentOS 6 system start-up issue.  I found the alternative boot options to be the most helpful.  Interrupting the boot-up process with Alt-d or Escape allowed me to see what appears to be a quite normal string of start, install a

Re: [CentOS] System Start-Up Issue Progress

2017-07-04 Thread Pete Biggs
> > Starting ipmidetectd: ipmidetectd: No nodes configured  [FAILED] > Starting sendmail: > > It is not clear to me whether the boot-up process is hanging due > to the failed starting of ipmidetectd or sendmail, but I suspect > that the ipmidetectd start up failure is the actual cause. It is > n

Re: [CentOS] System Start-Up Issue Progress

2017-07-04 Thread Tony Mountifield
In article <374968789.4117139.1499169677...@mail.yahoo.com>, Chris Olson wrote: > My thanks to all that responded to my posting about our virtual > machine CentOS 6 system start-up issue.  I found the alternative > boot options to be the most helpful.  Interrupting the boot-up > process with Alt

Re: [CentOS] System Start-Up Issue Progress

2017-07-04 Thread Jonathan Billings
On Jul 4, 2017, at 8:01 AM, Chris Olson wrote: > Starting ipmidetectd: ipmidetectd: No nodes configured [FAILED] > Starting sendmail: Any chance that this system doesn’t have valid DNS lookups? What I see above is that ipmidetetd failed (which doesn’t block) and then it is stuck starting send

Re: [CentOS] Problem with ipa-client

2017-07-04 Thread Fred Smith
On Tue, Jul 04, 2017 at 07:32:51AM +0200, Nicolas Kovacs wrote: > Hi, > > Here's the warning that Yum currently displays: > > ** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows: > ipa-client-4.4.0-14.el7.centos.7.x86_64 has installed conflicts > freeipa-client: ipa-client-4.4.0-

Re: [CentOS] System Start-Up Issue Progress

2017-07-04 Thread Chris Olson
Once again, my thanks to all that responded to my posting about our virtual machine CentOS 6 system start-up issue.  Addressing sendmail was the key to the start-up issue. While operating at Run Level 1, chkconfig sendmail off was commanded followed by the reboot command.  This brought up the syst

Re: [CentOS] System Start-Up Issue Progress

2017-07-04 Thread Gordon Messmer
On 07/04/2017 09:21 AM, Chris Olson wrote: It remains a mystery what could have happened during a standard yum update of the system to cause this domain and/or host related sendmail issue. Run "hostname". Has the hostname changed? Run "ls -l /etc/hosts /etc/resolv.conf". Have those files c

Re: [CentOS] System Start-Up Issue Progress

2017-07-04 Thread Alexander Dalloz
Am 04.07.2017 um 19:13 schrieb Gordon Messmer: On 07/04/2017 09:21 AM, Chris Olson wrote: It remains a mystery what could have happened during a standard yum update of the system to cause this domain and/or host related sendmail issue. Run "hostname". Has the hostname changed? Run "ls -l /e

Re: [CentOS] System Start-Up Issue Progress

2017-07-04 Thread Chris Olson
Organization policy dictates that information copied from systems with Internet access be "sanitized".  Thus the FAKE name computer as well as the designations and provided in my previous messages and presented again below: computer sendmail[]: unable to qualify my own domain name (c

Re: [CentOS] System Start-Up Issue Progress

2017-07-04 Thread Gordon Messmer
On 07/04/2017 02:17 PM, Chris Olson wrote: The actual system has totally legitimate names for domain and host. What actually happened during the system update is still being investigated. Your investigation should include: hostname dig +short $(hostname) host $(dig +short $(hostname