Anyone else experiencing a problem adding clients in 6.1.3? We have a very annoying bug where we have to restart the Networker processes once we add a client else we get "client not registered" probl
Author: John Damm Soerensen <Johnds AT SGI DOT COM>
Date: Fri, 11 Jul 2003 16:37:39 +0200
I had same error message, it turned out to be bad reverse IP mapping in the nameserver. I did not restart Networker though. John Damm Soerensen Anyone else experiencing a problem adding clients in 6.
This is not a DNS issue, we always have proper resolution in place but still have the addition bug that I spoke of. -- Note: To sign off this list, send a "signoff networker" command via email to lis
Author: Yura Pismerov <ypismerov AT TUCOWS DOT COM>
Date: Fri, 11 Jul 2003 11:16:11 -0400
All those clients, do they have just one IP ? Sometimes you have to add all the relevant client names to the list of the client aliases because Networker is not able to figure them itself. Also, chec
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, st
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
Author: Yura Pismerov <ypismerov AT TUCOWS DOT COM>
Date: Fri, 11 Jul 2003 13:13:25 -0400
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. -- Yuri Pismerov, Sr. S
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 register
Author: Yura Pismerov <ypismerov AT TUCOWS DOT COM>
Date: Fri, 11 Jul 2003 13:57:19 -0400
May I ask what is being used for the DNS resolution test ? Do you use nslookup or you do it with "getent hosts hostname/IP" ? I hope you are aware that for accurate test you should use either getent
Author: Kent Holloway <Kent.Holloway AT ONVOY DOT COM>
Date: Fri, 11 Jul 2003 13:49:33 -0500
We have this problem also on 6.1.2 on Solaris 8. I have double and triple checked our DNS settings in resolv.conf and nsswitch.conf. Hosts added have both proper forward and reverse DNS and we need t
It wasn't a problem with my environment until upgrading to 6.x. Not sure why nslookup is considered unreliable when used to query internal DNS entries. But I'll verify that getent returns the proper
Donovan Looks like you are running into a known issue, as found in the release notes: http://web1.legato.com/infodev/publications/NetWorker/UNIX/6.1.3/uxrs.pd -- Unable to Backup Remote Clients After
Author: Kent Holloway <Kent.Holloway AT ONVOY DOT COM>
Date: Fri, 11 Jul 2003 14:15:02 -0500
We have the same issue but are not running 6.1.3 (Running 6.1.2 instead..) Donovan Looks like you are running into a known issue, as found in the release notes: http://web1.legato.com/infodev/publica
Hi Kent, The problem was not seen in 6.1.1, but was found in 6.1.2 and 6.1.3. Cheers Patrick Terry LEGATO Systems, Inc Senior Technical Marketing Engineer LCNS, LEGATO Certified NetWorker(r) Speciali
Author: George Sinclair <George.Sinclair AT NOAA DOT GOV>
Date: Fri, 11 Jul 2003 15:43:18 -0400
True enough. And with all the horror stories I've heard about 7 and 6.1.3, et al, I'm really glad we've stayed with 6.1.1. It's reasonably tame. George -- Note: To sign off this list, send a "signoff
Yes. I did start a thread about it earlier myself. Someone suggested that one should try adding the necessary data to the host file on the client and the server, however it doesn't seem to give any e
One could expect the following from a good software manufacturer: * Creating bugfixes for releases made before the release reaches end of sales/end of support, which should be at least 2-3 years afte
Author: "Wood, R A (Bob)" <WoodR AT CHEVRONTEXACO DOT COM>
Date: Mon, 14 Jul 2003 09:14:21 +0100
George, I'd be interested to hear what horror stories you have heard about 7. Care to share them? Bob True enough. And with all the horror stories I've heard about 7 and 6.1.3, et al, I'm really glad
Author: Davina Treiber <Treiber AT HOTPOP DOT COM>
Date: Mon, 14 Jul 2003 08:15:17 +0100
One could expect the following from a good software manufacturer: * Creating bugfixes for releases made before the release reaches end of sales/end of support, which should be at least 2-3 years afte
Author: Davina Treiber <Treiber AT HOTPOP DOT COM>
Date: Mon, 14 Jul 2003 07:59:39 +0100
Not sure why nslookup is considered unreliable when used to query internal DNS entries. But I'll verify that getent returns the proper entries when I have a problem adding my next client. However, if