package systemd 219-7ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1446219 reported by Filippo Sacco
54
This bug affects 11 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Low
Unassigned

Bug Description

error while booting system

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
Date: Wed Apr 15 13:19:58 2015
DuplicateSignature: package:systemd:219-7ubuntu3:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=00348856-2dda-4157-8712-ea2e5f733cc1 ro splash quiet
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt 1.0.9.7ubuntu4
SourcePackage: systemd
Title: package systemd 219-7ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to vivid on 2015-03-20 (30 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
Filippo Sacco (filippo-sacco) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Brian Murray (brian-murray) wrote :

From DpkgTerminalLog:

Processing triggers for systemd (219-7ubuntu1) ...
Failed to execute operation: Connessione scaduta
dpkg: error processing package systemd (--unpack):
 subprocess installed post-installation script returned error exit status 1

Revision history for this message
Brian Murray (brian-murray) wrote :

In Dmesg we can also see a kernel OOPS which may or may not be related:

[ 772.092247] irq 11: nobody cared (try booting with the "irqpoll" option)
[ 772.092247] CPU: 0 PID: 2619 Comm: kworker/0:1 Not tainted 3.19.0-13-generic #13-Ubuntu
[ 772.092247] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[ 772.092247] Workqueue: usb_hub_wq hub_event
[ 772.092247] 00000000 00000000 f5433f54 c16e966d f5430480 f5433f74 c10b3b8c c18ee260
[ 772.092247] 0000000b c194c390 f883f31a f5430480 00000000 f5433f98 c10b3efe f5433f98
[ 772.092247] 00000100 0001cd07 00000000 f5430480 f54304dc 00000000 f5433fd4 c10b1c02
[ 772.092247] Call Trace:
[ 772.092247] [<c16e966d>] dump_stack+0x41/0x52

Changed in systemd (Ubuntu):
importance: Undecided → Low
Revision history for this message
Martin Pitt (pitti) wrote :

 It appears to be a temporary kernel glitch, but can you reproduce this with "sudo apt-get install --reinstall systemd"? If so, attaching the output of "journalctl" would be appreciated. If this reproduces the crash, please also copy&paste the output of

  sudo sh -x /var/lib/dpkg/info/systemd.postinst configure 219-7ubuntu3

Thanks!

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Filippo Sacco (filippo-sacco) wrote : Re: [Bug 1446219] Re: package systemd 219-7ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Download full text (5.0 KiB)

I Think You're right. now with system 219-7ubuntu4 there are no more errors.
btw here is the log
"+ set -e
+ [ configure = triggered ]
+ dpkg --compare-versions 219-7ubuntu3 lt 214-1
+ dpkg --compare-versions 219-7ubuntu3 lt 218-11~
+ dpkg --compare-versions 219-7ubuntu3 lt 204-1
+ dpkg --compare-versions 219-7ubuntu3 lt 33-1
+ dpkg --compare-versions 219-7ubuntu3 lt 204-9
+ dpkg --compare-versions 219-7ubuntu3 lt 204-8
+ dpkg --compare-versions 219-7ubuntu3 lt 40-1
+ systemd-machine-id-setup
+ addgroup --quiet --system systemd-journal
+ addgroup --quiet --system systemd-journal-remote
+ adduser --quiet --system --group --no-create-home --home /run/systemd
--gecos systemd Time Synchronization systemd-timesync
+ adduser --quiet --system --group --no-create-home --home
/run/systemd/netif --gecos systemd Network Management systemd-network
+ adduser --quiet --system --group --no-create-home --home
/run/systemd/resolve --gecos systemd Resolver systemd-resolve
+ adduser --quiet --system --group --no-create-home --home /run/systemd
--gecos systemd Bus Proxy systemd-bus-proxy
+ _update_catalog
+ journalctl --update-catalog
+ setcap cap_dac_override,cap_sys_ptrace=ep /usr/bin/systemd-detect-virt
+ dpkg --compare-versions 219-7ubuntu3 ge 204
+ read UNIT
+ systemctl enable <email address hidden>
+ read UNIT
+ systemctl enable remote-fs.target
+ read UNIT
+ systemctl enable systemd-timesyncd.service
+ read UNIT
+ [ -n 219-7ubuntu3 ]
+ _systemctl daemon-reexec
+ [ -d /run/systemd/system ]
+ systemctl daemon-reexec
+ _systemctl try-restart systemd-logind.service
+ [ -d /run/systemd/system ]
+ systemctl try-restart systemd-logind.service
+ _systemctl try-restart systemd-networkd.service
+ [ -d /run/systemd/system ]
+ systemctl try-restart systemd-networkd.service
+ _systemctl try-restart systemd-resolved.service
+ [ -d /run/systemd/system ]
+ systemctl try-restart systemd-resolved.service
+ _systemctl try-restart systemd-timesyncd.service
+ [ -d /run/systemd/system ]
+ systemctl try-restart systemd-timesyncd.service
+ dpkg --compare-versions 219-7ubuntu3 lt-nl 215-3
+ dpkg --compare-versions 219-7ubuntu3 lt-nl 219-4
+ dpkg-maintscript-helper rm_conffile /etc/lsb-base-logging.sh 25-1~
systemd -- configure 219-7ubuntu3
dpkg-maintscript-helper: error: environment variable DPKG_MAINTSCRIPT_NAME
is required

"
bye

2015-04-24 18:24 GMT+02:00 Martin Pitt <email address hidden>:

> It appears to be a temporary kernel glitch, but can you reproduce this
> with "sudo apt-get install --reinstall systemd"? If so, attaching the
> output of "journalctl" would be appreciated. If this reproduces the
> crash, please also copy&paste the output of
>
> sudo sh -x /var/lib/dpkg/info/systemd.postinst configure 219-7ubuntu3
>
> Thanks!
>
> ** Changed in: systemd (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1446219
>
> Title:
> package systemd 219-7ubuntu3 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 1
>
> Status in systemd package in Ubuntu:
> Incomplete
>
> Bug description:
> error while boot...

Read more...

Revision history for this message
Martin Pitt (pitti) wrote :

Ah, I forgot to give you the command with setting DPKG_MAINTSCRIPT_NAME=systemd, but it already went past all the interesting bits. This doesn't seem to be anything which we can fix/work around in systemd itself, at most it's a kernel bug. So I'm closing this report now. Please do yell if you see this again; once this is reproducible somehow we have a chance of investigating and fixing this properly. Thanks!

Changed in systemd (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Boris Aranovich (nomaed) wrote :

I got pointed to this bug while I was installing updates on 15.04 and got a crash...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.