Thanks for the quick response John. I used that title to get attention,
did it work?  :-) This has been a real pain to get working, seems like
it was fine with 98 and NT, but 2000 has thrown a wrench in the works.

To answer some of your questions:

It doesn't happen on all W2K hosts, but when it starts it keeps doing it.
I swapped some W2K hosts from a different config and neither worked on
each others configs, where the ones on the other config *were* working.

I am waiting to upgrade when my new server arrives, so maybe the problem
will not follow. I will also try your suggestion about catching the 
processes in the act, that could prove interesting. I will also up the
timeout to see what effect that has.

Thanks for the advice!

Terri


John R. Jackson wrote:
> 
> >I'm getting this on several of my Win2K clients:
> 
> Ummm, how is it you can put "Easy question" and "Win2K" in the same
> letter?  :-)
> 
> >mordor     //bali/personal$ lev 0 FAILED [missing result for //bali/personal$ 
> >in mordor response]
> >
> >This hasn't always happened with them.  ...
> 
> Does it happen for a given PC some of the time but not others?  Or once
> it starts happening with a particular host does it keep doing it?
> 
> >This is Amanda 2.4.1p1 ...
> 
> The first thing I'd suggest is upgrading mordor to 2.4.2p2 or later.
> Among other things, the logging is much better for tracking problems.
> 
> Whether you do that or not, you need to catch one of the smbclient
> commands in action (/tmp/amanda/sendsize*debug) to see what it tried
> to do.  Building with --with-pid-debug-files makes this much easier,
> although you have to clean out /tmp/amanda by hand once in a while
> (all of this is better in 2.4.2p2 and later).
> 
> This message comes from planner when it does not get an estimate back
> from a client.  It could just be that the client is taking a long time
> (that's another thing that's better with 2.4.2 -- smbclient is run with
> "du" instead of "dir" and is much faster), in which case cranking up
> etimeout in amanda.conf might help.
> 
> If more than one machine has Samba installed (i.e. something other
> than "mordor"), you might try spreading the load by changing disklist.
> Note that those PC's will then look "new" to Amanda and so full dumps
> will be required to get started unless you mess around with the database.
> 
> >Terri Eads
> 
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
> 

Reply via email to