Bug#930537: marked as done (at fails to install and to be removed afterwards even with dpkg --force-all)

Fri, 14 Jun 2019 13:15:55 -0700 

Your message dated Fri, 14 Jun 2019 22:12:43 +0200
with message-id <[email protected]>
and subject line Re: at fails to install and to be removed afterwards even with 
dpkg --force-all
has caused the Debian Bug report #930537,
regarding at fails to install and to be removed afterwards even with dpkg 
--force-all
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 [email protected]
immediately.)


-- 
930537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930537
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message --- 
Package: at
Version: 3.1.23-1
Severity: grave
Justification: renders package unusable

at fails to install:

E: at: »installiertes at-Skript des Paketes post-installation«-Unterprozess gab
den Fehlerwert 1 zurück

Vorbereitung zum Entpacken von .../archives/at_3.1.23-1_amd64.deb ...
Entpacken von at (3.1.23-1) ...
at (3.1.23-1) wird eingerichtet ...
Created symlink /etc/systemd/system/multi-user.target.wants/atd.service →
/etc/systemd/system/atd.service.
Failed to start atd.service: Unit atd.service has a bad unit file setting.
See system logs and 'systemctl status atd.service' for details.
invoke-rc.d: initscript atd, action "start" failed.
● atd.service - Deferred execution scheduler
   Loaded: bad-setting (Reason: Unit atd.service has a bad unit file setting.)
   Active: inactive (dead)
     Docs: man:atd(8)

Jun 14 20:58:18  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 20:58:20  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 20:58:20  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:00:42  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:00:46  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:00:46  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:00:46  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
dpkg: Fehler beim Bearbeiten des Paketes at (--configure):
 »installiertes at-Skript des Paketes post-installation«-Unterprozess gab den
Fehlerwert 1 zurück
Trigger für man-db (2.8.5-2) werden verarbeitet ...
Trigger für systemd (241-5) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 at
E: Sub-process /usr/bin/dpkg returned an error code (1)
Ein Paket konnte nicht installiert werden. Wiederherstellung wird versucht:
at (3.1.23-1) wird eingerichtet ...
Failed to start atd.service: Unit atd.service has a bad unit file setting.
See system logs and 'systemctl status atd.service' for details.
invoke-rc.d: initscript atd, action "start" failed.
● atd.service - Deferred execution scheduler
   Loaded: bad-setting (Reason: Unit atd.service has a bad unit file setting.)
   Active: inactive (dead)
     Docs: man:atd(8)

Jun 14 21:00:42  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:00:46  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:00:46  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:00:46  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:30  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:32  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:33  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
dpkg: Fehler beim Bearbeiten des Paketes at (--configure):
 »installiertes at-Skript des Paketes post-installation«-Unterprozess gab den
Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 at


----------------------

Purging  with Synaptic  fails too:

E: at: »installiertes at-Skript des Paketes pre-removal«-Unterprozess gab den
Fehlerwert 1 zurück

Entfernen von at (3.1.23-1) ...
Failed to stop atd.service: Unit atd.service not loaded.
invoke-rc.d: initscript atd, action "stop" failed.
dpkg: Fehler beim Bearbeiten des Paketes at (--remove):
 »installiertes at-Skript des Paketes pre-removal«-Unterprozess gab den
Fehlerwert 1 zurück
Failed to start atd.service: Unit atd.service has a bad unit file setting.
See system logs and 'systemctl status atd.service' for details.
invoke-rc.d: initscript atd, action "start" failed.
● atd.service - Deferred execution scheduler
   Loaded: bad-setting (Reason: Unit atd.service has a bad unit file setting.)
   Active: inactive (dead)
     Docs: man:atd(8)

Jun 14 21:00:46  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:30  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:32  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:33  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:08:38  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:08:39  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:08:39  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
dpkg: Fehler beim Aufräumen:
»installiertes at-Skript des Paketes post-installation«-Unterprozess gab den
Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 at
E: Sub-process /usr/bin/dpkg returned an error code (1)
Ein Paket konnte nicht installiert werden. Wiederherstellung wird versucht:
at (3.1.23-1) wird eingerichtet ...
Failed to start atd.service: Unit atd.service has a bad unit file setting.
See system logs and 'systemctl status atd.service' for details.
invoke-rc.d: initscript atd, action "start" failed.
● atd.service - Deferred execution scheduler
   Loaded: bad-setting (Reason: Unit atd.service has a bad unit file setting.)
   Active: inactive (dead)
     Docs: man:atd(8)

Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:28  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:30  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:32  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:02:33  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:08:38  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:08:39  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:08:39  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:08:41  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
Jun 14 21:08:41  systemd[1]: atd.service: Service has no ExecStart=, ExecStop=,
or SuccessAction=. Refusing.
dpkg: Fehler beim Bearbeiten des Paketes at (--configure):
 »installiertes at-Skript des Paketes post-installation«-Unterprozess gab den
Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 at

