Networker

Re: [Networker] Client Addition bug in 6.1.3

2003-07-11 13:26:53
Subject: Re: [Networker] Client Addition bug in 6.1.3
From: Joel Fisher <jfisher AT WFUBMC DOT EDU>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Fri, 11 Jul 2003 13:26:50 -0400
Sure has the symptoms of a DNS resolution problem... except that I can
resolve forward and reverse fine from both client and server.  Also why
would restarting Networker alone make the "not a registered client"
error go away?  There is a bug in the process of creating a new client.
Sometimes it works fine, other times it requires a initial host entry,
other times I have to restart Networker.  

Joel

-----Original Message-----
From: Yura Pismerov [mailto:ypismerov AT TUCOWS DOT COM] 
Sent: Friday, July 11, 2003 1:13 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Client Addition bug in 6.1.3

So it sounds like DNS resolution problem on the server side.
Besides nsswitch.conf I'd double check /etc/resolv.conf to ensure that
all the nameservers listed there are valid.



Joel Fisher wrote:
>
> We actually have 6.1.2, but I get this error quite frequently.  I've
> been able to "work around" it most of the time by adding a /etc/hosts
> entry for the client.  Then once the initial backup has run I can
remove
> that /etc/hosts entry.  Occasionaly I have to restart networker to get
a
> client added.
>
> One person on the list sent a suggestion on editing the
> /etc/nsswitch.conf file.  Check the archives.  I haven't tried it yet,
> but it seemed to work for him.
>
> Joel
>
> -----Original Message-----
> From: Donovan O'Brien [mailto:dobrien AT SIAC DOT COM]
> Sent: Friday, July 11, 2003 11:31 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] Client Addition bug in 6.1.3
>
> Most clients only have one IP address.  The others we add the alias to
> Networker (that brings up another bug with 6.1.3, if you have too many
> aliases and the nsr.res field spans more than one line, storage nodes
> fail
> to work, but that is another problem).
>
> Last night I added a client, its backup kicked off 6 hours later, that
> should be enough time for Networker to sync, and it failed.  This
> morning,
> I recycled the Networker processes then started another backup for
that
> same client which succeeded.
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via
email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Yuri Pismerov, Sr. System Administrator,
TUCOWS.COM INC. (416) 535-0123  ext. 1352

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=