From: Tru64 User (tru64user@yahoo.com)
Date: Fri Jul 11 2003 - 11:48:52 EDT
Hi ALL,
My original problem with multiple rdsym processes
starting seem to be occuring more frequently now, on
multiple machines. From time-to-time I would find::
root 436 1 0.0 19:49:08 ??
0:00.00 /usr/lbin/rdsym
root 1196 1 0.0 14:07:37 ??
0:00.00 /usr/lbin/rdsym
root 1348 1 0.0 19:48:41 ??
0:00.00 /usr/lbin/rdsym
root 1550 1 0.0 19:48:41 ??
0:00.00 /usr/lbin/rdsym
mostly btwn 60-70 such processes. Tracing them down,
it usually ends up to one user, at random, .
No idea why this is happening, but i know that killing
them all, and restarting kloadsrv takes care of the
problem.
Also, the associated user is not able to run ssh
anymore, since to create a random seed, it runs
several options of netstat. Netstat hangs when rdsym
processes show up.
Any other clues, b4 i open a software call?
OS: v4.0G Pk.#3, Alpha's 4100's
Permissions on rdsym OK as suggested by dk. Blinn.
_Thanks
--- Tru64 User <tru64user@yahoo.com> wrote:
> Much thanks to Dr. Tom Blinn and Joe Mario from HP.
> Restarting kloadsrv solved the weirdness going on.
> netstat is working once again. Theory of how it
> happened exists, no proof though (a user pasted big
> text file on command line, and immediately problems
> started...something there started it, probably!)
> ::starting kload server::
> /sbin/kloadsrv < /dev/console > /dev/console 2>&1
>
> ----------------------------------
> Text of entire dialog with the respondees::
> If I'm not mistaken, "netstat" itself may depend on
> "rdsym" and I know
> for sure it depends on being able to get kernel
> symbols through the
> kloadsrv service. I think kloadsrv is wedged on
> your
> system. I did
> find the source reference to "rdsym" and it's in a C
> library routine:
>
> ./usr/ccs/lib/libc/alpha/knlist.c: args[0] =
> "/usr/lbin/rdsym";
>
> and as it says in the source code,
>
> /*
> * The knlist() library function looks up addresses
> of
> kernel symbols.
> *
> * Return code:
> * -1 : unable to connect to kloadsrv, no lookup
> has
> been done.
> * 0 : all lookup has been successfully
> completed.
> * n : n is a positive integer. Some symbols are
> undefined.
> * n is the number of symbols that have
> failed
> in lookup.
> */
>
> and as it says in the knlist(3) reference page,
>
> RETURN VALUES
>
> The knlist() routine returns zero on success. The
> routine returns -1
> if it
> was unable to connect to the kloadsrv daemon. In
> this case, the
> routine
> was unable to determine any of the requested
> addresses. The routine
> returns a positive integer if it successfully
> finds
> some addresses
> and
> fails to find others. The integer value indicates
> the number of
> addresses
> knlist() was unable to return.
>
> if you are root, it talks to the kloadsrv directly,
> I
> think, but if you
> are not root, it tries to run "rdsym" in a
> subprocess
> and talk to it
> via
> pipes, and if you managed to run enough copies and
> the
> subprocessed did
> not go away, you'd kill yourself.
>
> Among the commands that invoke knlist() are these:
>
> nfsstat, pfstat, arp, ogated, rarpd, route,
> sendmail,
> srconfig,
> strsetup,
> trpt, and xntpd.
>
> Most of these, with the exception perhaps of
> sendmail
> under one or more
> of its aliases, would not normally be invoked by a
> non-privileged user.
>
> I'm guessing kloadsrv isn't running correctly on
> your
> system.
>
> Also, make sure rdsym is protected correctly; on my
> V4.0G system, it's
> got this setup:
>
> doctor[1682]> ls -l /usr/lbin/rdsym
> -rws--x--x 1 root bin 16384 May 14
> 2000
> /usr/lbin/rdsym
>
> in other words, it's setuid root (the library logic
> depends on it being
> running as root when it gets invoked).
>
>
>
=====
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:26 EDT