On Mon, 2017-07-03 at 15:16 -0400, m.r...@5-cent.us wrote:
> ken wrote:
> > On 07/03/2017 02:41 PM, Gordon Messmer wrote:
> >> On 07/03/2017 05:07 AM, Chris Olson wrote:
>
> Or just hit and after the low-level, it'll display.
I hit {F4} as soon as the rghb stuff starts to display and it shows
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
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
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
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
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
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
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
>
> 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
>
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
ken wrote:
> On 07/03/2017 02:41 PM, Gordon Messmer wrote:
>> On 07/03/2017 05:07 AM, Chris Olson wrote:
>>> A progress
>>> bar at the bottom of the start-up screen never reaches completion.
>
>> Press "alt+d" on the keyboard to disable the graphical (or text)
>> progress bar and view the console
On 07/03/2017 02:52 PM, ken wrote:
On 07/03/2017 02:41 PM, Gordon Messmer wrote:
On 07/03/2017 05:07 AM, Chris Olson wrote:
A progress
bar at the bottom of the start-up screen never reaches completion.
Press "alt+d" on the keyboard to disable the graphical (or text)
progress bar and view
On 07/03/2017 02:41 PM, Gordon Messmer wrote:
On 07/03/2017 05:07 AM, Chris Olson wrote:
A progress
bar at the bottom of the start-up screen never reaches completion.
Press "alt+d" on the keyboard to disable the graphical (or text)
progress bar and view the console output of the startup
On 07/03/2017 05:07 AM, Chris Olson wrote:
A progress
bar at the bottom of the start-up screen never reaches completion.
Press "alt+d" on the keyboard to disable the graphical (or text)
progress bar and view the console output of the startup sequence.
Mark Haney wrote:
> On 07/03/2017 10:52 AM, m.r...@5-cent.us wrote:
>> Chris Olson wrote:
>>> On Monday, July 3, 2017 5:58 AM, "m.r...@5-cent.us"
>>>
>>> wrote:
>>> Chris Olson wrote:
>>>
I went on vacation right after an update to one of our virtual CentOS
6.9
On 07/03/2017 10:52 AM, m.r...@5-cent.us wrote:
Chris Olson wrote:
On Monday, July 3, 2017 5:58 AM, "m.r...@5-cent.us"
wrote:
Chris Olson wrote:
I went on vacation right after an update to one of our virtual CentOS
6.9 systems so it was not restarted for a period of
Chris Olson wrote:
> On Monday, July 3, 2017 5:58 AM, "m.r...@5-cent.us"
> wrote:
> Chris Olson wrote:
>
>> I went on vacation right after an update to one of our virtual CentOS
>> 6.9 systems so it was not restarted for a period of time. Now it will not
>> complete
>
> Having very little experience with such start-up issues, we are at a loss
> to determine how to salvage the CentOS 6.9 virtual machine. Is there a
> standard way to start up a system without any extras like gnome to see if
> we can get a running system? Would it be wise to attempt using
None of the previous kernels will boot properly.
On Monday, July 3, 2017 5:58 AM, "m.r...@5-cent.us"
wrote:
Chris Olson wrote:
> I went on vacation right after an update to one of our virtual CentOS 6.9
> systems so it was not restarted for a period of time. Now it
Chris Olson wrote:
> I went on vacation right after an update to one of our virtual CentOS 6.9
> systems so it was not restarted for a period of time. Now it will not
> complete boot-up with the gnome display never fully launched. A progress
> bar at the bottom of the start-up screen never
We run several Intel-based CentOS machines. They are all at 6.9 or 7.x.
One of each OS is Oracle VirtualBox hosted on an up to date Windows 7 system.
We use these virtual machines for checkout of new applications before they
are loaded on native CentOS platforms. Regular weekly updates are run
21 matches
Mail list logo