xinetd failed

I noticed that my server was taking a few more seconds than usual to start up.

This is after I did a “shutdown -h 0” twice. Someone told me its bad to do it if the gui is up. I was logged in through ssh…But since my server was on run level 5, it was at the GUI login screen at the console. Is it bad to do shutdown -h while kde is up?

I switched to run level 3 so that it would default to command line. Thats when I noticed xinetd failed to start. I uninstalled it and installed it right back. But now it doesnt even try to start at all. Is that service essential to the system if I am running apache and mysql?

Oh…and I am running opensuse 11.1

Nope. In your situation KDE is not even up because nobody is loged in, only the display manager is running. But it does not matter even when somebody is loged in. Well, (s)he may be furious and her/his work may be lost, but the system as such is not damaged.

You say xindetd failed to start. Was that an error, or did it simply not start. Why do you think it should start? have you configured a service for it?
(Remember that xinetd refuses to start when it has nothing to do. It is like me, not coming out of my bed when there are no questions on the Forums lol! )

lol.

Well…

  • It just simply failed to start. When the server reaches the login prompt, you see “Failed” in red letters on xinetd.

  • I thought it should start because on my test server it starts up just fine. My test server is an exact config of my live server. So I thought something might be wrong since it failed on the live server.

But no, I have not configured a service for it. (at least not to my knowledge)

The only services I configured are Apache and MySQL.

Then you most probably have nothing to do for xinetd. Though I agree with you that it is strange to display a failed.

Dit you browse through

dmesg | less

to see if there is more info?

Also there is YaST > Network Services > Network services (xinetd) where you can see if anything is switched on.

And there is YaST > System > System services (Runlevel) where you can see if xinetd is switched on. When there is nothing switched ion in the first, you can switch of in the second. I hope there will be no annoying failed after that.

Since I had uninstalled it and reinstalled it, I do not get a failure. But the service doesn’t even try to start at all now.

I checked the config and it’s disabled now. Probably better since it appears I don’t need it.

Thanks! You were very helpful.:slight_smile:

You are welcome.

Well, then let’s guess why it actually might have failed.

Maybe because of this?

 rcxinetd start ; tail -n 1 /var/log/messages
Starting INET services. (xinetd)                                                             **failed**
Mar 13 17:46:51 Fatboy xinetd[29853]: 29853 {init_services} **no services.** Exiting...

:smiley: