[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#926305: marked as done (nis startup scripts are completely broken)

Your message dated Thu, 18 Apr 2019 15:43:59 +0200
with message-id <[🔎] 20190418134359.t6sqscgqkem7ienp@pippin.home.lxtec.de>
and subject line Re: Bug#926305: nis startup scripts are completely broken
has caused the Debian Bug report #926305,
regarding nis startup scripts are completely broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
926305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926305
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: nis
Version: 3.17.1-3+b1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

Startup scripts are completely broken. Something in the systemd conversion/autogeneration.

The ypbind binary is never started, the script goes into "backgrounded" and fails. From there
on the system is unusable - you cannot log in, UIDs and groups do not resolve, etc.

The same system operated correctly before buster upgrade and will operate correctly if
ypbind is invoked from the command line.

This looks like a pure systemd conversion issue of some sort.

-- Package-specific info:

NIS domain: home 

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nis depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  hostname               3.21
ii  libc6                  2.28-8
ii  libgdbm6               1.18.1-4
ii  libsystemd0            241-1
ii  lsb-base               10.2019031300
ii  make                   4.2.1-1.2
ii  netbase                5.6
ii  rpcbind [portmap]      1.2.5-0.3

nis recommends no packages.

Versions of packages nis suggests:
pn  nscd  <none>

-- Configuration Files:
/etc/yp.conf changed [not included]

-- debconf information:
* nis/domain: home

--- End Message ---
--- Begin Message --- 
* Elimar Riesebieter <riesebie@lxtec.de> [2019-04-03 11:06 +0200]:

> * Anton Ivanov <anton.ivanov@kot-begemot.co.uk> [2019-04-03 09:43 +0100]:
> 
> > Package: nis
> > Version: 3.17.1-3+b1
> > Severity: critical
> > Justification: breaks unrelated software
> > 
> > Dear Maintainer,
> > 
> > Startup scripts are completely broken. Something in the systemd conversion/autogeneration.
> > 
> > The ypbind binary is never started, the script goes into "backgrounded" and fails. From there
> > on the system is unusable - you cannot log in, UIDs and groups do not resolve, etc.
> > 
> > The same system operated correctly before buster upgrade and will operate correctly if
> > ypbind is invoked from the command line.
> > 
> > This looks like a pure systemd conversion issue of some sort.
> 
> At my systems installing nscd helped. As well setting "YPBINDARGS="
> in /etc/default/nis must be.

This bug should be closed as there is no response from the reporter.
As well it seems to be fixed following the advices given above,
though.

Elimar
-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
              --posting from alex in debian-user--

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: