Hello Centos,
I am getting an error that I am not familiar with when I restart ssh.
[root@virtcent01:~] #service sshd restart Stopping sshd: [ OK ] Starting sshd:WARNING: initlog is deprecated and will be removed in a future release [ OK ]
[root@virtcent01:~] #
I was just wondering if this is in the 'ignorable but annoying' category of things or whether there is something you can do about this. I've tried googling this error but haven't found any definitive answer here.
I've also tried grepping the conf file for some of the terms in the error message and not found anything.
I'm enclosing my conf file in case this has some clues I'm missing.
thanks in advance!
On Sun, Feb 20, 2011 at 04:19:23PM -0500, Tim Dunphy wrote:
I am getting an error that I am not familiar with when I restart ssh.
[root@virtcent01:~] #service sshd restart Stopping sshd: [ OK ] Starting sshd:WARNING: initlog is deprecated and will be removed in a future release
Have you replaced your sshd with a "generic" version?
I've also tried grepping the conf file for some of the terms in the error message and not found anything.
It's coming from the init script; check /etc/init.d/sshd
On 02/20/2011 03:22 PM, Stephen Harris wrote:
On Sun, Feb 20, 2011 at 04:19:23PM -0500, Tim Dunphy wrote:
I am getting an error that I am not familiar with when I restart ssh.
[root@virtcent01:~] #service sshd restart Stopping sshd: [ OK ] Starting sshd:WARNING: initlog is deprecated and will be removed in a future release
Have you replaced your sshd with a "generic" version?
I've also tried grepping the conf file for some of the terms in the error message and not found anything.
It's coming from the init script; check /etc/init.d/sshd
Also the following will help determine if you have normal centos packages or "something else":
rpm -q initscripts openssh-server
The result should look this for CentOS-5:
initscripts-8.45.30-3.el5.centos openssh-server-4.3p2-41.el5_5.1
On 02/20/11 2:36 PM, Johnny Hughes wrote:
Also the following will help determine if you have normal centos packages or "something else":
rpm -q initscripts openssh-server
The result should look this for CentOS-5:
initscripts-8.45.30-3.el5.centos openssh-server-4.3p2-41.el5_5.1
I believe that won't detect if package files have been overwritten by 'something else'... try...
# rpm -V initscripts openssh-server
if all files are unmolested, there should be no output. in my case, /etc/rc.d/rc.local has been tweaked, so I got...
# rpm -V initscripts openssh-server S.5....T c /etc/rc.d/rc.local
Hey guys,
good call! yes this is a custom ssh. It's a version that has LPK capabilities (LDAP public keys) included. It is the product of an rpm built from a spec file and tarball that was patched with LPK.
[root@LCENT01:~] #rpm -qa | grep ssh openssh-askpass-gnome-5.6p1-7.el5.em2 openssh-askpass-5.6p1-7.el5.em2 openssh-server-5.6p1-7.el5.em2 openssh-5.6p1-7.el5.em2 openssh-debuginfo-5.6p1-7.el5.em2 openssh-clients-5.6p1-7.el5.em2
so yes the speculation that the init script is to blame for this message is to blame for this is a good one. I'm including my init in the hopes that somebody with more experience of / knowledge of init scripts can point me in the right direction.
I certainly appreciate your help here. The centos list has gotten me over some pretty brutal humps in the past.
best!
On Sun, Feb 20, 2011 at 5:42 PM, John R Pierce pierce@hogranch.com wrote:
On 02/20/11 2:36 PM, Johnny Hughes wrote:
Also the following will help determine if you have normal centos packages or "something else":
rpm -q initscripts openssh-server
The result should look this for CentOS-5:
initscripts-8.45.30-3.el5.centos openssh-server-4.3p2-41.el5_5.1
I believe that won't detect if package files have been overwritten by 'something else'... try...
# rpm -V initscripts openssh-server
if all files are unmolested, there should be no output. in my case, /etc/rc.d/rc.local has been tweaked, so I got...
# rpm -V initscripts openssh-server S.5....T c /etc/rc.d/rc.local
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 02/20/2011 04:58 PM, Tim Dunphy wrote:
Hey guys,
good call! yes this is a custom ssh. It's a version that has LPK capabilities (LDAP public keys) included. It is the product of an rpm built from a spec file and tarball that was patched with LPK.
[root@LCENT01:~] #rpm -qa | grep ssh openssh-askpass-gnome-5.6p1-7.el5.em2 openssh-askpass-5.6p1-7.el5.em2 openssh-server-5.6p1-7.el5.em2 openssh-5.6p1-7.el5.em2 openssh-debuginfo-5.6p1-7.el5.em2 openssh-clients-5.6p1-7.el5.em2
so yes the speculation that the init script is to blame for this message is to blame for this is a good one. I'm including my init in the hopes that somebody with more experience of / knowledge of init scripts can point me in the right direction.
I certainly appreciate your help here. The centos list has gotten me over some pretty brutal humps in the past.
best!
It is not a problem .. the newer openssh is telling you that init log is not how things are going to be in the future. The reason you have this warning is that you are using a package that is not part of CentOS.
If you take a look at man sshd, there may be a switch you can pass in to make it not do that warning. You would have to edit the init.d startup script (probably /etc/init.d/sshd) if there is such a switch.
On Sun, Feb 20, 2011 at 05:16:47PM -0600, Johnny Hughes wrote:
If you take a look at man sshd, there may be a switch you can pass in to
No. This has nothing to do with sshd configuration.
As I previously said, the problem is purely 100% in the init script. The "generic" script from OpenSSH throws this warning with CentOS 5 because of this line in /etc/init.d/sshd
initlog -c "$SSHD $OPTIONS" && success || failure
The fix is to change it to $SSHD $OPTIONS && success || failure
On Sun, Feb 20, 2011 at 5:58 PM, Tim Dunphy bluethundr@gmail.com wrote:
Hey guys,
good call! yes this is a custom ssh. It's a version that has LPK capabilities (LDAP public keys) included. It is the product of an rpm built from a spec file and tarball that was patched with LPK.
[root@LCENT01:~] #rpm -qa | grep ssh openssh-askpass-gnome-5.6p1-7.el5.em2 openssh-askpass-5.6p1-7.el5.em2 openssh-server-5.6p1-7.el5.em2 openssh-5.6p1-7.el5.em2 openssh-debuginfo-5.6p1-7.el5.em2 openssh-clients-5.6p1-7.el5.em2
There are significant differences between OpenSSH 5.x, which is in RHEL 6 and which we can expect in CentOS 6, and OpenSSH 4.x as deployed in RHEL 5.
One rather startling difference is that remote SSH commands, such as 'ssh targethost echo $PATH', will not have the contents of your remote servers's ".bashrc" read in for bash users. The handling of .bashrc *CHANGED* between OpenSSH releases. This caused me a big problem a week ago. RHEL 6 addressed this by updates to bash, but we're very unlikely to see those backported to RHEL 5 and thus CentOS 5.
This kind of mismatched feature handling is why updating single components can become a very serious a nightmare in the long run.
-
John R Pierce -
Johnny Hughes -
Nico Kadel-Garcia -
Stephen Harris -
Tim Dunphy