On 03/10/2013 01:04 PM, Frank Cox wrote:
> On Sun, 10 Mar 2013 12:26:51 -0400
> Gerry Reno wrote:
>
>> The "yum update" that was running in your lost VNC session was in all
>> likelihood still running.
> If yum was indeed still running, it wasn't using any significant CPU. I did
> run top in my login terminal to see if anything significant was going on and yum
> didn't show up on the list.
>
> When I attempted to re-connect to vncserver after that, I was told "connection
> refused", and "service vncserver start" cranked up another session for me
> without any errors.
>
> I think vncserver just altogether crashed for some reason, probably related to
> the yum update that I was running on that machine at the time. I suppose the
> lesson learned here is to always update the host machine from a screen session
> running in a plain terminal, not through a vnc session.
The reason I said yum update was still running was because I've had this exact scenario occur before.
VNC died during yum update and when I got back in I could see that yum update was still running.
I just waited until it finished.
>
>> It may be easier to restore from backup and then attempt to do the update
>> again.
> Perhaps, but since everything seems to still be in place on those hard drives,
> and since my last "yum update" completed without any errors being reported, I
> suspect (hope?) that everything is still ok with the exception of whatever is
> causing the machines to fail to boot.
>
I hope it is only your initramfs. If that isn't it, for me I would just restore and rerun the update. Much less time
involved.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
