SRC daemon Error

[InduPramod]

Hi,

I reboot my machine everyday. After the morning reboot the nfsd daemon doesnot start up.

But if I reboot manually after 3 hours the daemon is been started and if I start the daemon startsrc -s nfsd it starts without any problem. Below are the following error which I see on the errpt -a.

Resource Name: SRC

Description
SOFTWARE PROGRAM ERROR

Probable Causes
APPLICATION PROGRAM

Failure Causes
SOFTWARE PROGRAM

Recommended Actions
PERFORM PROBLEM RECOVERY PROCEDURES

Detail Data
SYMPTOM CODE
0
SOFTWARE ERROR CODE
-9053
ERROR CODE
2
DETECTING MODULE
'srcmstr.c'@line:'529'
FAILING MODULE


Can someone give me a suggestion to get over this. I would appreciate it.

Thanks
Indu

 

[d3vzero]

Hi Indu,

I would have a quick look at your /etc/inittab file.

Its posible that your system is set to try and bring up nfs, prior to bringing up some resource that nfs depends on (like SRCMaster or TCP Network).

Have a look at the startup order in your /etc/inittab file, and make sure that rcnfs is preceeded by rctcpip (which is preceeded by srcmstr).

Brgds.

____________________
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debuging Mondays code.

 

[InduPramod]

Hi,

I checked the /etc/inittab, it looks like this

srcmstr:2:respawn:/usr/sbin/srcmstr # System Resource Controller
rctcpip:2:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons
rcnfs:2:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons

Yesterday the nfsd daemon didn't start and ?I had to start manually.

Today the nfsd daemon and rpc.mountd didn't start. I had to starr manuallu. When i start manually there is no error also.

Can someone give me a solution for this problem.

brgds

 

[d3vzero]

Hi Indu,

You will need to find the error output of the rc.nfs script (/dev/console), to find the nature of the failure.

You could use "lscons" to display the location of your Console file. If it points to a file, go to its directory and look at that file, and any others with similar names.

You could also look for the rc.nfs error output in the output from commands like :-

alog -t boot -o
alog -t console -o

Another thing you could try is, when trying to restart the nfs deamons in the morning, instead of using startsrc use the /etc/rc.nfs script directly (and view its output/errors onscreen). If it fails, then use the startsrc command to start the nfs processes.

If your manual exec of /etc/rc.nfs does not work, then I would suspect a problem with either the script, or ODM defs, or something else the script relies on.

If your manual exec of /etc/rc.nfs does work (without errors) then I would suspect its a timing issue in the boot process with respect to onlining of a resource that the nfs startup/process requires.

Let us know what you find.

BRgds.

____________________
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debuging Mondays code.