cannot bind to YP server under AMD64

Bug #174162 reported by Jonathan Grot
6
Affects Status Importance Assigned to Milestone
nis (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: nis

During boot, I get:
binding to YP server...
...
...
...

... [fail]

If I comment out the variable in /etc/default/nis that contains -no-dbus, it binds *sometimes*.

Revision history for this message
Jonathan Grot (jgrot) wrote :

Forgot to mention than I have two 32 bit Intel machines with 7.10 configured just about the same way and they both work fine.

Revision history for this message
Mark Brown (broonie) wrote :

I can't reproduce this here using 7.10 on an AMD64 - the device binds straight away. Your comment about playing with --no-dbus indicates that there may be some issues here with startup ordering with respect to the network interface coming up. Does this problem occur only on startup or does it also occur if you run

   /etc/init.d/nis restart

later?

Mark Brown (broonie)
Changed in nis:
status: New → Incomplete
Revision history for this message
Martti Kuparinen (mk1970) wrote :

I didn't have any problems on 7.10 but after performing a clean install of 32-bit 8.04 today I couldn't login as my NIS user after reboot. Here's what I did:

# sudo aptitude update && sudo aptitude dist-upgrade
# sudo aptitude install nis
# sudo vi /etc/nsswitch.conf

passwd: compat nis
group: compat nis
shadow: compat nis

# id mynislogin
uid=10000(mynislogin) ......
# sudo reboot

So, after reboot ypbind was not bound to the server. I solved this by

# sudo vi /etc/rc.local

/etc/init.d/nis restart

Revision history for this message
Mark Brown (broonie) wrote : Re: [Bug 174162] Re: cannot bind to YP server under AMD64

On Wed, Mar 19, 2008 at 12:21:17PM -0000, Martti Kuparinen wrote:

> passwd: compat nis
> group: compat nis
> shadow: compat nis

You really should use compat only. Adding NIS as well will at best
cause redundant queries of the NIS database if the compat lookup fails
and at worst defeat any access restructions introduced using the compat
lookups.

--
"You grabbed my hand and we fell into it, like a daydream - or a fever."

Revision history for this message
Martti Kuparinen (mk1970) wrote :

With "nis" in /etc/nsswitch.conf

n40:~> id martti
uid=2000(martti) gid=10000(tri) groups=...

Without "nis" in /etc/nsswitch.conf

n40:~> id martti
id: martti: No such user

Again with "nis" in /etc/nsswitch.conf

n40:~> id martti
uid=2000(martti) gid=10000(tri) groups=...

Please note that the NIS server is not running Linux but NetBSD...

Revision history for this message
Mark Brown (broonie) wrote :

Have you added the +:::: lines to the passwd, group and shadow files?

Revision history for this message
Martti Kuparinen (mk1970) wrote :

No, isn't that the "old way of doing this", I thought modifying /etc/nsswitch.conf was "the right thing to do"...

Revision history for this message
Mark Brown (broonie) wrote :

There is no reason not to use the compat mechanism for the user databases - it's more flexible. 'nis' is there to handle other cases such as those where there is no file to use (like netgroup).

If you really want to use an explicit nis for user database then you should replace the 'compat' with 'files'.

Revision history for this message
fil (fil-taz) wrote :

#152794 itself is duplicate of #50430. This one blocks setting it so.
Here should point straight to #50430 but it seems like I can't change that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.