xinetd and nfs services are not started !

shipon_97 · 11-03-2012, 01:03 AM

I am using Oracle enterprise Linux 5.4 . Suddenly I cannot start the services "xinetd" and "nfs" .

------------------------------------------------
[root@dataguard ~]# service xinetd restart

[root@dataguard ~]# service nfs restart
Shutting down NFS mountd: [FAILED]
Shutting down NFS daemon: [FAILED]
Shutting down NFS quotas: [FAILED]
Shutting down NFS services: [FAILED]
[root@dataguard ~]# service nfs restart
Shutting down NFS mountd: [FAILED]
Shutting down NFS daemon: [FAILED]
Shutting down NFS quotas: [FAILED]
Shutting down NFS services: [FAILED]
[root@dataguard ~]#
-----------------------------------

I also uninstall the both package and install the packages newly , but the problem not solved . And I dont find any log in the "/var/log/messages" file .

Your urgent help will be appreciated ... ...

linuxxer · 11-03-2012, 05:45 AM

Quote:

Originally Posted by shipon_97

And I dont find any log in the "/var/log/messages" file .

Check the /etc/rsyslog.conf file where daemon log messages goes.
Else try to get all log messages to any files (OR) terminal.
For example,

Code:

*.*                                    /dev/tty12

Now restart the rsyslogd, xinetd and nfsd server and check log messages,
Also check init-script of each server and check each and every steps.

jsaravana87 · 11-03-2012, 04:52 PM

I had faced out the nfs restart failure before,Im my case the cause was due to conflict between two nfs version

#rpm -qa | grep nfs -Check whether there is conflict between two nfs version

Look after the thread

http://www.linuxquestions.org/questi...led%5D-906297/

shipon_97 · 11-04-2012, 01:55 AM

thx arun ,

I remove the all rpm and install those newly but the problem not solved yet . My OS is 64 bit. Look @ the below output :

---------------------
[root@dataguard rpms]# yum list | grep nfs
nfs-utils.x86_64 1:1.0.9-42.el5 installed
nfs-utils-lib.x86_64 1.0.8-7.6.el5 installed
nfs-utils-lib-devel.x86_64 1.0.8-7.6.el5 installed
nfs-utils-lib.i386 1.0.8-7.6.el5 rhel-debuginfo
nfs-utils-lib-devel.i386 1.0.8-7.6.el5 rhel-debuginfo
nfs4-acl-tools.x86_64 0.3.3-1.el5 rhel-debuginfo
sblim-cmpi-nfsv3.x86_64 1.0.14-35.0.1.el5 rhel-debuginfo
sblim-cmpi-nfsv3-test.x86_64 1.0.14-35.0.1.el5 rhel-debuginfo
sblim-cmpi-nfsv4.x86_64 1.0.12-35.0.1.el5 rhel-debuginfo
sblim-cmpi-nfsv4-test.x86_64 1.0.12-35.0.1.el5 rhel-debuginfo
system-config-nfs.noarch 1.3.23-1.el5.0.1 rhel-debuginfo

[root@dataguard rpms]# yum list | grep xinetd
xinetd.x86_64 2:2.3.14-10.el5 installed

[root@dataguard rpms]# rpm -qa | grep nfs
nfs-utils-lib-devel-1.0.8-7.6.el5
nfs-utils-lib-1.0.8-7.6.el5
nfs-utils-1.0.9-42.el5
[root@dataguard rpms]#
----------------------------------

shipon_97 · 11-04-2012, 01:59 AM

Thx brother for ur reply but I don't understand how I generate the log when I restart/start/stop a service , like
"service xinetd restart"

My syslog file configuration is below .. ..

------------------------------------
[root@dataguard ~]# cat /etc/syslog.conf
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none /var/log/messages

# The authpriv file has restricted access.
authpriv.* /var/log/secure

# Log all the mail messages in one place.
mail.* -/var/log/maillog

