Bug#801384: marked as done (cron boot order is wrong with systemd, cronatbs ignored because non-local users are not known)

2018-03-12 Thread Debian Bug Tracking System 
Your message dated Mon, 12 Mar 2018 23:49:37 +
with message-id 
and subject line Bug#801384: fixed in cron 3.0pl1-130
has caused the Debian Bug report #801384,
regarding cron boot order is wrong with systemd, cronatbs ignored because 
non-local users are not known
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 ow...@bugs.debian.org
immediately.)


-- 
801384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-127+deb8u1
Severity: important

cron needs to be started later then certain services providing non-local users.
The init file (/etc/init.d/cron) has this LSB line in it:
Should-Start:  $network $named slapd autofs ypbind nscd nslcd 
winbind

But the systemd service file (/lib/systemd/system/cron.service) has no 
corresponding After= line.
When systemd is used, the service file gets precedence and the LSB init file is 
ignored, thus cron may
be started before these services.

E.g. on my system, I have local users in a locally-running LDAP server (slapd). 
When cron starts before slapd,
crontabs containing non-local users are ignored:

Oct  7 09:34:03 localhost cron[834]: Error: bad username; while reading 
/etc/crontab
Oct  7 09:34:03 localhost cron[834]: (*system*) ERROR (Syntax error, this 
crontab file will be ignored)

Fixed by adding "After=slapd.service" to the cron service file.

This is a regression when upgrading from wheezy (as it did not use systemd).

Other bug reports exist which are most likely caused by the same problem:
   #767016 [i|  |  ] [cron] cron does start before sssd and therefore 
authentication fails
   #783665 [i|  |  ] [cron] cron does not execute some non-root cron.d jobs 
when started before ypbind




-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cron depends on:
ii  adduser  3.113+nmu3
ii  debianutils  4.4+b1
ii  dpkg 1.17.25
ii  init-system-helpers  1.22
ii  libc62.19-18+deb8u1
ii  libpam-runtime   1.1.8-3.1
ii  libpam0g 1.1.8-3.1
ii  libselinux1  2.3-2
ii  lsb-base 4.1+Debian13+nmu1

Versions of packages cron recommends:
ii  postfix [mail-transport-agent]  2.11.3-1

Versions of packages cron suggests:
pn  anacron
pn  checksecurity  
ii  logrotate  3.8.7-1+b1

Versions of packages cron is related to:
ii  libnss-ldap   265-3+b1
pn  libnss-ldapd  
ii  libpam-ldap   184-8.7+b1
pn  libpam-mount  
pn  nis   
pn  nscd  

-- Configuration Files:
/etc/crontab changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cron
Source-Version: 3.0pl1-130

We believe that the bug you reported is fixed in the latest version of
cron, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 801...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated cron 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Mar 2018 22:00:01 +0100
Source: cron
Binary: cron
Architecture: source i386
Version: 3.0pl1-130
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Description:
 cron   - process scheduling daemon
Closes: 705570 757191 767016 783665 792572 801384 834728 840601 892720 892721 
892724
Changes:
 cron (3.0pl1-130) unstable; urgency=medium
 .
   * debian/postinst: Do not do check if /var/spool/cron/crontabs if empty
 (Closes: 892720, 892721, 892724)
   * debian/cron.service:
   - Add dependency on nss-user-lookup.target in the definition which
 properly fixes the issues when cron is started

Bug#801384: marked as done (cron boot order is wrong with systemd, cronatbs ignored because non-local users are not known)

2018-03-11 Thread Debian Bug Tracking System 
Your message dated Sun, 11 Mar 2018 23:04:21 +
with message-id 
and subject line Bug#801384: fixed in cron 3.0pl1-129
has caused the Debian Bug report #801384,
regarding cron boot order is wrong with systemd, cronatbs ignored because 
non-local users are not known
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 ow...@bugs.debian.org
immediately.)


-- 
801384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-127+deb8u1
Severity: important

cron needs to be started later then certain services providing non-local users.
The init file (/etc/init.d/cron) has this LSB line in it:
Should-Start:  $network $named slapd autofs ypbind nscd nslcd 
winbind

But the systemd service file (/lib/systemd/system/cron.service) has no 
corresponding After= line.
When systemd is used, the service file gets precedence and the LSB init file is 
ignored, thus cron may
be started before these services.

E.g. on my system, I have local users in a locally-running LDAP server (slapd). 
When cron starts before slapd,
crontabs containing non-local users are ignored:

Oct  7 09:34:03 localhost cron[834]: Error: bad username; while reading 
/etc/crontab
Oct  7 09:34:03 localhost cron[834]: (*system*) ERROR (Syntax error, this 
crontab file will be ignored)

Fixed by adding "After=slapd.service" to the cron service file.

This is a regression when upgrading from wheezy (as it did not use systemd).

Other bug reports exist which are most likely caused by the same problem:
   #767016 [i|  |  ] [cron] cron does start before sssd and therefore 
authentication fails
   #783665 [i|  |  ] [cron] cron does not execute some non-root cron.d jobs 
when started before ypbind




-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cron depends on:
ii  adduser  3.113+nmu3
ii  debianutils  4.4+b1
ii  dpkg 1.17.25
ii  init-system-helpers  1.22
ii  libc62.19-18+deb8u1
ii  libpam-runtime   1.1.8-3.1
ii  libpam0g 1.1.8-3.1
ii  libselinux1  2.3-2
ii  lsb-base 4.1+Debian13+nmu1

Versions of packages cron recommends:
ii  postfix [mail-transport-agent]  2.11.3-1

Versions of packages cron suggests:
pn  anacron
pn  checksecurity  
ii  logrotate  3.8.7-1+b1

Versions of packages cron is related to:
ii  libnss-ldap   265-3+b1
pn  libnss-ldapd  
ii  libpam-ldap   184-8.7+b1
pn  libpam-mount  
pn  nis   
pn  nscd  

-- Configuration Files:
/etc/crontab changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cron
Source-Version: 3.0pl1-129

We believe that the bug you reported is fixed in the latest version of
cron, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 801...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated cron 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Mar 2018 22:38:06 +0100
Source: cron
Binary: cron
Architecture: source i386
Version: 3.0pl1-129
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Description:
 cron   - process scheduling daemon
Closes: 767016 783665 801384 819832 864466
Changes:
 cron (3.0pl1-129) unstable; urgency=medium
 .
   * Acknowledge NMU
   * debian/cron.init, debian/cron.service: Make sure cron is started last and
 stopped first, with patch provided by Harald Dunke
 (Closes: #767016, #801384, #783665) (LP: #1593317)
   * crontab.1: Document limitation due to account renaming as described in
 Ubuntu's bug 73398