|
|
|
|
| OpenSSH fails under Redhat 7.2 with glibc 2.2.4-32 |
|---|
|
Problem:
After update of glibc, the following errors show up in /var/log/secure
May 8 22:58:50 ### sshd[1968]: Accepted password for ### from #.#.#.# port 54427 ssh2
May 8 22:58:50 ### sshd[1973]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directory
May 8 22:58:50 ### sshd[1973]: lastlog_openseek: /var/log/lastlog is not a file or directory!
May 8 22:58:51 ### sshd[1968]: error: openpty: No such file or directory
May 8 22:58:51 ### sshd[1973]: error: session_pty_req: session 0 alloc failed
|
Solution:This is caused by a change in glibc. An explanation of the hows and whys can be found here:
http://www.patoche.org/LTT/kernel/00000172.html
Notably, the latest stock kernel for RH7.2 does NOT support UNIX98 ptys so you will have to recompile.
After making the changes outlined in that document, booting your new kernel etc, download the newest version of openssh for RH7.2 from ftp.redhat.com. (Include ALL of the related packages, openssh* in practice) Put them in a separate directory for easier handling.
You will probably have a difficult time installing them, especially if you have tried recompiling, reinstalling and generally messing around with openssh. First, carefully try to uninstall any and all installed versions of openssh. You probably will not be able to uninstall them all.
Then, do an " rpm -Uvh * --nodeps --force" to hammer in the RPM packages you just downloaded. Note that this WILL override things in a very dangerous manner, and this may cause things to break. Still... things didn't work when you started, right?
Anyway, this worked for me. Don't shoot me if it ruins your life. Good luck :-)
|
|
|
|
|
|
This is free technical advice without any warranties.
Use at your own risk. Solutions offered may not apply to your particular problem at all.
Opinions and views expressed in the articles are the authors' personal
and may not necessarily reflect or coincide with those of Ano-Tech Computers.
We take no responsibility if anything bad happens from following any of
the intructions given. If you don't understand and accept this, please
contact us for personal assistance instead.
To read our full disclaimer, go
here.
We welcome anyone who is willing to contribute to this public knowledge base,
contact siteadmin@atc.no
if you have information you would like to share. The idea is not to replace
the commercial support sites, but to publish those hard-to-find
solutions you've found yourself looking for over and over again.
Show all articles
