← Back to team overview

kernel-packages team mailing list archive

[Bug 1594666] ProcEnviron.txt


apport information

** Attachment added: "ProcEnviron.txt"

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Multipath service fails to start in Ubuntu 16.04

Status in linux package in Ubuntu:

Bug description:
  Host OS with Support Pack - Ubuntu 16.04
  System(s) Under Test      - x86
  Adapter(s) Under Test     - Skyhawk
  Network Configuration     - Connected to Juniper Switch
  SAN Configuration         - LIO Target

  Steps To Reproduce Bug    - Enable multipath service, reboot the server.

  There is a similar bug raised but not sure if it relates to the issue I am
  getting :

  Below is the output while trying to start multipath service

  root@dhcp-10-227-28-83:~# service multipathd status
  ● multipathd.service - Device-Mapper Multipath Device Controller
     Loaded: loaded (/lib/systemd/system/multipathd.service; enabled; vendor
  preset: enabled)
     Active: active (running) (Result: timeout) since Thu 2016-04-21 20:54:36
  PDT; 1h 43min ago
   Main PID: 6156 (code=exited, status=0/SUCCESS)
     CGroup: /system.slice/multipath-tools.service
             └─2420 /sbin/multipathd

  Apr 21 22:23:37 dhcp-10-227-28-83 multipathd[6156]: could not create uxsock: 98
  Apr 21 22:23:37 dhcp-10-227-28-83 multipathd[6156]: sda: using deprecated
  getuid callout
  Apr 21 22:23:37 dhcp-10-227-28-83 multipathd[6156]: process is already running
  Apr 21 22:23:37 dhcp-10-227-28-83 multipathd[6156]: path checkers start up
  Apr 21 22:25:07 dhcp-10-227-28-83 systemd[1]: multipathd.service: Start
  operation timed out. Terminating.
  Apr 21 22:25:07 dhcp-10-227-28-83 multipathd[6156]: --------shut down-------
  Apr 21 22:25:07 dhcp-10-227-28-83 systemd[1]: Failed to start Device-Mapper
  Multipath Device Controller.
  Apr 21 22:25:07 dhcp-10-227-28-83 systemd[1]: multipathd.service: Unit entered
  failed state.
  Apr 21 22:25:07 dhcp-10-227-28-83 systemd[1]: multipathd.service: Failed with
  result 'timeout'.
  Apr 21 22:37:54 dhcp-10-227-28-83 systemd[1]: Started Device-Mapper Multipath
  Device Controller.
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/dhcp--10--227--28--83--vg-swap_1
  InstallationDate: Installed on 2016-03-29 (86 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta i386 (20160325)
  MachineType: IBM IBM System x -[7947I3S]-
  Package: linux (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic root=/dev/mapper/dhcp--10--227--28--83--vg-root ro intel_iommu=on iommu=pt
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware                            1.157
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 02/08/2011
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E150CUS-1.11]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 49Y6498
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E150CUS-1.11]-:bd02/08/2011:svnIBM:pnIBMSystemx-[7947I3S]-:pvr00:rvnIBM:rn49Y6498:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.name: IBM System x -[7947I3S]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

To manage notifications about this bug go to: