/etc/init.d/sshd restart
Stopping SSH Server… Not running. [ WARN ]
/etc/init.d/sshd start
completes without error
ssh: connect to host xxxxx port 222: Connection refused
Hmmm… do you have a file like this?
-rw-r--r-- 1 nobody nobody 0 Nov 16 17:17 /var/ipfire/remote/enablessh
Update to 155 didn’t take too particularly long, but have few addons.
Did not require a reboot. According to GUI, looks like 155 update “took”. No ALG options in Firewall Options, for example.
No SSH. I changed from port 22 to port 222 in GUI and back. No joy.
No, but:
less /var/ipfire/remote/settings
ENABLE_SSH_KEYS=off
ENABLE_SSH_PASSWORDS=on
ENABLE_SSH=off
ENABLE_SSH_PORTFW=off
I would suggest to establish a summary page, listing and linking together all known issues of both stable and testing releases here in this forum, so IPFire users do not have to check for and read through all postings and bugzilla reports to get an idea what’s going on…
Rebooted after 155 update. Would not reboot from console. /sys/initctl (?) error or similar. Soft reset.
On reboot SSH and haproxy fail. Console message on boot screen is "/lib/libcrypt.so.1: Version ‘XCRYPT_2.0’ not found.
I suggest editing /var/ipfire/remote/settings and change ENABLE_SSH=off to ENABLE_SSH=on
Then:
touch /var/ipfire/remote/enablessh
chmod 644 /var/ipfire/remote/enablessh
chown nobody:nobody /var/ipfire/remote/enablessh
/etc/init.d/sshd stop
/etc/init.d/sshd start
I’m just stabbing in the dark, but am curious to know if these actions have any effect.
Thanks!
/etc/init.d/sshd start
then produces:
Starting SSH Server…
/usr/sbin/sshd: /lib/libcrypt.so.1: version `XCRYPT_2.0’ not found (required by /usr/sbin/sshd) [ FAIL ]
Not surprisingly, ssh to IPFire still results in “connection refused”
1 Like
OK.
/etc/init.d/sshd stop
rm /lib/libcrypt.so.1 (It’s a symlink.)
ln -s /usr/lib/libcrypt.so.1 /lib/libcrypt.so.1
/etc/init.d/sshd start
And we’re back in the saddle again. SSH working here.
Seems to be a common error.
3 Likes
Should have replied to you.
Remove libcrypt.so.1 in /lib and sym link /usr/lib/libcrypt.so.1 into /lib
rm /lib/libcrypt.so.1
ln -s /usr/lib/libcrypt.so.1 /lib/libcrypt.so.1
/etc/init.d/sshd start
4 Likes
Thanks, that got SSH working.
I’ll now have to rig a kbd & monitor to the x86_64 mini PC, which normally runs “stable” but I had upgraded to “testing” for this issue.
Good to know. The fix is relatively easy if you’re at the console.
IMHO there is no way to downgrade if you not restore a backup of the disk. Reseting to stable is not a downgrade.
I have fixed the updater bugs in git but the builders are not finished yet. Fresh installations not have this problems.
https://nightly.ipfire.org/master/2021-03-12%2014:46:18%20+0000-103950e0/
I will post a note here after the rebuild is available.
2 Likes
Anyway, what I do for the return in 154…
-
In SSH / shell, edit the /opt/pakfire/db/core/mine and change current core update to an older one, for eg. :
nano /opt/pakfire/db/core/mine > 155 to 153 > Save and exit
or
echo 153 > /opt/pakfire/db/core/mine -
Go to GUI > Pakfire and run a new update from stable branch (today at 154)
Warning. Don’t set it back too far back. This can result in a messed up installation because you mix old and newer files. The core updates contain only the changed files from one version to another so set back to 153 and reinstall core154 not result in a correct core154 installation.
Set it back to 154 and reinstall core155.
Now the updater should work.
Ok, thanks !
Hello,
thanks for the fast fix!
And if you have no local access, this worked/helped for me (done on Windows system with cygwin):
mkdir -p opt/pakfire/db/core
echo 153 > opt/pakfire/db/core/mine
tar czf reload.ipk opt
Load the resulting reload.ipk in the GUI (System → Backup → Restore).
And redo the update.
Thanks again,
Uwe
1 Like
Top tip!
Saved me lugging keyboard and monitor to firewall.
SSH now working.
Thanks 
1 Like