-2

Our server was running fine this morning. I installed VirtualBox and rebooted the server. Since rebooting the server I do not recieve a response when pinging the IP address and I cannot connect through SSH anymore. I have access through KVM.

Does anybody know how I might begin to troubleshoot this? I am posting the process I went through to install VirtualBox incase there was some part of the process that has caused me an issue.

cd /etc/yum.repos.d/
wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
yum update
rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
yum install VirtualBox-4.3
service vboxdrv setup
usermod -a -G vboxusers root
VirtualBox

I then connected to the server to set up a virtual machine and created a new virtual Windows 7 machine

ssh -X root@xxxxxxx
VirtualBox

I then rebooted the server and now I no longer recieve a response to my ping requests and I am unable to ssh to the server. I have KVM access.

Does anybody know what I may have done? I have done multiple reboots in the past with no issue so I assume the issue is something to do with VirtualBox.

Many thanks for any help.

Syn
  • 141

2 Answers2

3

Does anybody know how I might begin to troubleshoot this?

You know, the usual stuff from the sysadmin kitbag

Use your console access to

  • check your logs and take appropriate action.
  • check you have correctly configured network interfaces
  • check your firewall.
  • check that sshd is running
  • check your change/config management system for other recent stuff
  • ...

You may also find the method here useful

Community
  • 1
user9517
  • 117,122
0

Something during the VirtualBox setup had changed my /etc/sysconfig/network-scripts and stopped the nameservers setting correctly.

To resolve this I turned off Network Manager

/etc/init.d/NetworkManager stop
/sbin/chkconfig NetworkManager off

Added

NM_CONTROLLED="no"

to /etc/sysconfig/network-scripts/ifcfg-eth0 and manually edited /etc/resolv.conf with vi to the correct nameservers. Rebooted the server and issue seems to have gone away!

Syn
  • 141