Pete Connolly wrote:

On Thursday 26 June 2008 13:04:43 Hudibras wrote:

...

When booting 11.0 it stops at sshd server, and it says "...dead" for a long time until it finally starts. What's wrong with sshd? It's the first time it appears this error with sshd. Any clue?

Many thanks again, Hudibras.

You should check your /var/log/messages file to see if there is any further information to help troubleshoot this.

Cheers

Pete

Try using the interactive option to bypass this script and as Pete said look at the logs and ssh logs (if configured), is the network active {OK} by the time your server gets to ssh? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hudibras wrote:

El jue, 26-06-2008 a las 10:31 -0400, Jose escribió:

...

Pete Connolly wrote:

...

On Thursday 26 June 2008 13:04:43 Hudibras wrote:

...

When booting 11.0 it stops at sshd server, and it says "...dead" for a long time until it finally starts. What's wrong with sshd? It's the first time it appears this error with sshd. Any clue?

Many thanks again, Hudibras. You should check your /var/log/messages file to see if there is any further information to help troubleshoot this.

Cheers

Pete

Try using the interactive option to bypass this script and as Pete said Yes, I was thinking over it. I'll do it.

look at the logs and ssh logs (if configured), is the network active {OK} by the time your server gets to ssh?

Yes, network is OK. A certain doubt I have is can be this produced by ntp?

Yes, ntp is the probable culprit if it is started either right before or right after ssh. The main reason is that /etc/ntp.conf is not configured by default. Specifically, you need to find a close ntp server and add its information to /etc/ntp.conf. example: ## ## Outside source of synchronized time ## ## server xx.xx.xx.xx # IP address of server server ntppub.tamu.edu server 129.119.80.126 server 207.55.146.19 Second reason, even if you have configured ntp with an outside server is when ntp is called before the network is started. This is the likely case when the network connection can be started and stopped by individual users using knetworkmanager or when the network connection is wireless. I both cases the processes that start immediately before or after ntp will often appear to have a long delay and receive what looks like a "Failed" status when in fact the process was successfully started and what you are actually seeing is the belated timeout of ntp and the ntp status of "Failed" overwriting the status line of a completely different process. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/28/2008 03:46 AM, Hudibras wrote:

The case is the "...dead" that appears is just after "sshd", and I cannot remember whether ntp booting process is the next after sshd. When booting I'll pay attention.

The ...dead usually happens when you crash or do not shutdown properly, leaving behind an old lock file or pid file. Many programs will be able to start anyway, but take longer, some can't and may need to be started manually after deleting the stale lock file, or invalid pid file. A proper shutdown shuts each program down and does not cause these types of problems. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

El vie, 27-06-2008 a las 15:30 -0400, Larry Stotler escribió:

On Thu, Jun 26, 2008 at 8:04 AM, Hudibras wrote:

...

When booting 11.0 it stops at sshd server, and it says "...dead" for a long time until it finally starts. What's wrong with sshd? It's the first time it appears this error with sshd. Any clue?

By default, the firewall is turned on, and the ssh port is blocked. do an:

/etc/init.d/sshd status

to see if it's actually turned on.

Yes! It's turned on. My issue was only when booting. As I have said to the list I'll reboot soon my machine and take a look. Possible problems will be solved one after another. My machine is a server and cannot reboot when I want. Many thanks again. Hudibras. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org