I've noticed that restarting a failed group doesn't continue off of the work 
list, but instead generates a new one (subsequently backing up every client in 
the group, even the completed ones).
 
Also, I'm not sure if this has to do with the new nsrauth system, but I had 
gotten "authentication type 0 not adequate (1, 13)" errors whenever I tried to 
load volumes. A restart of the networker service fixed it, but I consistently 
got this error whenever the service is started for the first time (reboot). 
 
-merill

        -----Original Message----- 
        From: Legato NetWorker discussion on behalf of Oscar Olsson 
        Sent: Fri 3/3/2006 12:39 AM 
        To: NETWORKER AT LISTSERV.TEMPLE DOT EDU 
        Cc: 
        Subject: Re: [Networker] Networker 7.3 discovered bugs
        
        

        On Fri, 3 Mar 2006, Oscar Olsson wrote:
        
        OO> * The new nsrauth system, based on GSSAPI is severely broken. It 
easily
        OO> breaks/times out, probably a deadlock problem. This creates a 
partly hung
        OO> state which gets worse and worse until networker is restarted (new 
in 7.3
        OO> obviously)
        
        It seems that even if you turn it off, networker still tries to relable
        volumes that are already in the media database, but it claims that they
        are not, but fails to relabel the tape since theres already a volume 
with
        the same name in the media database. *sigh*
        
        //Oscar
        
        To sign off this list, send email to listserv AT listserv.temple DOT 
edu and type "signoff networker" in the
        body of the email. Please write to networker-request AT listserv.temple 
DOT edu if you have any problems
        wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
        via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER