Re: Suse 10 problems - SSH

Thanks Peter,

On Nov 28, 5:50 pm, Peter Terpstra <pe...@xxxxxxxxxxxxxxxxxxxxx>
wrote:
jennlee_2 in
<a46c61c7-3a69-4416-9858-18dbd42ac...@xxxxxxxxxxxxxxxxxxxxxxxxxxx> :

Our Suse expert left recently, and now we've encountered a predicament
that we haven't been able to solve.

Are you looking for a new one? :-)

(speculation is because of the SSH issue it won't connect to get the
modules). Crontab jobs still execute.

In most cases YaST does not connect trough SSH, if there is a internet
connection it should work, maybe you can look what the installation sources
are and maybe add some.

But what kind of modules are you talking about? Kernelmodules are part of
the kernel.

I believe that at least one of the modules was a kernel module. I
don't have access myself at the moment and the staff that do are
currently out. I think there were four or five in total that it said
were damaged.


Anybody have anything to suggest? One of my group who is fairly
knowledgeable on other Linux flavors thinks that some automated update
was running Sunday night and the server crashed or failed in the
middle, corrupting modules (or at least the SSH stuff).

That's also the idea that i get but i can be wrong. In the
directory /var/log/YaST2 you should find logfiles which can explain what
happend. I'm curious.

I'll see what we can find in the YaST2 directory. Thanks for the
tip. I know there is something when the server is rebooted that it
even has trouble loading Yast, but they were eventually able to get
use of that.


Thanks for the posting.

P.


Thanks for your input Peter!
.