Hello!
Usually this happens as a result of a package update (yum update) having updated the kernel libraries on your system without a matching kernel being set.
To check to see if this is the case, please log into the control panel, click the droplet, then "Access" then "Console". Then log in as root. If you are unable to load the console or log in, please let us know, perhaps sharing the access credentials that you were using.
Once logged in, run:
ls -al /lib/modules
If you do not see more than one directory, leave yourself logged in to the server on the console and let us know. However, if you do see more than one directory there, take note of the versions (best way is to take a screenshot).
Then, go to the control panel, click on the droplet, click "settings" and then "Kernel". Click the list and find the right version that matches your kernel libraries. Make sure you choose the right architecture (x32 or x64) and version matching your droplet's OS. Then, return to the console and power off with the command "poweroff". Then boot the droplet using the control panel, and check to see if networking was restored once the droplet boots. If not, please log into the console as root and then let us know so that we may investigate more deeply.
Let us know if you have any additional questions or concerns.
Regards,
Tim
DigitalOcean Support |
发表于 2015-3-30 22:46:45
楼主
