Package: rpcbind
Version: 0.2.1-6+deb8u1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I used wheezy until a few days ago and after applying a regular
upgrade and rebooting the computer (since the kernel was also
upgraded) broke the previously working nis master configuration.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Finally, I upgraded the server machine to jessie and kernel 3.16,
but the problem still remained, that is nis won't start, so I had
to disable its automatic start at boottime.
I figured out, that when the nis script defines domainname the
communication with rpcbind hangs (rpcinfo...).
I am really stucked and no idea what could be scr*wed up...
The version of installed nis is 3.17-33.
I have also tried to remove (rename) all previously used configfiles
(/etc/default/nis, /etc/defaultdomain, /etc/yp*, /var/yp/)
and reinstall nis but without any success or progress.
sz.zs
-- System Information:
Debian Release: 8.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=hu_HU, LC_CTYPE=hu_HU (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages rpcbind depends on:
ii initscripts 2.88dsf-59
ii insserv 1.14.0-5
ii libc6 2.19-18+deb8u4
ii libtirpc1 0.2.5-1
ii libwrap0 7.6.q-25
ii lsb-base 4.1+Debian13+nmu1
rpcbind recommends no packages.
rpcbind suggests no packages.
-- no debconf information
