Results 1 to 9 of 9

Thread: NIS (?) problem

  1. #1

    Default NIS (?) problem

    I cannot login using NIS, though I can login as root. When using one of the NIS logins, it says that the passwd is wrong!
    ypcat and nisdomainname show what I expect, though.
    This problem only showed up after one of the latest dups.
    Code:
    Linux hp712 4.13.5-1-default #1 SMP PREEMPT Thu Oct 5 18:28:26 UTC 2017 (3fd9659) x86_64 x86_64 x86_64 GNU/Linux
    hp712:~ # nisdomainname 
    cluster
    hp712:~ # ypwhich
    leonardo
    
    hp712:~ # ypcat passwd
    
    abonfi:9gxOpiK3u0sLI:507:509:Aldo Bonfiglioli:/home/abonfi:/bin/bash
    guest:OiJrXy7DonX2k:503:508::/home/guest:/bin/csh
    
    hp712:~ #
    Any suggestion?
    Aldo

  2. #2
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: NIS (?) problem

    IIRC ( it's a long time ago ), you need to user 'yppasswd' for NIS users....
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  3. #3

    Default Re: NIS (?) problem

    NIS has been working for over a year on my TUMBLEWEED desktop.
    If I now try to log on or ssh on the TUMBLEWEED desktop, it looks like the passwd is wrong, but if I use the TUMBLEWEED desktop (once I have logged in as root) to log onto a different linux box (running an old OS) I can log as usual with the usual passwd.

  4. #4

    Default Re: NIS (?) problem

    Same here, after 'zypper up' yesterday (2017-10-12). No remote user login to updated server (= NIS client!!) with TUMBLEWEED.
    All updated Leap installations work fine. All TUMBLEWEED with GLIBC <= 2.26-2.1 are fine!! NIS server not touched at all!

    So, I think the NIS server is fine. Any suggestions?

    Error message in journalctl when I want to login to updated TUMBLEWEED client with NIS user:

    ---> SNIP
    Okt 13 09:09:09 btc9x4 sshd[22418]: Invalid user XXXXXXX from YYY.XXX.AAA.BBB
    Okt 13 09:09:09 btc9x4 sshd[22418]: input_userauth_request: invalid user XXXXXXX [preauth]
    Okt 13 09:09:09 btc9x4 sshd[22420]: gkr-pam: error looking up user information
    Okt 13 09:09:09 btc9x4 sshd[22418]: Postponed keyboard-interactive for invalid user XXXXXXX from YYY.XXX.AAA.BBB port 44444 ssh2 [preauth]
    ---> SNIP

    - When I copy passwd/shadow user lines to the local machine, I'm able to login.
    - 'ypcat passwd' shows NIS passwd file!!

    What is going on????

  5. #5
    Join Date
    Aug 2010
    Location
    Athens, Greece
    Posts
    11

    Default Re: NIS (?) problem

    Install libnss_nis2.
    It seems this functionality was split from glibc into a plugin.

  6. #6

    Default Re: NIS (?) problem

    The libnss_nis2 libraries are installed (version 1.3-1.1), but the problem persists.

  7. #7
    Join Date
    Aug 2010
    Location
    Athens, Greece
    Posts
    11

    Default Re: NIS (?) problem

    Hmm, I just installed the library and restored the new default /etc/nsswitch.conf and after a while NIS worked again.

  8. #8
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: NIS (?) problem

    Quote Originally Posted by mweatBT View Post
    Same here, after 'zypper up' yesterday (2017-10-12). No remote user login to updated server (= NIS client!!) with TUMBLEWEED.
    All updated Leap installations work fine. All TUMBLEWEED with GLIBC <= 2.26-2.1 are fine!! NIS server not touched at all!
    'zypper up' is plain wrong on TW, you need 'zypper dup'.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  9. #9

    Default Re: NIS (?) problem

    Quote Originally Posted by achaios View Post
    Hmm, I just installed the library and restored the new default /etc/nsswitch.conf and after a while NIS worked again.
    What do you mean by "restore the new default /etc/nsswitch.con?

    My nsswitch.conf is unchanged since August, which is much earlier than the dup that apparently caused the trouble.
    I noticed there is a nsswitch.conf.rpmnew dated oct 6th. Should I modify that and replace the current nsswitch.conf?

    The output listed below is what I get wneh trying to ssh from root on the same machine:

    Code:
    Oct 19 14:32:51 hp712 sshd[3435]: Invalid user abonfi from 127.0.0.1
    Oct 19 14:32:51 hp712 sshd[3435]: input_userauth_request: invalid user abonfi [preauth]
    Oct 19 14:32:51 hp712 sshd[3437]: gkr-pam: error looking up user information
    Oct 19 14:32:51 hp712 sshd[3435]: Postponed keyboard-interactive for invalid user abonfi from 127.0.0.1 port 34752 ssh2 [preauth]
    Oct 19 14:32:54 hp712 sshd[3437]: pam_unix(sshd:auth): check pass; user unknown
    Oct 19 14:32:54 hp712 sshd[3437]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=127.0.0.1
    Oct 19 14:32:56 hp712 sshd[3435]: error: PAM: User not known to the underlying authentication module for illegal user abonfi from 127.0.0.1
    Oct 19 14:32:56 hp712 sshd[3435]: Failed keyboard-interactive/pam for invalid user abonfi from 127.0.0.1 port 34752 ssh2
    Oct 19 14:32:56 hp712 sshd[3480]: gkr-pam: error looking up user information
    Oct 19 14:32:56 hp712 sshd[3435]: Postponed keyboard-interactive for invalid user abonfi from 127.0.0.1 port 34752 ssh2 [preauth]
    Oct 19 14:33:12 hp712 su[3635]: pam_unix(su:session): session opened for user root by (uid=0)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •