<< after upgrade to Debian 10, NIS client cannot connect >>

[icamps]

HI,

I upgrade my system from Debian 9 to Debian 10 using this guide here (https://www.cyberciti.biz/faq/update-up ... 10-buster/).

I using NIS and NFS to authenticate and share files.

Previous to upgrade, there was no problem.

My system:

Code: Select all

# lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

# uname -a
Linux orange 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux

After the upgrade, the NIS service fails to load.

Code: Select all

# systemctl status nis
nis.service - LSB: Start NIS client and server daemons.
   Loaded: loaded (/etc/init.d/nis; generated)
   Active: active (exited) since Fri 2021-04-09 07:59:20 -03; 45min ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 0 (limit: 4915)
   Memory: 0B
   CGroup: /system.slice/nis.service

Apr 09 07:59:09 orange systemd[1]: Starting LSB: Start NIS client and server daemons....
Apr 09 07:59:20 orange nis[1591]: Starting NIS services: ypbindbinding to YP server...........................................failed (backgrounded).
Apr 09 07:59:20 orange nis[1591]: .
Apr 09 07:59:20 orange systemd[1]: Started LSB: Start NIS client and server daemons..

ypbind test fail too:

Code: Select all

# ypwhich 
ypwhich: Can't communicate with ypbind

# yptest 
Test 1: domainname
Configured domainname is "fisica.icex"

Test 2: ypbind
Can't communicate with ypbind

Running ypbind in debug mode returns:

Code: Select all

# sudo ypbind -debug
10416: parsing config file
10416: Trying entry: ypserver 172.16.40.10
10416: parsed ypserver 172.16.40.10
10416: add_server() domain: fisica.icex, host: 172.16.40.10, slot: 0
10416: [Welcome to ypbind-mt, version 1.38]

10416: ping interval is 20 seconds

10416: rebind interval is 900 seconds

10418: ping host '172.16.40.10', domain 'fisica.icex'
10418: Answer for domain 'fisica.icex' from server '172.16.40.10'
10418: Pinging all active servers.

I appreciate any help to solve this issue.

Regards,

Camps

[Mark Poolman]

I have EXACTLY the same problem - code snippets above identical apart IP numbers etc.
The only thing I can add is that server is still running stretch in case that makes a difference.

Should this be treated as a bug report?

[Mark Poolman]

Udate:

This appears to be a systemd problem. If I start ypbind manually then all is OK.
Following that with
#/etc/init.d/nis restart
fails and also kills the previously launched ypbind process