By eric348479
I did a pacman -Syu about two weeks ago and rebooted after which I promptly lost my ability to ssh into the droplet. Console access was successful but I was unable to ping 8.8.8.8 (Network is unreachable). Restoring from backup fixed the problem. I can either wait and hope for a future update to fix the problem or I can try downgrading packages one at a time until I figure out what’s causing the problem. But there are 34 packages pacman updated. Among them:
bash-4.3-3 coreutils-8.22-3 cryptsetup-1.6.4-1 device-mapper-2.02.105-2 dhcpcd-6.3.2-1 e2fsprogs-1.42.9-2 file-5.17-2 git-1.9.1-1 glibc-2.19-3 grep-2.18-1 keyutils-1.5.9-1 libarchive-3.1.2-6 libedit-20140213_3.1-1 libnl-3.2.24-1 libseccomp-2.1.1-1 libsystemd-211-1 libtirpc-0.2.4-1 libutil-linux-2.24.1-3 linux-firmware-20140316.dec41bc-1 lvm2-2.02.105-2 man-pages-3.63-1 mkinitcpio-17-1 openssh-6.6p1-1 pkgfile-13-1 ppp-2.4.6-2 python2-2.7.6-3 readline-6.3-3 s-nail-14.6.2-1 sqlite-3.8.4.1-1 sudo-1.8.10.p2-1 systemd-211-1 systemd-sysvcompat-211-1 tzdata-2014a-1 util-linux-2.24.1-3
Has anyone else run into this problem? If not, I could not find this exact issue in google.
Thanks in advance for your guidance. EB
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I have this problem too… I don’t understand your answer ziltoide. Please be more specific?
From my pacman.log: <br> <br>[2014-03-06 21:41] [ALPM-SCRIPTLET] :: systemd has not been reexecuted. It is recommended that you <br>[2014-03-06 21:41] [ALPM-SCRIPTLET] reboot at your earliest convenience. <br>[2014-03-06 21:41] [ALPM-SCRIPTLET] :: Network device naming is now controlled by udev’s net_setup_link <br>[2014-03-06 21:41] [ALPM-SCRIPTLET] builtin. Refer to the NETWORK LINK CONFIGURATION section of the <br>[2014-03-06 21:41] [ALPM-SCRIPTLET] udev manpage for a full description. <br>[2014-03-06 21:41] [ALPM-SCRIPTLET] :: No changes have been made to your network naming configuration. <br>[2014-03-06 21:41] [ALPM-SCRIPTLET] Interfaces should continue to maintain the same names. <br>[2014-03-06 21:41] [PACMAN] upgraded systemd (208-11 -> 210-2) <br> <br> <br>But actually it did rename the network interface. Sounds like the same issue to me. If so, just update your network profile for netctl or netcfg or whatever you use.
I seem to have netcfg by default. How does this update break my configuration and how/why do I need to reconfigure it? Also, why would one use netctl vs. netcfg? <br>EB
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.