getmemwindow and files

[Jay Cantwell]

Hey everyone....I have 2 questions I need help with....

1st...what command can be used to find out which processes are using a particular file...

2nd...I am getting the following getmemwindow errors in my /etc/rc.log...

/usr/bin/getmemwindow[29]: cat not found
/usr/bin/getmemwindow[29]: awk not found

can anyone tell me whats happening here ???

thanks...Jay

[James R. Ferguson]

Hi Jay:

1. You can use 'fuser' (see man 1m 'fuser') to determine the processes used by a file or mountpoint.

2. The problem you report is symptomatic of a startup script that has not explictily set its PATH variable. At the least, the script should contain:

PATH=/usr/sbin:/usr/bin:/sbin

Regards!

...JRF...

[Jay Cantwell]

Thanks James....would this most likely be an
Oracle script or one of the many system scripts...is there a way to find out what might be the process causing my problem ??

Jay

[Darrell Allen]

Hi Jay,

I think rc.log lists each rc file's name as it begins to execute that file. Can you tell from rc.log what's calling getmemwindow? In any event, since it's from an rc file:
cd /sbin
grep getmemwindow rc?.d/*

Darrell

[Bill Hassell · Accepted solution]

/usr/bin/getmemwindow is a script and the error is found on line 29. However, $PATH is normally set to include /usr/bin but apparently $PATH has been seriously corrupted. Troubleshooting will have to start from the top down: trace the top level script using the -x option (if the script is ksh, then start it with: ksh -x script_name 2>&1 | lp -d

This will show all the steps in the current script...look for problems. Any errors that show up will appear in sequence where subscripts and processes were started, so you work your way down. If you know the parent-child relationship of all the scripts, I would search for getmemwindow and also PATH.

[Jay Cantwell]

Bill....could you help me a little further...
what command would I use to do this...and would I use this on each script mentioned in the rc.log as the system was coming up ??

thanks Jay

[James R. Ferguson]

Hi (again) Jay:

OK. Look at /etc/rc.log (where you first see the errors). You are looking for something like:

'Output from "/sbin/rc3.d/S999mything start":'

...under which you see something like:

'/usr/bin/getmemwindow[29]: cat not found'

..."/sbin/rc3.d/SSSmything" is a link to the script you want to examine. Do:

# ls -l /sbin/rc3.d/S999mything

...to expose the link (for instance):

# /sbin/init.d/mything

Then, in /sbin/init.d/mything add at least, a PATH statement containing:

PATH=/usr/sbin:/usr/bin:/sbin

This should resolve your problem.

Regards!

...JRF...

[Jay Cantwell]

James...I understand what you are saying. However, all my scripts have a PATH statement in them. I have attached my rc.log. Please take a look and let me know what you think. It is quite big (200k) because of the errors.

Thanks...Jay

[Darrell Allen]

Hi Jay,

You've got a bunch of errors in your rc.log.

The first shows up in the output from /sbin/rc1.d/S112kminit. Notice the _______________not found. Looks like you may have added ______________ as a comment line in a bunch of rc scripts but forgot to put a "#" at the beginning of the line. That's a minor problem.

Why are so many of your rc scripts trying to add routes? It seems that all those rc scripts with _____________ lines that should be comment lines are also trying to add routes.

As far as the getmemwindow problems, I'm guessing they are from /sbin/rc3.d/S933filerep which shows:
Execution error : file 'rd_replicator'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)

The oracle start up needs work also.

I'd start with the simple (?) things first: take care of the ___________ lines and figure out the cause of the route adds.

After cleaning that up perhaps you can re-post rc.log and go from there.

Darrell

[James R. Ferguson]

Hi Jay:

From your /etc/rc.log output, it appears that you may have a file that doesn't belong in the '/etc/rc.config.d' directory. This directory is designed to hold files containing configuration variables (only) for startup and shutdown scripts (see the comments in '/etc/rc.config').

To help locate any problems in this directory, do this and post the output:

# sh -vx /etc/rc.config 2> /tmp/rc.config.out

Regards!

...JRF...