| View previous topic :: View next topic |
| Author |
Message |
fidel
Guru
Joined: 16 Jul 2004
Posts: 407
Location: CH
|
 Posted: Sat Aug 27, 2005 9:48 am Post subject: After world update -- no more ssh!... |
 |
|
I just updated my Gentoo box:
| Code: |
# emerge sync
# emerge -u --deep world |
After all configuration changes I rebooted the system. Unfortunately though I am not able to log in the box anymore. sshd gets marked as running (rc-status shows sshd running...)
I should be assuming that I now can log in the box.. but no, "connection refused"...
Does NOT show any ssh service!... --> 
When I try to stop the daemon
| Code: | | # /etc/init.d/sshd stop |
It fails to stop, showing something like
"stopping sshd !!"
What the heck could there be wrong?... I tried to remerge openssh two times, fooled around with the configuration file, nothing changes. In the logs, under /var/log/sshd nothing appears, actually, nothing gets written!..
Has anybody an idea what there could be wrong? (The firewall is configured correctly! I opened the port 22, besides, before the update it worked!..)
Thanks for any hints!
greets
fidel |
|
| Back to top |
|
 |
SinoTech
Advocate
Joined: 20 Mar 2004
Posts: 2579
Location: Neunkirchen / Saarland / Germany
|
| Posted: Sat Aug 27, 2005 9:56 am Post subject: |
|
|
Some time ago I've got a similiar problem. I've to rebuild a library ... but can't remember how it was named. Have you tried to run "revdep-rebuild" (It's in the package "gentoolkit") ?
Mfg
Sino
EDIT:
Think the package I had rebuild was "sys-libs/com_err". But I'm not completely sure, so if ssh still doesn't work, try a "revdep-rebuild". |
|
| Back to top |
|
|
fidel
Guru
Joined: 16 Jul 2004
Posts: 407
Location: CH
|
| Posted: Sat Aug 27, 2005 10:16 am Post subject: |
|
|
Thanks!.. unfortunately though revdep-rebuild doesn't find anything to fix. How could I find out which library it is?... hmm... could it help if I
?
... not that I really want to rebuild the entire system, if there is no other possibility though... will last for days!...
greets
fidel |
|
| Back to top |
|
|
SinoTech
Advocate
Joined: 20 Mar 2004
Posts: 2579
Location: Neunkirchen / Saarland / Germany
|
| Posted: Sat Aug 27, 2005 10:28 am Post subject: |
|
|
While updating my system, emerge spokes out some warnings about recompiling the "com_err" package. That's why I've done it.
Have you tried to recompile that package ?
And yes, a "emerge -e world" should solve your problem. But since it will took a long long time, you should first search for an easier way  .
Mfg
Sino |
|
| Back to top |
|
|
fidel
Guru
Joined: 16 Jul 2004
Posts: 407
Location: CH
|
| Posted: Sat Aug 27, 2005 10:42 am Post subject: |
|
|
I recompiled com_err, ran revdep-rebuild again und re-emerged openssh, still, exactly the same error, just no sshd!...  |
|
| Back to top |
|
|
SinoTech
Advocate
Joined: 20 Mar 2004
Posts: 2579
Location: Neunkirchen / Saarland / Germany
|
| Posted: Sat Aug 27, 2005 11:19 am Post subject: |
|
|
Try executing sshd without using the initscripts
Is there any output ? And if not, is there something about it in "/var/log/messages" ?
Mfg
Sino |
|
| Back to top |
|
|
fidel
Guru
Joined: 16 Jul 2004
Posts: 407
Location: CH
|
| Posted: Sat Aug 27, 2005 11:56 am Post subject: |
|
|
Thanks again!.. well, the file /var/log/messages doesn't exist on my install, I got a /var/log/everything/current though. There is nothing in there about sshd though.
doesn't seem to do anything, there is absolutely no output...
|
|
| Back to top |
|
|
SinoTech
Advocate
Joined: 20 Mar 2004
Posts: 2579
Location: Neunkirchen / Saarland / Germany
|
| Posted: Sat Aug 27, 2005 12:04 pm Post subject: |
|
|
Ok, the file ("/var/log/messages") is used by "syslog-ng" to store log messages. If you have another logging tool, it's possible the destination for the messages is different.
Anyway, I can't think for any reason why sshd won't work for you. Perhaps somebody else has an idea ?
Mfg
Sino |
|
| Back to top |
|
|
Kaapeli
Tux's lil' helper
Joined: 27 Dec 2004
Posts: 110
Location: Oulu, Finland
|
| Posted: Sun Aug 28, 2005 9:31 am Post subject: Re: After world update -- no more ssh!... |
|
|
| fidel wrote: |
When I try to stop the daemon
| Code: | | # /etc/init.d/sshd stop |
It fails to stop, showing something like
"stopping sshd !!"
|
Did it say something like this:
| Code: |
# /etc/init.d/ntpd stop
* Stopping ntpd ...
No /usr/sbin/ntpd found running; none killed.
* Failed to stop ntpd
|
If so, then I think what the problem might be. I just had similiar problem that I couldn't shut down the ntpd daemon, it was still running there but for some reason it couldn't find it. I searched the pid files from /var/run directory, the ntpd pidfile was missing. Well, no wonder it can't kill the process when the pid file doesn't exist anymore. Killing the running ntpd didn't help, since I couldn't start it again because it said it was still running. Odd?
So, the scripts seem to still think that ntpd is running even it's not. There must be some other location (besides of /var/run) where it stores information about which services are started. After fiddling around with the scripts for a while, I found out that var/lib/init.d/started directory has a symlink to each started service. So, I simply removed the ntpd symlink and tried starting ntpd again. Worked like charm 
So, in your case, removing var/lib/init.d/started/sshd link should make the scripts forgot that sshd is still running (when it's not) so it will be able to start sshd again.
I've had this sort of problems couple of times recently. I think the new baselayouts package has a bug that allows this to happend, I never had this sort of problems with the old baselayouts package.
_________________
Temperatures |
|
| Back to top |
|
|
bgmncwj
n00b
Joined: 31 May 2004
Posts: 13
|
| Posted: Mon Aug 29, 2005 2:38 am Post subject: |
|
|
| Just to save you some time in the future, instead of tracking down the symlink just run /etc/init.d/scriptname zap and it should reset the state. I don't have anything to add for the ssh problem though, sorry. |
|
| Back to top |
|
|
fidel
Guru
Joined: 16 Jul 2004
Posts: 407
Location: CH
|
| Posted: Mon Aug 29, 2005 7:38 am Post subject: |
|
|
Thanks for your answers! I actually "solved" the problem by
I now have a similar problem with mythbackend, I will try to remove the link in /var/lib/init.d/started/mythbackend and see if that removes the problem...
Thanks!
greets |
|
| Back to top |
|
|
|
Networking & Security
