Couldn't ssh in after update

This forum is for discussion about general software issues.

Couldn't ssh in after update

Postby auzn » Sat Oct 17, 2015 3:20 pm

I have a goflex home. I did a update (pacman -syu) yesterday and after that I can no longer ssh into to the system. It always says access denied. I tried my normally used user name, tried root, and tried alarm:alarm. None seemed to work. But other than not be able to log in, the system is working fine with all the services running properly (as far as I can tell).

How do I log in to the system now.
Last edited by auzn on Sun Oct 18, 2015 1:22 am, edited 1 time in total.
auzn
 
Posts: 13
Joined: Fri Nov 16, 2012 8:39 pm

Re: Couldn't ssh in after update

Postby technosf » Sat Oct 17, 2015 5:33 pm

Ditto.

It was after only an update systemd components.

I'm always queesy when I see systemd updates close together, though I do like it much.
[size=85] MochaBin 5G || NSA325 [/size]
technosf
 
Posts: 147
Joined: Sat Jan 08, 2011 10:54 pm

Re: Couldn't ssh in after update

Postby niedi74 » Sat Oct 17, 2015 8:19 pm

same for me on my 2 armv5 boxes ;(

downgrade to libsystemd-226-3.1 systemd-226-3.1 systemd-sysvcompat-226-3.1

seams to be fix the problem
niedi74
 
Posts: 14
Joined: Mon Dec 23, 2013 7:32 am

Re: Couldn't ssh in after update

Postby auzn » Sun Oct 18, 2015 1:22 am

How to I downgrade though? given that I cannot log into my goflex.
auzn
 
Posts: 13
Joined: Fri Nov 16, 2012 8:39 pm

Re: Couldn't ssh in after update

Postby technosf » Sun Oct 18, 2015 1:34 am

$this->bbcode_second_pass_quote('', 'H')ow to I downgrade though? given that I cannot log into my goflex.

In my case, I break out the serial cable when I get home...

With no serial cable, I would be looking at popping out the disk and chrooting the install on another machine.

To downgrade you have to look in the package cache for the previous versions of the systemd packages and forcing them to overwrite the new ones.

It may be that the systemd upgrade expected a change to a config and that journalctl will tell you what the problem is. And then you make the change and all is well.
[size=85] MochaBin 5G || NSA325 [/size]
technosf
 
Posts: 147
Joined: Sat Jan 08, 2011 10:54 pm

Re: Couldn't ssh in after update

Postby niedi74 » Sun Oct 18, 2015 5:33 am

Hi
I've on both boxes serial to usb adapters.
Ive check first the pacman.log and use then the older packages out of the pacman/pkg cache folder.
niedi74
 
Posts: 14
Joined: Mon Dec 23, 2013 7:32 am

Re: Couldn't ssh in after update

Postby hecatae » Sun Oct 18, 2015 6:28 pm

is there an update on this,

I can pacman -Syu to same version if needed and boot into rescue system if there is an issue with the systemd227 packages?

edit: pacman -Syu to latest versions, can still get in:

$this->bbcode_second_pass_code('', 'Last login: Sun Oct 18 18:32:57 2015 from 192.168.1.104
[root@goflexhome ~]# pacman -Qi systemd | grep -i version
Version : 227-1
')
hecatae
 
Posts: 32
Joined: Tue Nov 18, 2014 9:17 pm

Re: Couldn't ssh in after update

Postby moonman » Sun Oct 18, 2015 8:57 pm

227 works fine for me on all my devices. Really don't know why you guys are having problems
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Couldn't ssh in after update

Postby mwNas » Sun Oct 18, 2015 9:54 pm

Fascinating. I could not SSH in (user) either (pogoplug). It's as if the user/password is no longer available. The device received a DHCP address and a SAMBA share was available on the boot USB stick. But a SAMBA share on /mnt/usb1 (fat32) was not available. I restored to last months backup, 225-1.
mwNas
 
Posts: 17
Joined: Sun Jul 19, 2015 8:28 pm

Re: Couldn't ssh in after update

Postby technosf » Sun Oct 18, 2015 10:08 pm

I'm hoping it's just a new config param on systemd - One of the prior systemd updates that buggered my system was changes to networking, more specifically the router mode setting. Looking at notes for release 227, nothing stands out wrt SSH.

Has any one looked at the SSH log? I'm using certificate auth.

Can't wait to get home and break out my serial cable.
[size=85] MochaBin 5G || NSA325 [/size]
technosf
 
Posts: 147
Joined: Sat Jan 08, 2011 10:54 pm

Next

Return to General

Who is online

Users browsing this forum: No registered users and 21 guests