*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
** This bug has been marked a duplicate of bug 50430
NIS has problems starting before the network comes up
--
nis daemon fails to attach to domain the first time it is run in Gutsy
this seems a duplicate of #50430.
shortcutting NM by configuring your interface the old style in
/etc/network/interfaces should solve your problems for the time being.
--
nis daemon fails to attach to domain the first time it is run in Gutsy
https://bugs.launchpad.net/bugs/152794
You received
This bug has caused me a lot of confusion; on some machines the
YPBINDARGS=-no-dbus worked, on others it did not. Moving the positions
of startup scripts provided inconsistent results. It does not seem to
be a NIS bug at all, but is something to do with NetworkManager taking
too long to start
Confirmed on Hardy
need to modify /etc/default/nis and add --no-dbus options to have it at boot
time:
# Additional options to be given to ypbind when it is started.
YPBINDARGS=-no-dbus
** Changed in: nis (Ubuntu)
Status: New = Confirmed
** Changed in: network-manager (Ubuntu)
Sorry -- I intended to attach the above comment to bug #224828; I
apologize if it's completely unrelated.
--
nis daemon fails to attach to domain the first time it is run in Gutsy
https://bugs.launchpad.net/bugs/152794
You received this bug notification because you are a member of Ubuntu
Bugs,
I had this problem as well. By experimenting with the order in which
the scripts in /etc/rc2.d/ are run, I discovered that if the
/etc/init.d/nis script runs after the /etc/init.d/hal script, then NIS
starts correctly, while if nis runs before hal, then it does not. This
is apparently why the
** Changed in: network-manager (Ubuntu)
Assignee: Basilio Kublik (sourcercito) = (unassigned)
--
nis daemon fails to attach to domain the first time it is run in Gutsy
https://bugs.launchpad.net/bugs/152794
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes, that's a bug - if you ever need to specify -no-dbus to NIS it
indicates a problem. See the earlier comments in this bug for diagnostic
suggestions.
--
nis daemon fails to attach to domain the first time it is run in Gutsy
https://bugs.launchpad.net/bugs/152794
You received this bug
dbus/network manager integration is not new in Hardy - it has been
present for several Ubuntu releases with the NIS side of the code
unchanged. Many of the problems experienced in this area have stemmed
from Network Manager providing inaccurate information about the state of
the interface (these
Hm, that's interesting. Because when I turned of NetworkManager in past
releases, NIS just worked fine. In Hardy beta, when I turn of
NetworkManager NIS never comes up; I assumed that was because it was
listening on dbus for NetworkManager to tell it the interface was
available. I had to add
I believe this bug is fixed in Hardy. There's a new version of NIS's
ypbind that uses dbus to connect to networkmanager and doesn't bind
until after the network interface is brought up.
Once I modified my /etc/yp.conf to use an IP address instead of a
hostname (I know the comments there say you
I am seeing this issue on a fresh Hardy amd64 install. ypbind is
actually failing to register with portmap, even though portmap started
significantly earlier (nis startup is S18 in rc2, while portmap seems to
be starting as S43 in rcS; curiously, portmap is also listed as S17 in
rc2, but that's
OK, I found a different machine that doesn't use LVM, and was able to
complete an install, then set up nis. While I didn't set up a nis
login, I was able to use ypcat after a clean reboot, and a local login.
So apparently all is well.
This was using the daily build posted on 3/21. Daily torrents
Hm, well I tried. But I need to actually do an install in order to test
it. That is, I need to install, configure NIS, then boot to test.
But there is a rub. I can't install from the Live CD, because I use
LVM, which isn't supported. I have to use the alternate install, which
isn't
Hi there
do you still experience this issue with the current version of the
application?, could you please try to reproduce this using the live
environment of the Desktop CD of the development release - Hardy Heron.
Thanks in advance
** Changed in: network-manager (Ubuntu)
Importance:
István Váradi: Yes, that's exactly the problem: Network Manager reports
the interface as up before it is actually up.
--
nis daemon fails to attach to domain the first time it is run in Gutsy
https://bugs.launchpad.net/bugs/152794
You received this bug notification because you are a member of
I had the same problem since upgrading to Gutsy. The problem seems to be
that the dhcdbd (some DHCP daemon) is started after NIS and autofs, so
the interface has no chance to come up before init attempts to start
NIS. One solution seems to be to start dhcdbd earlier, i.e. rename
S24dhcdbd to
Master maps are important client side for autofs users - if autofs
starts up while unable to obtain the master map it may decide that there
are no NIS maps availiable and therfore never try to use them even when
they come on-line. If you are not using autofs then this subthread is
irrelevant.
--
The machine with this problem is not a master in my home setup - the
master is a headless server/router running debian etch. So distributing
maps is not an issue, I just need to attach to the domain.
I have a workaround though - I simply added /etc/init.d/nis restart as
a line in /etc/rc.local.
The above workaround didn't work for me (-no-ping), and this is a show
stopping bug for gutsy in my lab environment (mostly a mixture of dapper
and feisty workstations, using NIS). I've two workarounds; one is to
manually reload autofs on start, but this is impractical for the number
of
The above workaround will only help with NIS - things using NIS will
need additional work. If you are distributing your autofs master map via
NIS you could try distributing it statically and only use NIS for the
main maps - that might help and the master map normally doesn't change
too often. That
You could try adding -no-ping to YPBINDARGS in /etc/default/nis. This
will disable the Network Manager integration. See
http://www.sirena.org.uk/log/?p=41
--
nis daemon fails to attach to domain the first time it is run in Gutsy
https://bugs.launchpad.net/bugs/152794
You received this bug
OK, thanks. I am away from home at the moment, but will try this when I
get back home - I don't want to try rebooting remotely while this
problem exists.
Another thing - there are over 200 open bugs on network manager, and I
was unable to find one that was clearly linked to the issue you
Hrm. I can't find any of the relevant bugs in Network Manager either so
I've added Network Manager to this bug.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
nis daemon fails to attach to domain the first time it is run in Gutsy
James, in your case it does look like Network Manager is reporting that
the network is up before it actually is up. There are a series of
existing bugs against Network Manager discussing this issue which you
could subscribe to to track work on the problem.
--
nis daemon fails to attach to domain
Um, what about a work-around while I am waiting for the real fix? The
current state of this problem requires being at the console to manually
login as a non-nis user with sudo privileges, to rerun the nis startup
command, following any reboot.
--
nis daemon fails to attach to domain the first
will have to look at this when I am back at work next week
- Original Message
From: James R. Phillips [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, 20 October, 2007 12:03:21 AM
Subject: [Bug 152794] Re: nis daemon fails to attach to domain the first time
it is run in Gutsy
OK. BTW, it is /usr/bin/nm-tool, not /usr/sbin/nm-tool.
Output of first run (during boot)
==
NetworkManager Tool
State: connected
- Device: eth0
NM Path: /org/freedesktop/NetworkManager/Devices/eth0
Could you please edit /etc/init.d/nis to record the output of nm-tool
after attempting to start ypbind? This should say what Network Manager
thinks is happening which ought to show if it's a problem there or not.
After this block:
if want_ypbind
then
I find this a problem also
--
nis daemon fails to attach to domain the first time it is run in Gutsy
https://bugs.launchpad.net/bugs/152794
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I think that this may be related to problems with network manager
--
nis daemon fails to attach to domain the first time it is run in Gutsy
https://bugs.launchpad.net/bugs/152794
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
31 matches
Mail list logo
