Networking Forums

Networking Forums > Computer Networking > Linux Networking > ypserv Error #-3 key lookup failure

Reply
Thread Tools Display Modes

ypserv Error #-3 key lookup failure

 
 
Lucas Carey
Guest
Posts: n/a

 
      08-18-2003, 09:14 AM
Hi,
I'm having trouble getting clients to recognize all of the keys in my
automount map. I distribute a map auto.LinuxMaster which the linux clients
are configured to read as the master map. This map refers to two other
maps, auto.users (x-platform) and auto.LinuxDirect, linux specific NFS
mounts. auto.users works fine and auto.LinuxDirect worked fine from our
old Tru64 NIS server, which is about to die. I replaced the machine with a
RedHat 9.0 (same as all other linux boxes) and the auto.LinuxDirect map
seems to be having issues.

NISmaster::~/ {33}# ypcat -k auto.LinuxDirect
Tru64_local runt:/usr/local
Tru64Docs eve:/usr/share/doclib/online
linux_local sloppy:/usr/local
src odd:/src
hunchback hunchback:/Volumes/Data

NISmaster::~/ {34}# ypmatch -k linux_local auto.LinuxDirect
linux_local sloppy:/usr/local

NISmaster::~/ {35}# ypmatch -k src auto.LinuxDirect
Can't match key src in map auto.LinuxDirect. Reason: No such key in map

if I run ypserv -d I get the following output(s/ipaddy/NISmaster/g):
connect from NISmaster
ypdb_open("flytheory", "passwd.byuid")
Found: flytheory/passwd.byuid (0)
ypdb_close() called
-> Value = "lcareywdhash:249:200:Lucas Carey:/users/lcarey:/usr/local/bin/tcsh"
ypproc_all_2_svc(): [From: NISmaster:35677]
domain = "flytheory"
map = "auto.LinuxDirect"
connect from NISmaster
ypdb_close_all() called
ypdb_close_all() called
ypdb_open("flytheory", "auto.LinuxDirect")
->Returning OK!
Opening: flytheory/auto.LinuxDirect (0) 80565e0
-> First value returned.
ypdb_close() called
sig_child: got signal 17
pid=798
children = 0
ypproc_domain("flytheory") [From: NISmaster:832]
connect from NISmaster
-> Ok.
ypproc_match(): [From: NISmaster:32797]
domainname = "flytheory"
mapname = "auto.LinuxDirect"
keydat = "linux_local"
connect from NISmaster
ypdb_open("flytheory", "auto.LinuxDirect")
->Returning OK!
Opening: flytheory/auto.LinuxDirect (1) 80bd970
ypdb_close() called
-> Value = "sloppy:/usr/local"
ypproc_match(): [From: NISmaster:32797]
domainname = "flytheory"
mapname = "auto.LinuxDirect"
keydat = "src"
connect from NISmaster
ypdb_open("flytheory", "auto.LinuxDirect")
Found: flytheory/auto.LinuxDirect (0)
ypdb_close() called
-> Error #-3
ypproc_match(): [From: NISmaster:32797]
domainname = "flytheory"
mapname = "auto.LinuxDirect"
keydat = "src"
connect from NISmaster
ypdb_open("flytheory", "auto.LinuxDirect")
Found: flytheory/auto.LinuxDirect (0)
ypdb_close() called
-> Error #-3

What is Error #-3, and why am I getting it? Everything worked so well in
Tru64. All of the other maps work fine, even other non-standard ones (like
the master map that refers to this one).
any ideas?
thanks
-Lucas
 
Reply With Quote
 
 
 
 
Lucas Carey
Guest
Posts: n/a

 
      08-18-2003, 05:05 PM
On Mon, 18 Aug 2003 05:14:07 -0400, Lucas Carey wrote:
> I'm having trouble getting clients to recognize all of the keys in my
> automount map. I distribute a map auto.LinuxMaster which the linux clients
> are configured to read as the master map. This map refers to two other
> maps, auto.users (x-platform) and auto.LinuxDirect, linux specific NFS
> mounts. auto.users works fine and auto.LinuxDirect worked fine from our

[cut]

Problem solved. I rebuilt the maps and everything worked. Must have been a
cruupot db file.

 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Reverse lookup failure Allan Butler Linux Networking 6 09-18-2005 05:57 AM
DNS lookup error Monster Linux Networking 4 01-23-2005 12:31 PM
ypserv question skwork Linux Networking 3 10-21-2004 09:23 AM
hostname lookup failure Patrick Linux Networking 2 07-28-2004 08:46 PM
Error 768 - failure to encrypt Todd hobdey Windows Networking 6 01-27-2004 05:18 AM



1 2 3 4 5 6 7 8 9 10 11