----------------

dpkg --purge --force-all at   also fails:

dpkg: Warnung: »ldconfig« wurde im PATH nicht gefunden oder ist nicht
ausführbar
dpkg: Warnung: »start-stop-daemon« wurde im PATH nicht gefunden oder ist nicht
ausführbar
dpkg: Warnung: Problem wird übergangen, weil --force angegeben ist:
dpkg: Warnung: 2 erwartete Programme nicht im PATH gefunden oder nicht
ausführbar
Beachten Sie: PATH von root sollte normalerweise /usr/local/sbin, /usr/sbin und
/sbin enthalten
(Lese Datenbank ... 147805 Dateien und Verzeichnisse sind derzeit installiert.)
Entfernen von at (3.1.23-1) ...
/var/lib/dpkg/info/at.prerm: 5: /var/lib/dpkg/info/at.prerm: invoke-rc.d: not
found
dpkg: Fehler beim Bearbeiten des Paketes at (--purge):
 »installiertes at-Skript des Paketes pre-removal«-Unterprozess gab den
Fehlerwert 1 zurück
/var/lib/dpkg/info/at.postinst: 33: /var/lib/dpkg/info/at.postinst: update-
rc.d: not found
dpkg: Fehler beim Aufräumen:
»installiertes at-Skript des Paketes post-installation«-Unterprozess gab den
Fehlerwert 127 zurück
Fehler traten auf beim Bearbeiten von:
 at


------------------

Removal of broken package only works when the following file is removed
manually:
rm /etc/init.d/atd

After that I can purge the package with Synaptic



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

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

Versions of packages at depends on:
ii  libc6           2.28-10
ii  libfl2          2.6.4-6.2
ii  libpam-runtime  1.3.1-5
ii  libpam0g        1.3.1-5
ii  libselinux1     2.8-1+b1
ii  lsb-base        10.2019051400

Versions of packages at recommends:
pn  default-mta | mail-transport-agent  <none>

at suggests no packages.

-- Configuration Files:
/etc/at.deny [Errno 13] Keine Berechtigung: '/etc/at.deny'

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hello Bert Schlumwig,

On Fri, Jun 14, 2019 at 09:20:32PM +0200, Bert Schlumwig wrote:
[...]
> Created symlink /etc/systemd/system/multi-user.target.wants/atd.service →
> /etc/systemd/system/atd.service.
> Failed to start atd.service: Unit atd.service has a bad unit file setting.
[...]

My german isn't great so I snipped all of it and kept the two above
lines which should be enough to confirm my suspicion.

You seem to have a locally customized atd.service file with invalid
syntax in it.
In your case the /etc/systemd/system/atd.service then masks the
package provided service file which lives in
/lib/systemd/system/atd.service.

Here's from my system for comparison:

------8<------>8------->8-------8<---------
$ ls -l /etc/systemd/system/multi-user.target.wants/atd.service 
lrwxrwxrwx 1 root root 31 apr 24  2016 
/etc/systemd/system/multi-user.target.wants/atd.service -> 
/lib/systemd/system/atd.service

$ systemctl cat atd.service
# /lib/systemd/system/atd.service
[Unit]
Description=Deferred execution scheduler
Documentation=man:atd(8)
After=remote-fs.target nss-user-lookup.target

[Service]
ExecStartPre=-find /var/spool/cron/atjobs -type f -name "=*" -not
-newercc /run/systemd -delete
ExecStart=/usr/sbin/atd -f
IgnoreSIGPIPE=false
KillMode=process
Restart=on-failure

[Install]
WantedBy=multi-user.target
------8<------>8------->8-------8<---------

It seems clear to me that this in not a packaging error, but a local
misconfiguration, so I'm closing this bug report.

Regards,
Andreas Henriksson

--- End Message ---

Reply via email to