So, the postinst code will generate a new initrd based on the installed
kernel and write it to /var/lib/kdump/.

As you mention this is a diskless system, I wonder if there is a kernel
installed and if it shows up at /boot/ and /lib/modules/, and if it is
allowed to write to /var/lib/kdump/ and /var/crash/.

Can you confirm if there is a kernel installed and if it shows up and if
you can write to these directories as root?

Thank you very much.
Cascardo.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1850548

Title:
  Unable to install kdump tools: post install script returning fail

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Unable to install Kdump-tools.
    
  ---Steps to Reproduce---
   Unable to Install Kdump-tool Debian package kdump-tools_1.6.3-2_ppc64el.deb
  ============================================================================
  Note: Unable to install the Kdump-tool. The problem comes when postinst 
script is run:

  root@pok1-qz1-sr1-rk005-s10:~/tar# uname -a
  Linux pok1-qz1-sr1-rk005-s10 4.15.0-1039-ibm-gt #41-Ubuntu SMP Wed Oct 2 
10:52:25 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux

  root@pok1-qz1-sr1-rk005-s10:~/tar# dmesg | grep crash
  [    0.000000] Kernel command line: 
imgurl=http://192.168.0.2:80//install/netboot/ubuntu18.04/ppc64el/hostos-boot_bionic-4.15.0.1039-20191003-6f8d26a/rootimg.tar.gz
 XCAT=192.168.0.2:3001  XCATHTTPPORT=80 BOOTIF=08:94:EF:80:1B:54 console=tty0 
console=hvc0,115200 default_hugepagesz=1G hugepagesz=1G hugepages=1 
transparent_hugepage=never intel_iommu=on iommu=pt 
cloud-config-url=http://192.168.0.2/install/netboot/cloud-init/pok1-qz1-sr1-rk005-s10.txt
 ds=nocloud crashkernel=768M,low crashkernel=4G,high

  Error:
  =====
  update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write 
(write) in auto mode^M
  update-alternatives: warning: skip creation of /usr/share/man/man1/write.1.gz 
because associated file /usr/share/man/man1/bsd-write.1.gz (of link group 
write) doesn't exist^M
  update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) 
in auto mode^M
  update-alternatives: warning: skip creation of /usr/share/man/man1/from.1.gz 
because associated file /usr/share/man/man1/bsd-from.1.gz (of link group from) 
doesn't exist^M
  Setting up ifenslave (2.9ubuntu1) ...^M
  Setting up file (1:5.32-2ubuntu0.2) ...^M
  Setting up kdump-tools (1:1.6.3-2) ...^M
  ^M
  Creating config file /etc/default/kdump-tools with new version^M
  dpkg: error processing package kdump-tools (--configure):^M
   installed kdump-tools package post-installation script subprocess returned 
error exit status 1^M
  dpkg: dependency problems prevent configuration of linux-crashdump:^M
   linux-crashdump depends on kdump-tools; however:^M
    Package kdump-tools is not configured yet.^M
  ^M

  
  Detail Log:
  ===========

  root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i 
libmagic1_5.32-2ubuntu0.2_ppc64el.deb
  (Reading database ... 65250 files and directories currently installed.)
  Preparing to unpack libmagic1_5.32-2ubuntu0.2_ppc64el.deb ...
  Unpacking libmagic1:ppc64el (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ...
  Setting up libmagic1:ppc64el (1:5.32-2ubuntu0.2) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i 
libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb
  (Reading database ... 65250 files and directories currently installed.)
  Preparing to unpack libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb ...
  Unpacking libmagic-mgc (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ...
  Setting up libmagic-mgc (1:5.32-2ubuntu0.2) ...
  root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i file_5.32-2ubuntu0.2_ppc64el.deb
  (Reading database ... 65250 files and directories currently installed.)
  Preparing to unpack file_5.32-2ubuntu0.2_ppc64el.deb ...
  Unpacking file (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ...
  Setting up file (1:5.32-2ubuntu0.2) ...
  root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i 
bsdmainutils_11.1.2ubuntu1_ppc64el.deb
  (Reading database ... 65250 files and directories currently installed.)
  Preparing to unpack bsdmainutils_11.1.2ubuntu1_ppc64el.deb ...
  Unpacking bsdmainutils (11.1.2ubuntu1) over (11.1.2ubuntu1) ...
  Setting up bsdmainutils (11.1.2ubuntu1) ...
  root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i  
makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb
  (Reading database ... 65250 files and directories currently installed.)
  Preparing to unpack makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb ...
  Unpacking makedumpfile (1:1.6.5-1ubuntu1~18.04.1) over 
(1:1.6.5-1ubuntu1~18.04.1) ...
  Setting up makedumpfile (1:1.6.5-1ubuntu1~18.04.1) ...
  root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i 
kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb
  (Reading database ... 65250 files and directories currently installed.)
  Preparing to unpack kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb ...
  Unpacking kexec-tools (1:2.0.16-1ubuntu1.1) over (1:2.0.16-1ubuntu1.1) ...
  Setting up kexec-tools (1:2.0.16-1ubuntu1.1) ...
  debconf: unable to initialize frontend: Dialog
  debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
  debconf: falling back to frontend: Readline
  Configuring kexec-tools
  -----------------------

  If you choose this option, a system reboot will trigger a restart into a 
kernel loaded by kexec instead of going
  through the full system boot loader process.

  Should kexec-tools handle reboots (sysvinit only)? [yes/no] yes

  Processing triggers for ureadahead (0.100.0-21) ...
  Processing triggers for systemd (237-3ubuntu10.29) ...
  root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i kdump-tools_1.6.3-2_ppc64el.deb
  (Reading database ... 65250 files and directories currently installed.)
  Preparing to unpack kdump-tools_1.6.3-2_ppc64el.deb ...
  Unpacking kdump-tools (1:1.6.3-2) over (1:1.6.3-2) ...
  Setting up kdump-tools (1:1.6.3-2) ...
  debconf: unable to initialize frontend: Dialog
  debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
  debconf: falling back to frontend: Readline
  Configuring kdump-tools
  -----------------------

  If you choose this option, the kdump-tools mechanism will be enabled. A 
reboot is still required in order to enable
  the crashkernel kernel parameter.

  Should kdump-tools be enabled by default? [yes/no] yes

  dpkg: error processing package kdump-tools (--install):
   installed kdump-tools package post-installation script subprocess returned 
error exit status 1
  Processing triggers for ureadahead (0.100.0-21) ...
  Processing triggers for systemd (237-3ubuntu10.29) ...
  Errors were encountered while processing:
   kdump-tools

  root@pok1-qz1-sr1-rk005-s10:~/tar# DEBIAN_FRONTEND=noninteractive  dpkg -i 
kdump-tools_1.6.3-2_ppc64el.deb 
  (Reading database ... 65250 files and directories currently installed.)
  Preparing to unpack kdump-tools_1.6.3-2_ppc64el.deb ...
  Unpacking kdump-tools (1:1.6.3-2) over (1:1.6.3-2) ...
  Setting up kdump-tools (1:1.6.3-2) ...
  dpkg: error processing package kdump-tools (--install):
   installed kdump-tools package post-installation script subprocess returned 
error exit status 1
  Processing triggers for ureadahead (0.100.0-21) ...
  Processing triggers for systemd (237-3ubuntu10.29) ...
  Errors were encountered while processing:
   kdump-tools

   
  ---uname output---
  Linux pok1-qz1-sr1-rk005-s10 4.15.0-1039-ibm-gt #41-Ubuntu SMP Wed Oct 2 
10:52:25 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
   
  This is on Diskless Environment

  ====
  Can you attach the /var/log/syslog to see what sort of messages are getting 
logged (if any)?

  It might be worthwhile if you can add a set -x at the start of the
  following:

  /target/var/lib/dpkg/info/kdump-tools.postinst

  and

  /etc/kernel/postinst.d/kdump-tools

  if they exist to see what is going on in them at the time of the
  failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1850548/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to