Blush!
This was a well-known networker bug, not an AdvFS bug even though it
started immediately after my switch to AdvFS.
"Jeffrey S. Jewett" <spider_at_umd5.umd.edu> was the first one to answer,
and in my case upgrading to 3.1A fixed the problem. I didn't get any
info on whether it is a client or server problem, so I upgraded both.
Last night my Unix savegroup went fine, but my NT savegroup failed so
badly that the server "crashed", i.e. all tools said "server not
available" even though nsrd & friends were around, and the NT savegroup
was running but not doing anything. Here's the shutdown:
# nsr_shutdown -a
nsr_shutdown will kill the following processes
1404 ?? 0:00.72 savegroup
29590 ?? 0:00.42 asavegroup
5949 ?? 2:00.08 nsrd
8007 ?? 2:12.55 nsrindexd
21118 ?? 11:27.88 nsrmmd
21803 ?? 8:03.93 ansrd
23352 ?? 15:04.66 nsrmmd
23937 ?? 1:33.59 nsrmmdbd
Do you want to continue? [Yes]?
* * * Killing savegroup
* * * Waiting for savegroup to die.
* * * Killing NetWorker daemons
kill: 21803: no such process
* * * daemons not dead yet.
17805 ?? 0:03.87 nsrindexd
* * * daemons not dead yet.
17805 ?? 0:06.97 nsrindexd
* * * daemons not dead yet.
17805 ?? 0:10.18 nsrindexd
* * * daemons not dead yet.
17805 ?? 0:15.72 nsrindexd
* * * daemons not dead yet.
17805 ?? 0:21.79 nsrindexd
* * * daemons not dead yet.
17805 ?? 0:40.73 nsrindexd
#
Funny, that nsrindexd started eating CPU like that...
Should I be worried?
Thanx to all you other guys, too:
Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>
Dave Golden <golden_at_falcon.invincible.com>
Client-Cerveza Computing 24-Jun-1996 0908 <farlee_at_decwet.ENET.dec.com>
Kurt Carlson <SXKAC_at_orca.alaska.edu>
--hl
Harald Lundberg <hl_at_tekla.fi>;Tekla Oy,Koronakatu 1,FIN-02210,ESPOO,FINLAND
tel +358-{0-8879449work,0-8039489fax,0-8026752,11-2418013res,50-5578303mob)
Received on Tue Jun 25 1996 - 09:04:49 NZST