------- Comment From [email protected] 2019-10-31 10:05 EDT-------
Hi,

Please see the detail information below
----------------------------------------------------
root@pok1-qz1-sr1-rk005-s10:~# mount | sed -e 's/^/    /g'
/proc on /proc type proc (rw,relatime)
/sys on /sys type sysfs (rw,relatime)
/dev on /dev type devtmpfs 
(rw,relatime,size=188307264k,nr_inodes=2942301,mode=755)
/dev/pts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
rootfs on / type tmpfs (rw,relatime,mode=755)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=26,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=23573)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=1024M)
tmpfs on /var/tmp type tmpfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs 
(rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
tmpfs on /run/user/0 type tmpfs 
(rw,nosuid,nodev,relatime,size=39788672k,mode=700)

root@pok1-qz1-sr1-rk005-s10:~# ls -l /boot/
total 91840
-rw------- 1 root root  3661770 Oct  8 18:31 System.map-4.15.0-1039-ibm-gt
-rw-r--r-- 1 root root   192377 Oct  8 18:31 config-4.15.0-1039-ibm-gt
drwxr-xr-x 5 root root      160 Oct  8 18:31 grub
lrwxrwxrwx 1 root root       29 Oct  8 18:31 initrd.img -> 
initrd.img-4.15.0-1039-ibm-gt
-rw-r--r-- 1 root root 53903653 Oct  8 18:31 initrd.img-4.15.0-1039-ibm-gt
-rw-r--r-- 1 root root 11537139 Oct  8 18:31 initrd.img-4.15.0-65-generic
lrwxrwxrwx 1 root root       29 Oct  8 18:31 initrd.img.old -> 
initrd.img-4.15.0-1039-ibm-gt
lrwxrwxrwx 1 root root       26 Oct  8 18:31 vmlinux -> 
vmlinux-4.15.0-1039-ibm-gt
-rw------- 1 root root 24595712 Oct  8 18:31 vmlinux-4.15.0-1039-ibm-gt
lrwxrwxrwx 1 root root       26 Oct  8 18:31 vmlinux.old -> 
vmlinux-4.15.0-1039-ibm-gt

root@pok1-qz1-sr1-rk005-s10:~# ls -l /boot/
total 91840
-rw------- 1 root root  3661770 Oct  8 18:31 System.map-4.15.0-1039-ibm-gt
-rw-r--r-- 1 root root   192377 Oct  8 18:31 config-4.15.0-1039-ibm-gt
drwxr-xr-x 5 root root      160 Oct  8 18:31 grub
lrwxrwxrwx 1 root root       29 Oct  8 18:31 initrd.img -> 
initrd.img-4.15.0-1039-ibm-gt
-rw-r--r-- 1 root root 53903653 Oct  8 18:31 initrd.img-4.15.0-1039-ibm-gt
-rw-r--r-- 1 root root 11537139 Oct  8 18:31 initrd.img-4.15.0-65-generic
lrwxrwxrwx 1 root root       29 Oct  8 18:31 initrd.img.old -> 
initrd.img-4.15.0-1039-ibm-gt
lrwxrwxrwx 1 root root       26 Oct  8 18:31 vmlinux -> 
vmlinux-4.15.0-1039-ibm-gt
-rw------- 1 root root 24595712 Oct  8 18:31 vmlinux-4.15.0-1039-ibm-gt
lrwxrwxrwx 1 root root       26 Oct  8 18:31 vmlinux.old -> 
vmlinux-4.15.0-1039-ibm-gt

root@pok1-qz1-sr1-rk005-s10:~# ls -l /lib/modules
total 0
drwxr-xr-x 6 root root 360 Oct 30 17:28 4.15.0-1039-ibm-gt

root@pok1-qz1-sr1-rk005-s10:~# ls -ld /var/lib/kdump
drwxr-xr-x 3 root root 120 Oct 30 20:05 /var/lib/kdump
root@pok1-qz1-sr1-rk005-s10:~# ls -ld /var/crash
drwxrwxrwt 2 root root 80 Oct 30 20:05 /var/crash

-- 
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     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to