NIS does not start on 15.04

[Sean Clarke]

After upgrade to 15.04 network services were not working as expected. Investigation showed NIS was removed during the upgrade and installation fails with unmet dependencies:

The following packages have unmet dependencies.
 nis : Depends: upstart (>= 0.9.7-2)

[Sean Clarke (sean-clarke)]

Update of upstart last night now progresses installation, however failure is now:

Need to get 0 B/152 kB of archives.
After this operation, 0 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 591467 files and directories currently installed.)
Preparing to unpack .../nis_3.17-32ubuntu6_amd64.deb ...
Unpacking nis (3.17-32ubuntu6) over (3.17-32ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up nis (3.17-32ubuntu6) ...
invoke-rc.d: ypbind.service doesn't exist but the upstart job does. Nothing to start or stop until a systemd or init job is present.
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'gdm' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `gdm'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `gdm'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'gdm' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `gdm'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `gdm'
invoke-rc.d: ypserv.service doesn't exist but the upstart job does. Nothing to start or stop until a systemd or init job is present.
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'gdm' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `gdm'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `gdm'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'gdm' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `gdm'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `gdm'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'gdm' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `gdm'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `gdm'

and obviously NIS fails to start / missing init script etc. etc.

[Sean Clarke (sean-clarke)]

Synch'd against the latest packages (which I believe is beta2) - problem still present

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sean Clarke (sean-clarke)]

Looks like this is purely the startup - I start bind manually and it all works fine and dandy.

[Sean Clarke (sean-clarke)]

2 weeks to go an this still has not even been assigned or triaged?

[Launchpad Janitor (janitor)]

This bug was fixed in the package nis - 3.17-32ubuntu7

---------------
nis (3.17-32ubuntu7) vivid; urgency=medium

  * Revert our dropping of the init.d script, so that services start under
    systemd, and to unbreak other init.d script dependencies to "nis" in
    insserv. (LP: #1431581)
  * Add debian/nis.upstart dummy job to avoid running the init.d script under
    upstart.
 -- Martin Pitt <email address hidden> Tue, 14 Apr 2015 15:09:51 -0500

[Sean Clarke (sean-clarke)]

NIS client now starts correctly:

/usr/sbin/ypbind -no-dbus

However on our NIS slave the NIS server is not starting:

ps -ef | grep ypserv

If I start manually> ypserv - it is fine and works as expected:

/usr/sbin/ypbind -no-dbus
ypserv

ypwhich
myserver.mydomain.co.uk

[Sean Clarke (sean-clarke)]

Just to confirm I have updated to the official release and although nis does now start without error, the ypserve process does not get started (as described above) meaning that NIS clients work, but NIS server master and slaves do not work properly.

[Sean Clarke (sean-clarke)]

Still not resolved for the reason above

[Sean Clarke (sean-clarke)]

Still not fully resolved

[Martin Pitt (pitti)]

Did you actually enable NISSERVER=slave or =master in /etc/default/nis? ypserv is only started if you do that. As far as I can see, the upstart job (/etc/init/ypserv.conf) uses exactly the same setting.

[Sean Clarke (sean-clarke)]

Thanks Martin - good guess.

Oddly, all the machines were working previous (with several slaves), probably for 2+ years with regular updates.

Anyway, thanks for the assistance, it's all working now as expected.

[Sean Clarke (sean-clarke)]

Update : Just went onto a client NIS server that was running 14.10 and checked the /etc/default/nis file and it was set to master, upgraded to 15.04 and it was changed to NISSERVER=false and all clients couldn't bind.

Changed manually back to NISSERVER=master and all is OK.

Looks like the upgrade doesn't observe the original settings