Thread View: comp.sys.sgi.admin
2 messages
2 total messages
Started by Ori Degani
Thu, 07 Jan 1993 11:10
RPC.LOCKD can't find statd
Author: Ori Degani
Date: Thu, 07 Jan 1993 11:10
Date: Thu, 07 Jan 1993 11:10
62 lines
3292 bytes
3292 bytes
Hi,
I got this error message in my SYSLOG on the day I booted the machine.
--
Jan 4 10:48:37 marvin inetd[117]: /usr/etc/rpc.rwalld: No such file or directory
Jan 4 10:48:37 marvin inetd[117]: /usr/etc/rpc.rusersd: No such file or directory
Jan 4 10:48:37 marvin inetd[117]: /usr/etc/rpc.rquotad: No such file or directory
Jan 4 10:48:37 marvin inetd[117]: /usr/etc/rpc.sprayd: No such file or directory
Jan 4 10:48:37 marvin inetd[117]: /usr/etc/rpc.ypupdated: No such file or directory
Jan 4 10:48:37 marvin inetd[117]: /usr/etc/rpc.snoopd: No such file or directory
Jan 4 10:48:37 marvin inetd[117]: /usr/etc/cvpcsd: No such file or directory
Jan 4 10:48:37 marvin inetd[117]: /usr/etc/podd: No such file or directory
--
No lockd, or statd here
6 hours later:
--
Jan 4 16:50:30 marvin rpc.lockd[120]: cannot contact local statd
Jan 4 16:50:30 marvin rpc.lockd[120]: req discard due to status monitor problem
--
And this goes on and on... (every 2 seconds lockd looks for statd)
at 17:52 I tried to log in (I never noticed this I think)
--
[...]
Jan 4 17:52:47 marvin unix: Killing the input queue owner
Jan 4 17:52:47 marvin Xsession: ori: fatal IO error 32 (Broken pipe)
--
So I tried to log in again, and it worked...
Three days later:
--
Jan 7 12:43:40 marvin unix: WARNING: Process [Xsgi] pid 3058 killed due to insufficient memory/swap.
Jan 7 12:43:40 marvin unix:
Jan 7 12:43:39 marvin rpc.lockd[120]: req discard due to status monitor problemJan 7 12:43:42 marvin Xsession: ori: fatal IO error 32 (Broken pipe)
Jan 7 12:43:43 marvin rpc.lockd[120]: cannot contact local statd
Jan 7 12:43:43 marvin rpc.lockd[120]: req discard due to status monitor problemJan 7 12:43:44 marvin xdm[425]: Server for display :0 terminated unexpectedly: 2304
--
Those rpc.lockd[120] are always happening and I don't know if they have
anything to do with the problem...
Because I was kicked out of my session I investigated the SYSLOG, and
saw the rpc.lockd thing. So my questions are:
1) What is that rpc.lockd error, and why is it happening? I'm rebooting
the machine now, and hoping it will disappear, but still...
2) Why did I get logged out of the machine? (It _might_ be because
I'm using the new Lucid Emacs (19.3)).
3) Any connection between 2, and 3? Notice that I was logged out before
(January 4th), and didn't notice it.
Thanks,
Ori
--
| ---- Ori Degani
| |___ ori@eddie.technion.ac.il (Ship Computer on the HOG)
| | ori@marvin.technion.ac.il (Who else)
| ---- s2973229@techst02.technion.ac.il (Ech..)
--
| ---- Ori Degani
| |___ ori@eddie.technion.ac.il (Ship Computer on the HOG)
| | ori@marvin.technion.ac.il (Who else)
| ---- s2973229@techst02.technion.ac.il (Ech..)
Re: RPC.LOCKD can't find statd
Author: Dave Olson
Date: Sun, 10 Jan 1993 04:30
Date: Sun, 10 Jan 1993 04:30
52 lines
2752 bytes
2752 bytes
In <1993Jan7.111000.9089@discus.technion.ac.il> ori@marvin.technion.ac.il (Ori Degani) writes:
| Hi,
| I got this error message in my SYSLOG on the day I booted the machine.
| --
| No lockd, or statd here
Yes, but were they running (lockd obviously was, but how about statd)?
Note that the init.d/network script runs it only if it is present.
Neither rpc.lockd nor rpc.statd are started by inetd, they are started
from the network script if they are installed in the 'standard' place.
| 6 hours later:
| --
| Jan 4 16:50:30 marvin rpc.lockd[120]: cannot contact local statd
| Jan 4 16:50:30 marvin rpc.lockd[120]: req discard due to status monitor problem
Presumably, if this is the first message, then either statd just died,
or this was the first time lockd tried to contact statd (I don't know
enough about how lockd works to tell for sure).
If you are running 405A, there is a lockd patch in 405C for lockd,
but I don't know of one for statd dying.
| Jan 4 17:52:47 marvin unix: Killing the input queue owner
This message is printed when the vulcan death grip is used from the
console keyboard to kill the server (left ctrl, left shift, F12, keypad /,
all depressed simultaneously), and under no other circumstances.
The following message just means that the server exited.
| Jan 4 17:52:47 marvin Xsession: ori: fatal IO error 32 (Broken pipe)
| Jan 7 12:43:40 marvin unix: WARNING: Process [Xsgi] pid 3058 killed due to insufficient memory/swap.
This means you ran out of virtual memory. You need to run fewer/smaller
processes, buy more memory, or add more swap space.
| 2) Why did I get logged out of the machine? (It _might_ be because
| I'm using the new Lucid Emacs (19.3)).
I hope it doesn't use the key strokes I listed above!
| 3) Any connection between 2, and 3? Notice that I was logged out before
| (January 4th), and didn't notice it.
I doubt there is any connection, but nobody can say absolutely
positively for sure without a lot more info.
--
Let no one tell me that silence gives consent, | Dave Olson
because whoever is silent dissents. | Silicon Graphics, Inc.
Maria Isabel Barreno | olson@sgi.com
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads