Ubuntu
systemd package

ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages

Bug #1491850 reported by bugproxy
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
crashdump (Ubuntu)
New
Undecided
Unassigned
systemd (Ubuntu)
New
High
Martin Pitt

Bug Description

== Comment: #0 - YUECHANG E. MEI <email address hidden> - 2015-09-02 12:57:52 ==
---Problem Description---
We tried to install linux-crashdump package (using "apt-get install linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the work around in bug 122925 and the linux-crashdump get install successfully.

Error we see when we install linux-crashdump:

root@conelp2:~# apt-get install linux-crashdump
....
....
Unpacking linux-crashdump (4.1.0.3.3) ...
Selecting previously unselected package policykit-1.
Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ...
Unpacking policykit-1 (0.105-11) ...
Processing triggers for man-db (2.7.2-1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (224-2ubuntu2) ...
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20)
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--unpack):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for dbus (1.9.20-1ubuntu2) ...
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@conelp2:~# dpkg -l | grep linux-crashdump
iU linux-crashdump 4.1.0.3.3 ppc64el Linux kernel crashdump setup for the latest generic kernel

---uname output---
Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = n/a

---Debugger---
A debugger is not configured

---Steps to Reproduce---
 1. Install Ubuntu 15.10 in a lpar
2. Login as root, and run "apt-get update".
3. Install linux-crashdump packages, run "apt-get install linux-crashdump", then you will see the error

Stack trace output:
 no

Oops output:
 no

System Dump Info:
  The system is not configured to capture a system dump.

*Additional Instructions for Yuechang (Erin) Mei /<email address hidden>, Raja Sunkari /<email address hidden>:
-Attach sysctl -a output output to the bug.

bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-129812 severity-high targetmilestone-inin---
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1491850/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Brian Murray (brian-murray)
affects: ubuntu → linux-meta (Ubuntu)
Brad Figg (brad-figg)
affects: linux-meta (Ubuntu) → linux (Ubuntu)
bugproxy (bugproxy)
tags: added: targetmilestone-inin1510
removed: targetmilestone-inin---
Revision history for this message
Breno Leitão (breno-leitao) wrote :
Download full text (3.6 KiB)

I am not able to reproduce this problem on my machine:

ubuntu@1510:~$ sudo apt-get install linux-crashdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  g++-4.9 libboost-iostreams1.55.0 libregexp-common-perl linux-headers-3.19.0-16 linux-headers-3.19.0-16-generic linux-image-3.19.0-16-generic
  linux-image-extra-3.19.0-16-generic
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  crash kdump-tools kexec-tools makedumpfile
The following NEW packages will be installed:
  crash kdump-tools kexec-tools linux-crashdump makedumpfile
0 upgraded, 5 newly installed, 0 to remove and 19 not upgraded.
Need to get 2,891 kB of archives.
After this operation, 12.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ports.ubuntu.com/ubuntu-ports/ wily/main crash ppc64el 7.1.1-1ubuntu3 [2,694 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports/ wily/main makedumpfile ppc64el 1:1.5.8-4 [105 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports/ wily/main kexec-tools ppc64el 1:2.0.9-1ubuntu1 [73.2 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports/ wily/main kdump-tools all 1:1.5.8-4 [16.7 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports/ wily-proposed/main linux-crashdump ppc64el 4.2.0.10.10 [2,410 B]
Fetched 2,891 kB in 36s (80.2 kB/s)
Preconfiguring packages ...
Selecting previously unselected package crash.
(Reading database ... 156556 files and directories currently installed.)
Preparing to unpack .../crash_7.1.1-1ubuntu3_ppc64el.deb ...
Unpacking crash (7.1.1-1ubuntu3) ...
Selecting previously unselected package makedumpfile.
Preparing to unpack .../makedumpfile_1%3a1.5.8-4_ppc64el.deb ...
Unpacking makedumpfile (1:1.5.8-4) ...
Selecting previously unselected package kexec-tools.
Preparing to unpack .../kexec-tools_1%3a2.0.9-1ubuntu1_ppc64el.deb ...
Unpacking kexec-tools (1:2.0.9-1ubuntu1) ...
Selecting previously unselected package kdump-tools.
Preparing to unpack .../kdump-tools_1%3a1.5.8-4_all.deb ...
Unpacking kdump-tools (1:1.5.8-4) ...
Selecting previously unselected package linux-crashdump.
Preparing to unpack .../linux-crashdump_4.2.0.10.10_ppc64el.deb ...
Unpacking linux-crashdump (4.2.0.10.10) ...
Processing triggers for man-db (2.7.3-1) ...
Processing triggers for systemd (225-1ubuntu4) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up crash (7.1.1-1ubuntu3) ...
Setting up makedumpfile (1:1.5.8-4) ...
Setting up kexec-tools (1:2.0.9-1ubuntu1) ...
Generating /etc/default/kexec...
Generating grub configuration file ...
Found linux image: /boot/vmlinux-4.2.0-7-generic
Found initrd image: /boot/initrd.img-4.2.0-7-generic
Found linux image: /boot/vmlinux-4.1.0-3-generic
Found initrd image: /boot/initrd.img-4.1.0-3-generic
Found linux image: /boot/vmlinux-3.19....

Read more...

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-09-17 20:09 EDT-------
(In reply to comment #6)
> I am not able to reproduce this problem on my machine:
>

I installed Ubuntu 15.10 in my lpar. After installation, I ran "apt-get update" and "apt-get install linux-crashdump", and we are still hitting this bug.

root@callalp3:~# uname -a
Linux callalp3 4.2.0-10-generic #11-Ubuntu SMP Sun Sep 13 11:24:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

root@callalp3:~# apt-get update
.......
......
Preparing to unpack .../linux-crashdump_4.2.0.10.10_ppc64el.deb ...
Unpacking linux-crashdump (4.2.0.10.10) ...
Selecting previously unselected package policykit-1.
Preparing to unpack .../policykit-1_0.105-11ubuntu1_ppc64el.deb ...
Unpacking policykit-1 (0.105-11ubuntu1) ...
Processing triggers for man-db (2.7.3-1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (225-1ubuntu4) ...
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--unpack):
subprocess installed post-installation script returned error exit status 1
Processing triggers for dbus (1.10.0-1ubuntu1) ...
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@callalp3:~# dpkg -l | grep crashdump
iU linux-crashdump 4.2.0.10.10 ppc64el Linux kernel crashdump setup for the latest generic kernel

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-09-17 20:15 EDT-------
Sorry, typo in comment 7. This is the correct one:

root@callalp3:~# apt-get install linux-crashdump
.......
......
Preparing to unpack .../linux-crashdump_4.2.0.10.10_ppc64el.deb ...
Unpacking linux-crashdump (4.2.0.10.10) ...
Selecting previously unselected package policykit-1.
Preparing to unpack .../policykit-1_0.105-11ubuntu1_ppc64el.deb ...
Unpacking policykit-1 (0.105-11ubuntu1) ...
Processing triggers for man-db (2.7.3-1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (225-1ubuntu4) ...
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--unpack):
subprocess installed post-installation script returned error exit status 1
Processing triggers for dbus (1.10.0-1ubuntu1) ...
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
bugproxy (bugproxy) wrote : putty_log

------- Comment (attachment only) From <email address hidden> 2015-09-17 20:12 EDT-------

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-09-21 19:13 EDT-------
collalp3 is using 2 cpu and 6.25 GB memory, and it is using virtual network and VSCSI disk, no physical adapters has assigned to it. VIOS is using Austin adapter (FC 5899) as the NIC.

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-10-01 06:59 EDT-------
Canonical,
Any updates?

Revision history for this message
Louis Bouchard (louis) wrote :

Hello,

The interesting part of the log is :

Processing triggers for systemd (225-1ubuntu4) ...
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--unpack):
subprocess installed post-installation script returned error exit status 1

The interesting line is :

Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)

which leads to LP: #1447654 : installing policykit-1 hangs under systemd

This was fixed in policykit-1 (0.105-10). Can you please check which version you have ?

Revision history for this message
bugproxy (bugproxy) wrote : putty_log

------- Comment (attachment only) From <email address hidden> 2015-09-17 20:12 EDT-------

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-10-05 06:43 EDT-------
YUECHANG E. MEI 2015-10-01 10:56:02 EDT

(In reply to comment #18)
> Hello,
>
> The interesting part of the log is :
>
> Processing triggers for systemd (225-1ubuntu4) ...
> Error getting authority: Error initializing authority: Error calling
> StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
> (g-io-error-quark, 24)
> Failed to execute operation: Connection timed out
> dpkg: error processing package systemd (--unpack):
> subprocess installed post-installation script returned error exit status 1
>
> The interesting line is :
>
> Error getting authority: Error initializing authority: Error calling
> StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
> (g-io-error-quark, 24)
>
> which leads to LP: #1447654 : installing policykit-1 hangs under systemd
>
> This was fixed in policykit-1 (0.105-10). Can you please check which version
> you have ?

We have policykit-1 (0.105-11), but it isn't installed successfully. I know we have a workaround for this problem. The workaround is to install policykit-1 first and install Linux-crashdump after that. My question is can we fix this problem or should we document this workaround for Ubuntu 15.10?

root@callalp3:~# dpkg -l | grep policykit
iU policykit-1 0.105-11ubuntu1 ppc64el framework for managing administrative policies and privileges

Revision history for this message
Breno Leitão (breno-leitao) wrote :

it seems that bug#1447654 was not fixed released yet. Can you double check if this version has the fix?

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-10-06 16:55 EDT-------
(In reply to comment #22)
> it seems that bug#1447654 was not fixed released yet. Can you double check
> if this version has the fix?

I reinstalled the lpar and did these after lpar boot up from installation.
1. Ran "apt-get update"
2. Ran "apt-get install linux-crashdump", select "no" when it asked "Should kexec-tools handle reboots?"
3. Then I saw this error:

Unpacking policykit-1 (0.105-11ubuntu1) ...
Processing triggers for man-db (2.7.3-1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (225-1ubuntu7) ...
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--unpack):
subprocess installed post-installation script returned error exit status 1
Processing triggers for dbus (1.10.0-1ubuntu1) ...
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@callalp3:~# dpkg -l | grep crashdump
iU linux-crashdump 4.2.0.14.15 ppc64el Linux kernel crashdump setup for the latest generic kernel
root@callalp3:~# dpkg -l | grep policykit-1
iU policykit-1 0.105-11ubuntu1 ppc64el framework for managing administrative policies and privileges

Then I tried again. I reinstalled the lpar and did the following:
1. Ran "apt-get update"
2. Ran "apt-get install policykit-1"

root@callalp3:~# dpkg -l | grep policykit
ii policykit-1 0.105-11ubuntu1 ppc64el framework for managing administrative policies and privileges

3. Ran "apt-get install linux-crashdump", select "no" when it asked "Should kexec-tools handle reboots?"
4. I didn't see the error message, and the linux-crashdump and policykit-1 packages were properly installed.

I will upload the putty screen outputs, so you can check and see the detailed output. Is these what you want me to verify? Please let me know if I missed anything, thank you!

Revision history for this message
bugproxy (bugproxy) wrote : Intall crashdump packages first and hit the error

------- Comment (attachment only) From <email address hidden> 2015-10-06 16:57 EDT-------

Revision history for this message
bugproxy (bugproxy) wrote : installed policykit first then no error

------- Comment (attachment only) From <email address hidden> 2015-10-06 16:57 EDT-------

Revision history for this message
Steve Langasek (vorlon) wrote :

This is a problem with the systemd trigger, rather than with the linux-crashdump package. Reassigning.

Signs point to bug #1447654, but that is somehow assigned to policykit-1, which AFAIK is not meant to be installed at all in a basic server environment. Martin, can you please take a look at this?

affects: linux (Ubuntu) → systemd (Ubuntu)
Changed in systemd (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
Revision history for this message
Martin Pitt (pitti) wrote :

Yes, this is indeed a duplicate of bug 1447654, and the first attempt at fixing that was not sufficient. policykit-1 did get installed as per the log in the description.

I have a gut feeling that this is related to https://github.com/systemd/systemd/issues/1505, as a recent fix for state notification has made this bug a lot more common and obvious . I've already spent days on this, but this needs some more work. However, I'll try to come up with a cheap workaround.

Steve Langasek (vorlon)
Changed in systemd (Ubuntu):
importance: Undecided → High
Revision history for this message
Martin Pitt (pitti) wrote :

The solution was much simpler; I uploaded a fix to the SRU review queues for vivid and wily. It's not available in the archive yet, it needs to be reviewed/accepted by the SRU team first.

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-10-26 17:08 EDT-------
I reinstalled the system, and the installation of linux-crashdump is fine. It seems like the problem has been fixed. Thank you!

root@callalp3:~# uname -a
Linux callalp3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 14:49:47 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
root@callalp3:~# dpkg -l | grep crashdump
ii linux-crashdump 4.2.0.16.18 ppc64el Linux kernel crashdump setup for the latest generic kernel

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-10-27 16:37 EDT-------
Problem was fixed in the latest build, I am closing this bug now.

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

Other bug subscribers

Remote bug watches

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