Date: Sat, 19 May 2001 19:44:59 +0200 (CEST) From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/27457: yppush fails when updating two or more slaves Message-ID: <200105191744.f4JHixo82799@curry.mchp.siemens.de>
next in thread | raw e-mail | index | archive | help
>Number: 27457
>Category: bin
>Synopsis: yppush fails when updating two or more slaves
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat May 19 10:50:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Andre Albsmeier
>Release: FreeBSD 4.3-STABLE i386
>Organization:
>Environment:
FreeBSD 4.3-STABLE FreeBSD 4.3-STABLE #56: Tue May 15 09:35:09 CEST 2001
One YP server, two (or more) slaves
>Description:
When updating the NIS databases on the slaves by running yppush
in /var/yp on the server, the clients get updated properly. However,
the calling yppush hangs:
root@server:/var/yp>yppush -vv -h spoolfix -h printfix amd.host
yppush: initiating transfer: amd.host -> pr (transid = 990293135)
yppush: pr has been called
yppush: checking return status: transaction ID: 990293135
yppush: transfer of map amd.host to server pr failed
yppush: status returned by ypxfr: Master's version not newer
yppush: initiating transfer: amd.host -> spoolfix (transid = 990293136)
yppush: spoolfix has been called
yppush: all jobs dispatched
yppush: spoolfix has not responded
yppush: pr has responded
yppush: 1 transfer still pending
[wait 1 to 2 minutes here]
yppush: timed out
yppush: warning: exiting with transfer to spoolfix (transid = 990293136) still pending
In the logfile of one client we see:
May 19 19:25:43 <daemon.notice> spoolfix ypxfr[4428]: callback failed: RPC: Timed out
May 19 19:26:15 <daemon.notice> spoolfix ypxfr[4429]: callback failed: RPC: Timed out
It seems that somehow the callback of the second slave doesn't
make it through to the server.
The problem already appeared as described in PR# 12496. It then
went away until the recent changes to libexec/rtld-elf/rtld.c
made appear it again.
>How-To-Repeat:
Use the newest FreeBSD 4.3-STABLE sources. Put two slave servers into
ypservers. Run yppush as above (with any map).
>Fix:
The following patch is no fix. It circumvents the problem but
I can't explain why :-)
--- libexec/rtld-elf/rtld.c.ORI Fri May 18 08:05:01 2001
+++ libexec/rtld-elf/rtld.c Sat May 19 19:39:04 2001
@@ -386,6 +386,8 @@
dbg("initializing key program variables");
set_program_var("__progname", argv[0] != NULL ? basename(argv[0]) : "");
+ set_program_var("environ", "dummy");
+ set_program_var("environ", "dummy");
set_program_var("environ", env);
dbg("initializing thread locks");
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105191744.f4JHixo82799>