You are not logged in.

#1 2014-09-06 19:32:14

Ashex
Member
Registered: 2008-12-05
Posts: 16

SSH access lost after updating systemd package

I've encountered a rather unexpected issue, I started an update earlier today and when systemd was installed I lost remote access to the system. It was at this point that things went haywire:

( 11/139) upgrading systemd                                                                                                                                  [#################################################################################################] 100%
warning: /etc/systemd/journald.conf installed as /etc/systemd/journald.conf.pacnew
warning: directory permissions differ on /var/log/journal/
filesystem: 755  package: 2755

Any new ssh connection just hang, no login prompt or anything. I had to do a hard reboot to get the system back up, worried that I may have an incomplete install I tried reinstalling systemd. This time I opened a screen session and started the installing, as soon as it got to the same point it hung. I popped out of the screen session and could still access things so I decided to check the pacman.log by issuing the command sudo less /var/log/pacman.log and it hung.

Back to square one, what's going on?

Offline

#2 2014-09-07 06:11:07

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,642

Re: SSH access lost after updating systemd package

First, make certain your system is fully up to date.  Do a pacman -Syu
Second, ensure there are no .pacnew files floating around.  First, as root, run updatedb   then do a locate pacnew
If there are any, merge them with the existing configurations.   At that point, it would probably be go to restart your system.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#3 2014-09-07 08:13:13

Ashex
Member
Registered: 2008-12-05
Posts: 16

Re: SSH access lost after updating systemd package

I ran into this when updating the system with pacman -Syu, I normally go through pacnew files after upgrades but I'll go through again.

Offline

#4 2014-09-07 18:09:40

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,642

Re: SSH access lost after updating systemd package

Okay, I have re-read everything and am a bit confused.
First, what led you to conclude that systemd needed to be re-installed?
Are you using this system to initiate a ssh connection to another system? Or are you trying to ssh into this box?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#5 2014-09-08 20:19:01

Ashex
Member
Registered: 2008-12-05
Posts: 16

Re: SSH access lost after updating systemd package

I was performing regular updates when the systemd package was marked for upgrade, it was during the upgrade of this package that things "hung" and I wasn't able to determine the package successfully upgraded (no record in /var/log/pacman.log). As such to avoid leaving the system in an inconsistent state I decided to explicitly "force upgrade" systemd hoping it was a transient issue resolved by the first reboot.

This is a personal headless file server that I access via ssh.

I'll add systemd* to IgnorePkg and upgrade everything else than loop back.

Last edited by Ashex (2014-09-08 20:43:22)

Offline

#6 2014-09-09 10:02:23

Ashex
Member
Registered: 2008-12-05
Posts: 16

Re: SSH access lost after updating systemd package

I was able to upgrade everything, systemd packages were held back so they're still on the list. Also went through and took care of pacnew files.

Offline

#7 2014-09-13 20:08:16

Ashex
Member
Registered: 2008-12-05
Posts: 16

Re: SSH access lost after updating systemd package

Exact same issue occurred when I tried to upgrade systemd after all packages had been upgraded.

Edit: Additionally this time around I got hit by some disk corruption as I'm now getting this spewed at me when installing packages:

ldconfig: Cannot mmap file /usr/lib/libGL.so.1.2.0.

ldconfig: Cannot mmap file /usr/lib/libGL.so.1.

ldconfig: Cannot mmap file /usr/lib/libGL.so.

ldconfig: Cannot mmap file /usr/lib/libEGL.so.1.0.0.

ldconfig: Cannot mmap file /usr/lib/libEGL.so.1.

ldconfig: Cannot mmap file /usr/lib/libEGL.so.

ldconfig: Cannot mmap file /usr/lib/libGLESv1_CM.so.1.1.0.

ldconfig: Cannot mmap file /usr/lib/libGLESv1_CM.so.1.

ldconfig: Cannot mmap file /usr/lib/libOSMesa.so.

ldconfig: Cannot mmap file /usr/lib/libgc.so.

ldconfig: Cannot mmap file /usr/lib/libOSMesa.so.8.

ldconfig: Cannot mmap file /usr/lib/libgc.so.1.

ldconfig: Cannot mmap file /usr/lib/libgbm.so.1.

ldconfig: Cannot mmap file /usr/lib/libgccpp.so.1.

ldconfig: Cannot mmap file /usr/lib/libgccpp.so.

ldconfig: Cannot mmap file /usr/lib/libcord.so.

ldconfig: Cannot mmap file /usr/lib/libpcap.so.1.

ldconfig: Cannot mmap file /usr/lib/libwayland-egl.so.1.

ldconfig: Cannot mmap file /usr/lib/libxatracker.so.2.

ldconfig: /usr/lib/libgccpp.so.1.0.3 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: Cannot mmap file /usr/lib/libglapi.so.0.

ldconfig: /usr/lib/libgbm.so.1.0.0 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: Cannot mmap file /usr/lib/libGLESv1_CM.so.

ldconfig: Cannot mmap file /usr/lib/libGLESv2.so.2.

ldconfig: /usr/lib/libgc.so.1.0.3 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: /usr/lib/libcord.so.1.0.3 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: Cannot mmap file /usr/lib/libglapi.so.

ldconfig: Cannot mmap file /usr/lib/libGLESv2.so.

ldconfig: Cannot mmap file /usr/lib/libwayland-egl.so.

ldconfig: Cannot mmap file /usr/lib/libpcap.so.

ldconfig: Cannot mmap file /usr/lib/libGLESv2.so.2.0.0.

ldconfig: /usr/lib/libOSMesa.so.8.0.0 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: Cannot mmap file /usr/lib/libgbm.so.

ldconfig: Cannot mmap file /usr/lib/libxatracker.so.

ldconfig: /usr/lib/libwayland-egl.so.1.0.0 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: Cannot mmap file /usr/lib/libcord.so.1.

ldconfig: /usr/lib/libxatracker.so.2.2.0 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: /usr/lib/libpcap.so.1.6.2 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: /usr/lib/libglapi.so.0.0.0 is not an ELF file - it has the wrong magic bytes at the start.

edit edit: So pacman database went a little weird and didn't have any records of those files, used pkgfile to identify the package they belonged to and had to do a force reinstall of them.

Last edited by Ashex (2014-09-13 20:25:36)

Offline

Board footer

Powered by FluxBB