Hi The subject says it all. I checked yast xinetd and the service was missing. The package is installed. I tried looking in the admin guide and while they do a nice job explaining how sshd works I can't find out where they tell us how to start it. I have tried scanning the port just to see if it is already running and I get a connection refused. I have not started the firewall yet. In the firewall section of yast I can see where we are supposed to allow ssh but if it isn't running??? -- 100% Linux Only 100% GPL tools were used in the generation and posting of this message. Registered Linux User #249090
On Friday 05 November 2004 14:29, Xaos Katawin wrote:
Hi
The subject says it all. I checked yast xinetd and the service was missing. The package is installed. I tried looking in the admin guide and while they do a nice job explaining how sshd works I can't find out where they tell us how to start it. I have tried scanning the port just to see if it is already running and I get a connection refused. I have not started the firewall yet. In the firewall section of yast I can see where we are supposed to allow ssh but if it isn't running???
-- 100% Linux Only 100% GPL tools were used in the generation and posting of this message. Registered Linux User #249090
Try this chkconfig --add sshd if you have just installed it. then chkconfig sshd on and then /etc/init.d/sshd start good luck! -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
Hi,
On Fri, 5 Nov 2004 14:29:59 +0200
Xaos Katawin
Hi
The subject says it all. [...]
Try: # /etc/init.d/sshd start Or: # rcsshd start If you want to start automatically on boot, try: # chkconfig sshd on HTH, -- - E - on SUSE 9.1 | blackbox 0.65 | copperwalls was here ;) "By iron, iron itself is sharpened. So one man sharpens the face of another." - Proverbs 27:17
On Friday 05 November 2004 13:29, Xaos Katawin wrote:
Hi
The subject says it all. I checked yast xinetd and the service was missing. The package is installed. I tried looking in the admin guide and while they do a nice job explaining how sshd works I can't find out where they tell us how to start it. I have tried scanning the port just to see if it is already running and I get a connection refused. I have not started the firewall yet. In the firewall section of yast I can see where we are supposed to allow ssh but if it isn't running???
Use YaST's runlevel module. Alternatively, you could start it manually (provided sshd is installed) by issuing: rcsshd start and, if that succeeds: insserv sshd to include it in the boot process. Not everything runs as an x?inetd service. ;) Cheers, Leen
Well I can get the daemon started and I even saw the boot message showing that it is indeed started but every time I try to connect I get: ssh: connect to host xxx.xxx.xxx.xxx port 22: Connection refused I am tearing my hair out and there isn't much of that left. -- 100% Linux Only 100% GPL tools were used in the generation and posting of this message. Registered Linux User #249090
The Friday 2004-11-05 at 18:18 +0200, Xaos Katawin wrote:
Well I can get the daemon started and I even saw the boot message showing that it is indeed started but every time I try to connect I get:
ssh: connect to host xxx.xxx.xxx.xxx port 22: Connection refused
Firewall? Have you tried locally on the same machine? What user are you trying with? Root will not work. Logs at the server? Iptraf at the server? -- Cheers, Carlos Robinson
On Friday 05 November 2004 17:18, Xaos Katawin wrote:
Well I can get the daemon started and I even saw the boot message showing that it is indeed started but every time I try to connect I get:
ssh: connect to host xxx.xxx.xxx.xxx port 22: Connection refused
I am tearing my hair out and there isn't much of that left.
-- 100% Linux Only 100% GPL tools were used in the generation and posting of this message. Registered Linux User #249090
2 questions: 1) started is not same as running... what does "rcsshd status" say? 2) Is the firewall blocking port 22? Simple test: In shell type "tail -f /var/log/messages" (This will show you all new messages in file) then in another shell try "ssh 127.0.0.1" See what messages are written to /var/log/messages if any... Jerry
On Friday 05 November 2004 17:18, Xaos Katawin wrote:
Well I can get the daemon started and I even saw the boot message showing that it is indeed started but every time I try to connect I get:
ssh: connect to host xxx.xxx.xxx.xxx port 22: Connection refused
I am tearing my hair out and there isn't much of that left.
This happened to me when on the remote I had an old public key sitting ~/.ssh/authorized_keys2 on the remote, trying to login with a newer key on the local machine. Just remove the old key from ~/.ssh/authorized_keys2 on the remote. Cheers, Leen
The Friday 2004-11-05 at 14:29 +0200, Xaos Katawin wrote:
The subject says it all. I checked yast xinetd and the service was missing. The package is installed. I tried looking in the admin guide and while they do a nice job explaining how sshd works I can't find out where they tell us how to start it. I have tried scanning the port just to see if it is already running and I get a connection refused. I have not started the firewall yet. In the firewall section of yast I can see where we are supposed to allow ssh but if it isn't running???
rcsshd status will tell you if it is running. Use "start" to start it. And in Yast, runlevel configuration, you can set the service to run allways; or use "chkconfig sshd on" manually. -- Cheers, Carlos Robinson
rcsshd status gives me a message that sshd is unused. rcsshd start gives the message "done" Trying to connect locally using localhost or the ip address gives the same old message. --
On Monday 08 November 2004 09:58 am, Xaos Katawin wrote:
rcsshd status gives me a message that sshd is unused.
rcsshd start gives the message "done"
Trying to connect locally using localhost or the ip address gives the same old message.
--
What does: ps aux | grep ssh show? (after you've issued rcsshd start)
On Mon, Nov 08, 2004 at 11:56:36AM -0500, Bruce Marshall wrote:
What does:
ps aux | grep ssh
show? (after you've issued rcsshd start)
root 6940 0.0 0.2 2596 700 pts/47 S+ 13:22 0:00 grep ssh rcsshd status shows: Checking for service sshd unused
On Tuesday 09 November 2004 12:25, Xaos Katawin wrote:
On Mon, Nov 08, 2004 at 11:56:36AM -0500, Bruce Marshall wrote:
What does:
ps aux | grep ssh
show? (after you've issued rcsshd start)
root 6940 0.0 0.2 2596 700 pts/47 S+ 13:22 0:00 grep ssh
rcsshd status shows:
Checking for service sshd unused
Okay, the service crashed... Check /var/log/messages for the reason why... Jerry
On Monday 08 November 2004 15:58, Xaos Katawin wrote:
rcsshd status gives me a message that sshd is unused.
rcsshd start gives the message "done"
Trying to connect locally using localhost or the ip address gives the same old message.
-- and what does rcsshd status say after it's started? Jerry
Xaos Katawin wrote:
Hi
The subject says it all. I checked yast xinetd and the service was missing. The package is installed. I tried looking in the admin guide and while they do a nice job explaining how sshd works I can't find out where they tell us how to start it. I have tried scanning the port just to see if it is already running and I get a connection refused. I have not started the firewall yet. In the firewall section of yast I can see where we are supposed to allow ssh but if it isn't running???
Did you enable it in the run level editor?
On Friday 05 November 2004 07:29 am, Xaos Katawin wrote:
Hi
The subject says it all. I checked yast xinetd and the service was missing. The package is installed. I tried looking in the admin guide and while they do a nice job explaining how sshd works I can't find out where they tell us how to start it. I have tried scanning the port just to see if it is already running and I get a connection refused. I have not started the firewall yet. In the firewall section of yast I can see where we are supposed to allow ssh but if it isn't running???
I believe you've been given these instructions before: Yast --> system --> runlevel editor --> enable sshd
Let's start from scratch:
First, check your firewall settings. SSHD listens on port number 22. Make
sure that this port is open.
Next, make sure the ssh daemon is running, by either turning it on via YaST
or using the rcsshd command. As root:
# rcsshd status
Checking for service sshd running
You can start it as:
# rcsshd start
You can then test it:
gaf@xxxx:~> ssh localhost
The authenticity of host 'localhost (127.0.0.1)' can't be established.
RSA key fingerprint is 4e:8f:9e:8a:c8:cc:c0:f9:3c:88:c5:ad:e9:79:34:d3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
Last login: Mon Nov 8 10:50:42 2004 from console
Have a lot of fun...
I have it working fine on my home system suse 9.1, my system at work, SuSE
9.2.
--
Jerry Feldman
Well to recap. Yes I have installed ssh. Yes I have enabled ssh in the run-level editor. I have issued rcsshd status with the resulting message "unused." I then used rcsshd start and the resulting message was "starting ssh." When I checked with ps aux, I don't see a process for sshd. I then checked rcsshd status once again and the message was still "unused." Neither root nor any local user can connect to port 22.
The Tuesday 2004-11-09 at 13:33 +0200, Xaos Katawin wrote:
Yes I have installed ssh. Yes I have enabled ssh in the run-level editor. I have issued rcsshd status with the resulting message "unused." I then used rcsshd start and the resulting message was "starting ssh." When I checked with ps aux, I don't see a process for sshd. I then checked rcsshd status once again and the message was still "unused." Neither root nor any local user can connect to port 22.
Then it crashed. You definitely have to look at the system logs to find out why. This is must in Linux for any service that is not behaving as you expect. -- Cheers, Carlos Robinson
participants (9)
-
- Edwin - -
Bruce Marshall -
Carlos E. R. -
Chadley Wilson -
James Knott -
Jerry Feldman -
Jerry Westrick -
Leendert Meyer -
Xaos Katawin