NIS not working

Bug #372426 reported by Andrey M
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nis (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: nis

This is on Ubuntu 9.04 for x86_64

at boot up
YP bind fails.

then at GDM,
NIS terminal login does not work

temporary fix:
login as root, log out, and then NIS does work

permanent fix:
in /etc/rc2.d/, move nis and gdm after NetworkManager
in my case, I have
S50NetworkManager

so I had to move NIS and and GDM to
S51nis
S52gdm

$ lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty

$ apt-cache policy nis
nis:
  Installed: 3.17-17ubuntu1
  Candidate: 3.17-17ubuntu1
  Version table:
 *** 3.17-17ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
banshee (banshee-dreamwiz) wrote :

so i have a similar problem but a little different
i have installed ubuntu 9.04 and i can not login using my account but can login as root
before i had ubuntu 8.10 and i had the same problem, i would reboot my computer and i could not login as myself but if I login as root them logout then login as myself it would work.
but after installing 9.04 this would not work, the only way i could login as myself is if i login as root then DO NOT logout but switch user then login as myself. If i logout of root then i can not login as myself.
can anyone help me with this? I have tried the solution mentioned above (although it is for a different problem) and of course it did not solve the issue. i am a novice at this so please explain in an easy to understand language. appreciate it! thanks.

Revision history for this message
Andrey M (andrey.mrt.) wrote :

I found that reshuffling the service startup order fixed the issue for me, if you feel comfortable, give it a try and report back

permanent fix:
in /etc/rc2.d/, move nis and gdm after NetworkManager
in my case, I have
S50NetworkManager

so I had to move NIS and and GDM to
S51nis
S52gdm

Revision history for this message
banshee (banshee-dreamwiz) wrote : Re:[Bug 372426] Re: NIS not working

yeah i tried that and it still didnt help.... :(

>----- Original Message -----
>From: "Andrey M" <email address hidden>
>To: <email address hidden>
>Date: Wed, 01 Jul 2009 15:47:25 -0000
>Subject: [Bug 372426] Re: NIS not working
>
>I found that reshuffling the service startup order fixed the issue for
>me, if you feel comfortable, give it a try and report back
>
>permanent fix:
>in /etc/rc2.d/, move nis and gdm after NetworkManager
>in my case, I have
>S50NetworkManager
>
>so I had to move NIS and and GDM to
>S51nis
>S52gdm
>
>--
>NIS not working
>https://bugs.launchpad.net/bugs/372426
>You received this bug notification because you are a direct subscriber
>of the bug.
>
>Status in “nis” package in Ubuntu: New
>
>Bug description:
>Binary package hint: nis
>
>This is on Ubuntu 9.04 for x86_64
>
>at boot up
>YP bind fails.
>
>then at GDM,
>NIS terminal login does not work
>
>temporary fix:
>login as root, log out, and then NIS does work
>
>permanent fix:
>in /etc/rc2.d/, move nis and gdm after NetworkManager
>in my case, I have
>S50NetworkManager
>
>so I had to move NIS and and GDM to
>S51nis
>S52gdm
>
>
>$ lsb_release --all
>No LSB modules are available.
>Distributor ID: Ubuntu
>Description: Ubuntu 9.04
>Release: 9.04
>Codename: jaunty
>
>$ apt-cache policy nis
>nis:
> Installed: 3.17-17ubuntu1
> Candidate: 3.17-17ubuntu1
> Version table:
> *** 3.17-17ubuntu1 0
> 500 http://archive.ubuntu.com jaunty/main Packages
> 100 /var/lib/dpkg/status
>

-------------------------------------------------
Your Life on the Net
DreamWiz Free Mail @ http://www.dreamwiz.com/

Revision history for this message
Chuck Short (zulcss) wrote :

Hi,

Is this still a problem?

Regards
chuck

Changed in nis (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
banshee (banshee-dreamwiz) wrote :

yup, i could not fix it so i gave up and
i just login as root, change user and login as myself.
it slows the computer down but it works.....
i would like to know of a fix if there is one..
thanks

>----- Original Message -----
>From: "Chuck Short" <email address hidden>
>To: <email address hidden>
>Date: Thu, 15 Oct 2009 17:15:06 -0000
>Subject: [Bug 372426] Re: NIS not working
>
>Hi,
>
>Is this still a problem?
>
>Regards
>chuck
>
>** Changed in: nis (Ubuntu)
> Importance: Undecided => Low
>
>** Changed in: nis (Ubuntu)
> Status: New => Incomplete
>
>--
>NIS not working
>https://bugs.launchpad.net/bugs/372426
>You received this bug notification because you are a direct subscriber
>of the bug.
>
>Status in “nis” package in Ubuntu: Incomplete
>
>Bug description:
>Binary package hint: nis
>
>This is on Ubuntu 9.04 for x86_64
>
>at boot up
>YP bind fails.
>
>then at GDM,
>NIS terminal login does not work
>
>temporary fix:
>login as root, log out, and then NIS does work
>
>permanent fix:
>in /etc/rc2.d/, move nis and gdm after NetworkManager
>in my case, I have
>S50NetworkManager
>
>so I had to move NIS and and GDM to
>S51nis
>S52gdm
>
>
>$ lsb_release --all
>No LSB modules are available.
>Distributor ID: Ubuntu
>Description: Ubuntu 9.04
>Release: 9.04
>Codename: jaunty
>
>$ apt-cache policy nis
>nis:
> Installed: 3.17-17ubuntu1
> Candidate: 3.17-17ubuntu1
> Version table:
> *** 3.17-17ubuntu1 0
> 500 http://archive.ubuntu.com jaunty/main Packages
> 100 /var/lib/dpkg/status
>
>

-------------------------------------------------
Your Life on the Net
DreamWiz Free Mail @ http://www.dreamwiz.com/

Chuck Short (zulcss)
Changed in nis (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Arunas (aris020) wrote :

11.10 keeps freezing randomly with NIS enabled if the interface is not in /etc/network/interfaces as "auto" - I presume network-manager enables it just for the user session and times it out when no user is logged in? It works for a short period of time after reboot and if users keep logging in, but freezes up after any significant idle period.

I had troubles even shutting the system down until I moved eth0 control to /etc/network/interfaces. This should be part of package configuration script (as well as adding NIS to /etc/nsswitch.conf), I suppose.

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.