banned_9-26-2021 @ 400000005e3b67fe29c95885 execl-envfile: fatal: unable to get value from line: [main]: Success I get this on my sshd log and I can't figure out what happened. One day was working the next it didn't. It denies service,
banned_9-26-2021 Name : sshd In tree : ssh Status : enabled, up (pid 14241) 1012 seconds Type : classic Description : ssh daemon Source : /usr/lib/66/service/sshd Live : /run/66/scandir/0/sshd Dependencies : sshd-log Optional dependencies : None External dependencies : None Start script : foreground { exec ssh-keygen -A } execl-cmdline -s { /usr/bin/sshd -f ${conf_file} ${cmd_args} } Stop script : None Environment source : /etc/66/conf/sshd Environment file : conf_file=!/etc/ssh/sshd_config cmd_args=!-D Log name : sshd-log Log destination : /var/log/66/sshd Log file : @ 400000005e3c11f338f077ae ${conf_file}: No such file or directory @ 400000005e3c11f439028fc1 ${conf_file}: No such file or directory @ 400000005e3c11f53912cb35 ${conf_file}: No such file or directory @ 400000005e3c11f639254082 ${conf_file}: No such file or directory @ 400000005e3c11f739393c67 ${conf_file}: No such file or directory @ 400000005e3c11f8393c96d8 ${conf_file}: No such file or directory @ 400000005e3c11f93959bbfe ${conf_file}: No such file or directory @ 400000005e3c11fa396ab2b7 ${conf_file}: No such file or directory @ 400000005e3c11fb397e6d6b ${conf_file}: No such file or directory @ 400000005e3c11fc398c5754 ${conf_file}: No such file or directory @ 400000005e3c11fd39972fbc ${conf_file}: No such file or directory @ 400000005e3c11fe39a586cd ${conf_file}: No such file or directory
banned_9-26-2021 obcore/66 0.2.5.0-2 (base s6-suite) [installed] small tools built around s6 and s6-rc programs observice/sshd-66serv 0.1.2-1 [installed] ssh service for 66 tools obcore/openssh 8.1p1-3 [installed] Premier connectivity tool for remote login with the SSH protocol
[deleted] Well, exactly the same versions on my side and my service is working. Last thing, last idea, check your right access on /etc/ssh folder and your sshd_config file. But your service is running ? Status : enabled, up (pid 14241) 1012 seconds
banned_9-26-2021 I did this, and I compared with other installations and they are identical. I think I know what it is but don't know how it is affecting sshd and not other things. Can execline be affected by a change in glibc gcc-libs gcc ? The new versions in testing are breaking sshd. I tried this on a vm just now, did all upgrades except those and sshd worked fine. If I upgrade those and reboot sshd refuses to work right.
banned_9-26-2021 confirmed, downgraded those 3 and rebooted and it is all fine Check fdmove functionality in a test machine, I think it is being affected by the new glibc (testing)
banned_9-26-2021 jean-michel wroteWell, exactly the same versions on my side and my service is working. Last thing, last idea, check your right access on /etc/ssh folder and your sshd_config file. But your service is running ? Status : enabled, up (pid 14241) 1012 seconds Yes that is because I run it manually at the moment I posted this and forgot, sshd run ok if you started it in a command line, it was sshd-66serv that is breaking it. Either fdmove or s6log is unhappy with testing/glibc gcc gcc-libs But it takes a reboot to be affected, this threw me off, because it broke the day after the update, when I rebooted.
banned_9-26-2021 https://git.archlinux.org/svntogit/packages.git/commit/?h=packages/openssh&id=462581bdef99db2e1d8dbc7d089365b0ffbd6fcc Maybe the error starts at ssh-keygen and causes the rest to malfunction, but I have no clue where to look for the error, not on the sshd log.
banned_9-26-2021 Finally I pinpointed the problem Openssh breaks with testing/glibc 2.31 Probably openssh and a whole bunch of other stuff will have to be recompiled before they reach stable, so expect a gigantic wave of arch upgrades in the coming days. Now they moved to 2.31 it doesn't take a reboot, this seems like a more stable edition, you just downgrade to current core/glibc and openssh works again.
[deleted] Tested with my VM. Sshd works as expected. sudo 66-inservice -t system -o status,logfile sshd Status : enabled, up (pid 737) 206 seconds Log file : None
banned_9-26-2021 I meant with the updated glibc. The new edition moved to core from testing. The one I originally had problems with was like a pre-edition and I think it was patched. The new openssh needs the patch for the new glibc, I think.
[deleted] openssh has been updated. pacman -Qi openssh Name : openssh Version : 8.1p1-5 Sshd already works as expected sudo 66-inservice -o status,logfile sshd Status : enabled, up (pid 2061) 24 seconds Log file : None
banned_9-26-2021 got it thanks, meanwhile arch's openssh -4 worked, while obcore's -3 was failing. What does arch's version have different from the one you guys rebuilt. I spent sometime on the git and I couldn't find the difference, other than that glibc patch. With v.-3 and the new glibc sshd would be up and running no error but I couldn't log into it, it would deny access. Just installing the one from obcore and restarting it would fix the problem.