Is there a way to overcome DA incompatibility with RHEL/Centos 64bit 5.3 ?

In addition to Jeffs suggestions.. you mentioned
any new connections via SSH cannot be made
Click to expand...
are you able to connect to port 22 and get a failed password, or is port 22 completely dead?

After attempted to restart sshd through DA, check:
Admin Level -> Log Viewer -> /var/log/messages

Also make sure you didn't add "AllowUsers username" just like that. "username" is intended to be replaced by a username that exists on the system. If you add non-existant users to the AllowUsers option in the sshd_config, that could prevent sshd from loading up.
Note that there is an editor for the sshd_config via:
Admin Level -> File Editor -> /etc/ssh/sshd_config
if you need to make alterations.

John
 
Here is my vanilla RHEL 5.3 sshd_config file

PHP: 
#       $OpenBSD: sshd_config,v 1.73 2005/12/06 22:38:28 reyk Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

#Port 22
#Protocol 2,1
Protocol 2
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 768

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
SyslogFacility AUTHPRIV
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6

#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile     .ssh/authorized_keys


# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
GSSAPIAuthentication yes
#GSSAPICleanupCredentials yes
GSSAPICleanupCredentials yes

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication mechanism.
# Depending on your PAM configuration, this may bypass the setting of
# PasswordAuthentication, PermitEmptyPasswords, and
# "PermitRootLogin without-password". If you just want the PAM account and
# session checks to run without PAM authentication, then enable this but set
# ChallengeResponseAuthentication=no
#UsePAM no
UsePAM yes

# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#ShowPatchLevel no
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no

# no default banner path
#Banner /some/path

# override default of no subsystems
Subsystem       sftp    /usr/libexec/openssh/sftp-server
 
The only difference is that DA adds in:

AllowUsers root
AllowUsers admin


at the bottom of the file.

There must be a problem at some other level unfortuantly? I'm a diehard DA fan and want to keep using it, but every new server i'm buying uses 5.3 and so this incompatibility with 5.3 is becoming a problem and I dont want to switch control panel software.

Is anyone else out there able to get this working on RHEL 5.3?
 
DirectAdmin Support said:
In addition to Jeffs suggestions.. you mentioned are you able to connect to port 22 and get a failed password, or is port 22 completely dead?

After attempted to restart sshd through DA, check:
Admin Level -> Log Viewer -> /var/log/messages

Also make sure you didn't add "AllowUsers username" just like that. "username" is intended to be replaced by a username that exists on the system. If you add non-existant users to the AllowUsers option in the sshd_config, that could prevent sshd from loading up.
Note that there is an editor for the sshd_config via:
Admin Level -> File Editor -> /etc/ssh/sshd_config
if you need to make alterations.

John
Click to expand...

Port 22 is just completly dead to any new connections.

The connection I used to do the installation still stays open
 
Ok what a stupid solution.. I just did a 'yum update' and updated a few packages and now ssh works again! Maybee there was some bug in RHEL 5.3 that the DA installation triggered, which is now patched with yum. Who knows, but it works again. yay :)
 
You must log in or register to reply here.
Back
Top