# Log cron stuff
cron.* /var/log/cron

# Everybody gets emergency messages
*.emerg *

# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler

# Save boot messages also to boot.log
local7.* /var/log/boot.log
------------------------------------

linuxxer · 11-04-2012, 05:37 AM

@shipon_97

Quote:

Originally Posted by shipon_97

*.info;mail.none;authpriv.none;cron.none /var/log/messages

As per your rsyslogd configuration you will find required logs in /var/log/messages file.
If you are not able to see any log messages related with xinetd and nfsd,
then start the servers and check the output of

Code:

netstat -tan

I am not sure, but I think improper shutdown of server left some lock files on system.
So read the init-script and check each steps.

shipon_97 · 11-05-2012, 02:03 AM

I reboot the server but problem still exists here ..

server~]# netstat -nat
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:9514 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.244:427 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:427 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9515 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.244:1521 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6363 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.244:39155 192.168.0.244:1521 ESTABLISHED
tcp 0 0 192.168.0.244:39134 192.168.0.244:1521 ESTABLISHED
tcp 0 0 127.0.0.1:22801 127.0.0.1:9515 TIME_WAIT
tcp 0 0 127.0.0.1:33081 127.0.0.1:9514 TIME_WAIT
tcp 0 0 127.0.0.1:58258 127.0.0.1:9514 TIME_WAIT
tcp 0 0 192.168.0.244:1521 192.168.0.244:39134 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.244:39155 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53154 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53155 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53152 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53153 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53150 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53151 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53148 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53149 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53146 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.95:53147 ESTABLISHED
tcp 0 0 192.168.0.244:1521 192.168.0.31:2944 ESTABLISHED
tcp 0 0 :::13123 :::* LISTEN
tcp 0 0 :::9510 :::* LISTEN
tcp 0 0 :::14215 :::* LISTEN
tcp 0 0 :::28808 :::* LISTEN
tcp 0 0 :::14248 :::* LISTEN
tcp 0 0 fe80::e61f:13ff:fec1:5c:427 :::* LISTEN
tcp 0 0 ::1:427 :::* LISTEN
tcp 0 0 :::6987 :::* LISTEN
tcp 0 0 :::6988 :::* LISTEN
tcp 0 0 :::80 :::* LISTEN
tcp 0 0 :::15988 :::* LISTEN
tcp 0 0 :::15989 :::* LISTEN
tcp 0 0 :::22 :::* LISTEN
tcp 0 0 :::65144 :::* LISTEN
tcp 0 128 ::ffff:192.168.0.244:22 ::ffff:192.168.0.34:8634 ESTABLISHED

linuxxer · 11-05-2012, 06:06 AM

@shipon_97

Quote:

Originally Posted by shipon_97

tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN

I can say that, portmapper service is running.

But brother, I can't say which port is used by xinetd and nfsd.
It is totally depend upon server configuration.
So check configuration file of xinetd and nfsd, init-script and /etc/sysconfig files of servers,
to find out which port is used by servers.

By reading your first post, what I understand is:
Previously xinetd and nfsd servers was running and suddenly you are not able to start servers.

So Just to find out the problem,
I suggest,

Code:

*.*                                    /dev/tty12

Add this line into /etc/rsyslogd.conf

Run your system in SELinux permissive mode.

Code:

# setenforce 0
# sestatus

After that restart rsyslogd, xinetd and nfsd server.

Check logs at virtual console tty12,

Then check output of

Code:

# netstat -tan
# showmount -e
# rpcinfo -p

Also check /etc/hosts.allow and /etc/hosts.deny, /etc/services files.
If nfsd port no entry is not present in /etc/services then we can't start nfsd.
And check /etc/exports files.

chrism01 · 11-05-2012, 06:44 AM

The main nfs daemon listens on port 2049: /etc/services.
See Chap 18 http://www.linuxtopia.org/online_boo...ion/index.html