Nis host resolution bug ?

[ChoBolT]

Hi,

I've just installed OpenSuse 11.1, and I'm facing a weird problem :

I'm using NIS as hostname resolution in my network, so I added, as I usually do with other versions of Suse, this line in nsswitch.conf :

hosts:  files nis mdns4_minimal [NOTFOUND=return] dns

As soon as there is the "nis" option for the hosts resolution I cannot use ssh/rsh anymore (from the host, or from another host).
I get this error when trying to ssh from another host :

** glibc detected *** in.rshd: free(): invalid pointer: 0x00007ff0f15a6af9 ***

And when trying to log from this host to another host, I get this :

*** glibc detected *** ssh: free(): invalid pointer: 0x00007f63a461f199 ***
======= Backtrace: =========
/lib64/libc.so.6[0x7f63a250a118]
/lib64/libc.so.6(cfree+0x76)[0x7f63a250bc76]
/lib64/libnss_nis.so.2(_nss_nis_gethostbyname4_r+0x1b9)[0x7f63a145c709]
/lib64/libc.so.6[0x7f63a25532a6]
/lib64/libc.so.6(getaddrinfo+0x1d2)[0x7f63a25555b2]
ssh[0x7f63a43c05f7]
ssh(main+0xf15)[0x7f63a43b6a15]
/lib64/libc.so.6(__libc_start_main+0xe6)[0x7f63a24b4586]
ssh[0x7f63a43b54b9]
======= Memory map: ========

(...)


Any idea on how to solve this ?
Thanks a lot
ChoBolT

[super-hornet]

I encounter similar problem as yours except I do not have any error.

The situation is this:
System A is openSUSE 11.1. Configured as NIS client. nsswitch.conf is set to:
hosts: files nis dns

System B is openSUSE 10.3. Configured as NIS client also.

The problem is, from System B, I cannot ssh to System A at all. It alway disconnect me after I enter password. I even try to enter nothing for password and it disconnect me right away (not like usual asking for password for 3 times).

Then, if I set System A (openSUSE 11.1) nsswitch.conf by removing "nis" from the hosts:
hosts: files dns

I can connect from System B to System A.

Help!

SH

[super-hornet]

I think I solve my problem.

It turns out the glibc that comes with the openSUSE 11.1 that is causing it. The version is:
glibc-2.9-2.9

I upgrade/update it to:
glibc-2.9-2.11.1.x86_64.rpm { Yes, I'm using x86_64 version }

and now the problem solve!

To get the update RPM for glibc:
x86_64:
Index of /update/11.1/rpm/x86_64
xi586:
Index of /update/11.1/rpm/i586

SH