[Touch-packages] [Bug 1347504] [NEW] display screen keeps moving around when curser gets close to edge

2014-07-23 Thread Jeff Turner
Public bug reported:

ithe display moves both up and sideways on all desktops i have installed

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Jul 23 05:00:58 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed
 nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0605] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: BFG Tech Device [19f1:09be]
InstallationDate: Installed on 2014-07-21 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Dell Inc. OptiPlex GX620
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=33d95161-92aa-495a-a6f4-026768e08b97 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0HH807
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/27/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0HH807:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex GX620
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Jul 23 04:34:34 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1347504

Title:
  display screen keeps moving around when curser gets close to edge

Status in “xorg” package in Ubuntu:
  New

Bug description:
  ithe display moves both up and sideways on all desktops i have
  installed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jul 23 05:00:58 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0605] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: BFG Tech Device [19f1:09be]
  InstallationDate: Installed on 2014-07-21 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. OptiPlex GX620
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1729836] [NEW] update-initramfs generating unbootable initrd files

2017-11-03 Thread Jeff Turner
Public bug reported:

After running 'update-initramfs -u -k $(uname -r)', Linux will not boot.
With 'quiet splash' set in grub, it appears to freeze after the 'Loading
ramdisk...' message, and if booted in recovery mode, I see the following
kernel panic:

Freeing unused kernel memory: 948k
Freeing unused kernel memory: 104K
x86/mm: Chcked W+X mappings: passed, no W+X pages found.
Failed to execute /init (error -2)
Kernel panic - not syncing: No working init found.  Try passing init= optin to 
kernel. See Linux Documentation/admin-guide/init.rst for guidance.
CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu
Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011
Call Trace:
  dump_stack+0x63/0x8b
  ? rest_init+0xb0/0xc0
  panic+0xe4/0x23d
  ? putname+0x4b/0x50
  ? rest_init+0xc0/0xc0
  kernel_init+0xeb/0xfc
  ret_from_fork0x25/0x30
Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 
0x8000-0xbfff)
---[ end Kernel panic - no syncing: No working init found.  Try passing init= 
option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

(full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2).

Examining the initrd files, here is a good one, as installed by the
Ubuntu 17.10 installer:

# file /boot/initrd.img-4.13.0-16-generic
/boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC)
# ls -la /boot/initrd.img-4.13.0-16-generic
-rw-r--r-- 1 root root 50764087 Nov  3 21:02 /boot/initrd.img-4.13.0-16-generic

and here is the file after 'update-initramfs -u -k 4.13.0-16-generic':

# file /boot/initrd.img-4.13.0-16-generic
/boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu 
Nov  2 10:51:42 2017, from Unix
root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic
-rw-r--r-- 1 root root 50895514 Nov  3 21:01 /boot/initrd.img-4.13.0-16-generic

Good and bad initrds can be downloaded from
https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing

After downloading initrd.img-4.13.0-16-generic-broken, the panic can be
replicated in qemu with:

kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd
/boot/initrd.img-4.13.0-16-generic-broken

(tip obtained from https://lists.debian.org/debian-
kernel/2016/02/msg00323.html)

I've experienced this problem with Ubuntu 17.04 and 17.10 on two
separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially,
until one day I update the kernel or something, and a .deb postinst
script calls update-initramfs and trashes that kernel's initrd file. If
I run 'update-initramfs -u -k all', all my old initrd files are toast.

The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is
strange. I'm not getting many google hits on it. None of my other
Ubuntu/Debian servers use that format in their initrds.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: initramfs-tools 0.125ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Fri Nov  3 21:33:12 2017
InstallationDate: Installed on 2017-08-05 (90 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to artful on 2017-10-24 (10 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1729836

Title:
  update-initramfs generating unbootable initrd files

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After running 'update-initramfs -u -k $(uname -r)', Linux will not
  boot. With 'quiet splash' set in grub, it appears to freeze after the
  'Loading ramdisk...' message, and if booted in recovery mode, I see
  the following kernel panic:

  Freeing unused kernel memory: 948k
  Freeing unused kernel memory: 104K
  x86/mm: Chcked W+X mappings: passed, no W+X pages found.
  Failed to execute /init (error -2)
  Kernel panic - not syncing: No working init found.  Try passing init= optin 
to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
  CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu
  Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011
  Call Trace:
dump_stack+0x63/0x8b
? rest_init+0xb0/0xc0
panic+0xe4/0x23d
? putname+0x4b/0x50
? rest_init+0xc0/0xc0
kernel_init+0xeb/0xfc
ret_from_fork0x25/0x30
  Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 
0x8000-0xbfff)
  ---[ end Kernel panic - no syncing: No working init found.  Try passing init= 
option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

  (full screenshot at 

[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files

2018-01-18 Thread Jeff Turner
Sure, I've attached update-initramfs -v output, and confirmed that the
generated initrd is unusable, both with kvm and a real computer.


** Attachment added: "Output of 'update-initramfs -v' that generates an 
unusable initrd."
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1729836/+attachment/5039270/+files/update-initramfs-output.txt

** Summary changed:

- update-initramfs generating unbootable initrd files
+ update-initramfs generating unbootable initrd files when using stderred 
LD_PRELOAD hook

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1729836

Title:
  update-initramfs generating unbootable initrd files when using
  stderred LD_PRELOAD hook

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After running 'update-initramfs -u -k $(uname -r)', Linux will not
  boot. With 'quiet splash' set in grub, it appears to freeze after the
  'Loading ramdisk...' message, and if booted in recovery mode, I see
  the following kernel panic:

  Freeing unused kernel memory: 948k
  Freeing unused kernel memory: 104K
  x86/mm: Chcked W+X mappings: passed, no W+X pages found.
  Failed to execute /init (error -2)
  Kernel panic - not syncing: No working init found.  Try passing init= optin 
to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
  CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu
  Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011
  Call Trace:
dump_stack+0x63/0x8b
? rest_init+0xb0/0xc0
panic+0xe4/0x23d
? putname+0x4b/0x50
? rest_init+0xc0/0xc0
kernel_init+0xeb/0xfc
ret_from_fork0x25/0x30
  Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 
0x8000-0xbfff)
  ---[ end Kernel panic - no syncing: No working init found.  Try passing init= 
option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

  (full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2).

  Examining the initrd files, here is a good one, as installed by the
  Ubuntu 17.10 installer:

  # file /boot/initrd.img-4.13.0-16-generic
  /boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC)
  # ls -la /boot/initrd.img-4.13.0-16-generic
  -rw-r--r-- 1 root root 50764087 Nov  3 21:02 
/boot/initrd.img-4.13.0-16-generic

  and here is the file after 'update-initramfs -u -k 4.13.0-16-generic':

  # file /boot/initrd.img-4.13.0-16-generic
  /boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu 
Nov  2 10:51:42 2017, from Unix
  root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic
  -rw-r--r-- 1 root root 50895514 Nov  3 21:01 
/boot/initrd.img-4.13.0-16-generic

  Good and bad initrds can be downloaded from
  
https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing

  After downloading initrd.img-4.13.0-16-generic-broken, the panic can
  be replicated in qemu with:

  kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd
  /boot/initrd.img-4.13.0-16-generic-broken

  (tip obtained from https://lists.debian.org/debian-
  kernel/2016/02/msg00323.html)

  I've experienced this problem with Ubuntu 17.04 and 17.10 on two
  separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially,
  until one day I update the kernel or something, and a .deb postinst
  script calls update-initramfs and trashes that kernel's initrd file.
  If I run 'update-initramfs -u -k all', all my old initrd files are
  toast.

  The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is
  strange. I'm not getting many google hits on it. None of my other
  Ubuntu/Debian servers use that format in their initrds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Nov  3 21:33:12 2017
  InstallationDate: Installed on 2017-08-05 (90 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to artful on 2017-10-24 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1729836/+subscriptions

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


[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook

2018-01-18 Thread Jeff Turner
I think I figured out the cause. Basically PEBCAK..

There's a program called stderred (https://github.com/sickill/stderred)
which colorizes stderr to differentiate it from stdout, via a LD_PRELOAD
hook. I have had this set for years in my ~/.bashrc:

root@jturner-home:~# echo $LD_PRELOAD
/home/jturner/src/github/stderred/build/libstderred.so

When I examine the initrd file as follows, I see half the binaries in
bin/ contain ANSI escape codes, and the libstderred.so library has been
pulled in:

root@jturner-home:/boot# update-initramfs -u -k 4.13.0-25-generic
update-initramfs: Generating /boot/initrd.img-4.13.0-25-generic
root@jturner-home:/boot# mkdir bad
root@jturner-home:/boot# ( cd bad; zcat ../initrd.img-4.13.0-25-generic | cpio 
-idmv; )
root@jturner-home:/boot# ls 
bad/home/jturner/src/github/stderred/build/libstderred.so 
bad/home/jturner/src/github/stderred/build/libstderred.so
root@jturner-home:/boot# ls -1 bad/bin
?[0m
?[0m?[1m?[31m[[?[0m?[1m?[31m
?[0m?[1m?[31macpid?[0m?[1m?[31m
?[0m?[1m?[31mash?[0m?[1m?[31m
?[0m?[1m?[31mawk?[0m?[1m?[31m
?[0m?[1m?[31mbasename?[0m?[1m?[31m
?[0m?[1m?[31mblockdev?[0m?[1m?[31m
?[0m?[1m?[31mcat?[0m?[1m?[31m
...
?[1m?[31m[?[0m?[1m?[31m
busybox
cat
chroot
cpio
dash
date
dd
...


The output of update-initramfs goes red halfway.

Perhaps update-initramfs could sanitize its environment, or explicitly
unset LD_PRELOAD. Hard to be idiot-proof when there's such sophisticated
idiots :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1729836

Title:
  update-initramfs generating unbootable initrd files when using
  stderred LD_PRELOAD hook

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After running 'update-initramfs -u -k $(uname -r)', Linux will not
  boot. With 'quiet splash' set in grub, it appears to freeze after the
  'Loading ramdisk...' message, and if booted in recovery mode, I see
  the following kernel panic:

  Freeing unused kernel memory: 948k
  Freeing unused kernel memory: 104K
  x86/mm: Chcked W+X mappings: passed, no W+X pages found.
  Failed to execute /init (error -2)
  Kernel panic - not syncing: No working init found.  Try passing init= optin 
to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
  CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu
  Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011
  Call Trace:
dump_stack+0x63/0x8b
? rest_init+0xb0/0xc0
panic+0xe4/0x23d
? putname+0x4b/0x50
? rest_init+0xc0/0xc0
kernel_init+0xeb/0xfc
ret_from_fork0x25/0x30
  Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 
0x8000-0xbfff)
  ---[ end Kernel panic - no syncing: No working init found.  Try passing init= 
option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

  (full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2).

  Examining the initrd files, here is a good one, as installed by the
  Ubuntu 17.10 installer:

  # file /boot/initrd.img-4.13.0-16-generic
  /boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC)
  # ls -la /boot/initrd.img-4.13.0-16-generic
  -rw-r--r-- 1 root root 50764087 Nov  3 21:02 
/boot/initrd.img-4.13.0-16-generic

  and here is the file after 'update-initramfs -u -k 4.13.0-16-generic':

  # file /boot/initrd.img-4.13.0-16-generic
  /boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu 
Nov  2 10:51:42 2017, from Unix
  root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic
  -rw-r--r-- 1 root root 50895514 Nov  3 21:01 
/boot/initrd.img-4.13.0-16-generic

  Good and bad initrds can be downloaded from
  
https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing

  After downloading initrd.img-4.13.0-16-generic-broken, the panic can
  be replicated in qemu with:

  kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd
  /boot/initrd.img-4.13.0-16-generic-broken

  (tip obtained from https://lists.debian.org/debian-
  kernel/2016/02/msg00323.html)

  I've experienced this problem with Ubuntu 17.04 and 17.10 on two
  separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially,
  until one day I update the kernel or something, and a .deb postinst
  script calls update-initramfs and trashes that kernel's initrd file.
  If I run 'update-initramfs -u -k all', all my old initrd files are
  toast.

  The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is
  strange. I'm not getting many google hits on it. None of my other
  Ubuntu/Debian servers use that format in their initrds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  

[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook

2018-01-18 Thread Jeff Turner
Logged at https://github.com/sickill/stderred/issues/63

** Bug watch added: github.com/sickill/stderred/issues #63
   https://github.com/sickill/stderred/issues/63

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1729836

Title:
  update-initramfs generating unbootable initrd files when using
  stderred LD_PRELOAD hook

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After running 'update-initramfs -u -k $(uname -r)', Linux will not
  boot. With 'quiet splash' set in grub, it appears to freeze after the
  'Loading ramdisk...' message, and if booted in recovery mode, I see
  the following kernel panic:

  Freeing unused kernel memory: 948k
  Freeing unused kernel memory: 104K
  x86/mm: Chcked W+X mappings: passed, no W+X pages found.
  Failed to execute /init (error -2)
  Kernel panic - not syncing: No working init found.  Try passing init= optin 
to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
  CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu
  Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011
  Call Trace:
dump_stack+0x63/0x8b
? rest_init+0xb0/0xc0
panic+0xe4/0x23d
? putname+0x4b/0x50
? rest_init+0xc0/0xc0
kernel_init+0xeb/0xfc
ret_from_fork0x25/0x30
  Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 
0x8000-0xbfff)
  ---[ end Kernel panic - no syncing: No working init found.  Try passing init= 
option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

  (full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2).

  Examining the initrd files, here is a good one, as installed by the
  Ubuntu 17.10 installer:

  # file /boot/initrd.img-4.13.0-16-generic
  /boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC)
  # ls -la /boot/initrd.img-4.13.0-16-generic
  -rw-r--r-- 1 root root 50764087 Nov  3 21:02 
/boot/initrd.img-4.13.0-16-generic

  and here is the file after 'update-initramfs -u -k 4.13.0-16-generic':

  # file /boot/initrd.img-4.13.0-16-generic
  /boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu 
Nov  2 10:51:42 2017, from Unix
  root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic
  -rw-r--r-- 1 root root 50895514 Nov  3 21:01 
/boot/initrd.img-4.13.0-16-generic

  Good and bad initrds can be downloaded from
  
https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing

  After downloading initrd.img-4.13.0-16-generic-broken, the panic can
  be replicated in qemu with:

  kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd
  /boot/initrd.img-4.13.0-16-generic-broken

  (tip obtained from https://lists.debian.org/debian-
  kernel/2016/02/msg00323.html)

  I've experienced this problem with Ubuntu 17.04 and 17.10 on two
  separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially,
  until one day I update the kernel or something, and a .deb postinst
  script calls update-initramfs and trashes that kernel's initrd file.
  If I run 'update-initramfs -u -k all', all my old initrd files are
  toast.

  The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is
  strange. I'm not getting many google hits on it. None of my other
  Ubuntu/Debian servers use that format in their initrds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Nov  3 21:33:12 2017
  InstallationDate: Installed on 2017-08-05 (90 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to artful on 2017-10-24 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1729836/+subscriptions

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


[Touch-packages] [Bug 1887744] [NEW] systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798

2020-07-15 Thread Jeff Turner
Public bug reported:

On an Ubuntu 20.04 server, when I started a newly installed systemd
service 'systemctl start testemail2jira.service', systemd trips on an
assertion (from journalctl):

Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at 
src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting.
Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 
2906637.
Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution.

apport generates a core dump which I trust is attached.

The server still works, but my terminal keeps showing:

Failed to get properties: Failed to activate service
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

and pauses for 25s after each command.

In case it's relevant, the  i was trying to start had just been
symlinked into /etc/systemd/system/:

root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service
lrwxrwxrwx 1 root root 82 Jul 16 13:48 
/etc/systemd/system/testemail2jira.service -> 
/opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service

File contents:

[Unit]
Description=Check that email to %i JIRA works

[Service]
#Type=oneshot
# Note: I keep the config file, testemail2jira.json5 and rsa.* files in 
emailprocessing/, one directory below testemail2jira/, so that they can be 
version-controlled independently.
# If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add 
testemail2jira/ to WorkingDirectory and remove it from the ExecStart command
WorkingDirectory=/opt/atlassian/%i/current/emailprocessing
ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python
 testemail2jira/testemail2jira.py
User=root

[Install] 
WantedBy=multi-user.target


Perhaps the problem is that my service file is a template 
(testemail2jira@.service), but I symlinked it as a regular 
'testemail2jira.service'.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jul 16 14:13:06 2020
InstallationDate: Installed on 2020-05-27 (49 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
 
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro 
console=ttyS0,19200n8 net.ifnames=0
SourcePackage: systemd
SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] 
failed with exit code 1: Failed to get properties: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-3.1
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-3.1
dmi.sys.vendor: QEMU

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1887744

Title:
  systemd dumps core on starting service: Assertion 'u->instance' failed
  at src/core/load-fragment.c:4798

Status in systemd package in Ubuntu:
  New

Bug description:
  On an Ubuntu 20.04 server, when I started a newly installed systemd
  service 'systemctl start testemail2jira.service', systemd trips on an
  assertion (from journalctl):

  Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed 
at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as 
pid 2906637.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution.

  apport generates a core dump which I trust is attached.

  The server still works, but my terminal keeps showing:

  Failed to get properties: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  and pauses for 25s after each command.

  In case it's relevant, the  i was trying to start had just
  been symlinked into /etc/systemd/system/:

  root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service
  lrwxrwxrwx 1 root root 82 Jul 16 13:48 
/etc/systemd/system/testemail2jira.service -> 

[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798

2020-07-17 Thread Jeff Turner
Sorry, turns out the /etc/systemd/system service file needs to be a
symlink to trigger the bug. This will do it:

su -
cat < /crashsystemd@.service
[Unit]
Description=Template for instance %i

[Service]
ExecStart=/bin/true
EOF

cd /etc/systemd/system
ln -s /crashsystemd@.service crashsystemd.service
systemctl daemon-reload
systemctl start crashsystemd


After the 'systemctl start crashsystemd' my terminal says:

Failed to start crashsystemd.service: Connection reset by peer
See system logs and 'systemctl status crashsystemd.service' for details.

and in the systemd logs I see:

Jul 17 23:20:33 jturner-desktop systemd[1]: Assertion 'u->instance'
failed at src/core/load-fragment.c:4798, function unit_load_fragment().
Aborting.


Things are pretty broken now. 'systemctl' and 'reboot' commands won't work. 
Don't forget to delete the /etc/systemd/system/crashsystemd.service symlink 
before rebooting.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1887744

Title:
  systemd dumps core on starting service: Assertion 'u->instance' failed
  at src/core/load-fragment.c:4798

Status in systemd package in Ubuntu:
  New

Bug description:
  On an Ubuntu 20.04 server, when I started a newly installed systemd
  service 'systemctl start testemail2jira.service', systemd trips on an
  assertion (from journalctl):

  Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed 
at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as 
pid 2906637.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution.

  apport generates a core dump which I trust is attached.

  The server still works, but my terminal keeps showing:

  Failed to get properties: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  and pauses for 25s after each command.

  In case it's relevant, the  i was trying to start had just
  been symlinked into /etc/systemd/system/:

  root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service
  lrwxrwxrwx 1 root root 82 Jul 16 13:48 
/etc/systemd/system/testemail2jira.service -> 
/opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service

  File contents:

  [Unit]
  Description=Check that email to %i JIRA works

  [Service]
  #Type=oneshot
  # Note: I keep the config file, testemail2jira.json5 and rsa.* files in 
emailprocessing/, one directory below testemail2jira/, so that they can be 
version-controlled independently.
  # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add 
testemail2jira/ to WorkingDirectory and remove it from the ExecStart command
  WorkingDirectory=/opt/atlassian/%i/current/emailprocessing
  
ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python
 testemail2jira/testemail2jira.py
  User=root

  [Install] 
  WantedBy=multi-user.target

  
  Perhaps the problem is that my service file is a template 
(testemail2jira@.service), but I symlinked it as a regular 
'testemail2jira.service'.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jul 16 14:13:06 2020
  InstallationDate: Installed on 2020-05-27 (49 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro 
console=ttyS0,19200n8 net.ifnames=0
  SourcePackage: systemd
  SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 
'Error:'] failed with exit code 1: Failed to get properties: Failed to activate 
service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798

2020-07-16 Thread Jeff Turner
Attached is /var/crash/_usr_lib_systemd_systemd.0.crash

** Attachment added: "/var/crash/_usr_lib_systemd_systemd.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+attachment/5393190/+files/_usr_lib_systemd_systemd.0.crash

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1887744

Title:
  systemd dumps core on starting service: Assertion 'u->instance' failed
  at src/core/load-fragment.c:4798

Status in systemd package in Ubuntu:
  New

Bug description:
  On an Ubuntu 20.04 server, when I started a newly installed systemd
  service 'systemctl start testemail2jira.service', systemd trips on an
  assertion (from journalctl):

  Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed 
at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as 
pid 2906637.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution.

  apport generates a core dump which I trust is attached.

  The server still works, but my terminal keeps showing:

  Failed to get properties: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  and pauses for 25s after each command.

  In case it's relevant, the  i was trying to start had just
  been symlinked into /etc/systemd/system/:

  root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service
  lrwxrwxrwx 1 root root 82 Jul 16 13:48 
/etc/systemd/system/testemail2jira.service -> 
/opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service

  File contents:

  [Unit]
  Description=Check that email to %i JIRA works

  [Service]
  #Type=oneshot
  # Note: I keep the config file, testemail2jira.json5 and rsa.* files in 
emailprocessing/, one directory below testemail2jira/, so that they can be 
version-controlled independently.
  # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add 
testemail2jira/ to WorkingDirectory and remove it from the ExecStart command
  WorkingDirectory=/opt/atlassian/%i/current/emailprocessing
  
ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python
 testemail2jira/testemail2jira.py
  User=root

  [Install] 
  WantedBy=multi-user.target

  
  Perhaps the problem is that my service file is a template 
(testemail2jira@.service), but I symlinked it as a regular 
'testemail2jira.service'.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jul 16 14:13:06 2020
  InstallationDate: Installed on 2020-05-27 (49 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro 
console=ttyS0,19200n8 net.ifnames=0
  SourcePackage: systemd
  SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 
'Error:'] failed with exit code 1: Failed to get properties: Failed to activate 
service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+subscriptions

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


[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798

2020-07-16 Thread Jeff Turner
Replicated on my local Ubuntu 20.04 system with systemd
245.4-4ubuntu3.1.

It's a PEBCAK error where a user writes a .service file containing %i's,
but instead of naming the file foo@bar.service, just names it
foo.service. To replicate:

cd /etc/systemd/system
curl -s -o testemail2jira.service 
'https://hg.sr.ht/~redradishtech/testemail2jira/raw/testemail2jira%40.service?rev=tip'
systemctl daemon-reload
systemctl start testemail2jira

On one of the last two steps everything freezes, errors start appearing:

[system] Failed to activate service 'org.freedesktop.systemd1': timed
out (service_start_timeout=25000ms)

and /var/crash/_usr_lib_systemd_systemd.0.crash is created.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1887744

Title:
  systemd dumps core on starting service: Assertion 'u->instance' failed
  at src/core/load-fragment.c:4798

Status in systemd package in Ubuntu:
  New

Bug description:
  On an Ubuntu 20.04 server, when I started a newly installed systemd
  service 'systemctl start testemail2jira.service', systemd trips on an
  assertion (from journalctl):

  Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed 
at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as 
pid 2906637.
  Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution.

  apport generates a core dump which I trust is attached.

  The server still works, but my terminal keeps showing:

  Failed to get properties: Failed to activate service
  'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

  and pauses for 25s after each command.

  In case it's relevant, the  i was trying to start had just
  been symlinked into /etc/systemd/system/:

  root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service
  lrwxrwxrwx 1 root root 82 Jul 16 13:48 
/etc/systemd/system/testemail2jira.service -> 
/opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service

  File contents:

  [Unit]
  Description=Check that email to %i JIRA works

  [Service]
  #Type=oneshot
  # Note: I keep the config file, testemail2jira.json5 and rsa.* files in 
emailprocessing/, one directory below testemail2jira/, so that they can be 
version-controlled independently.
  # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add 
testemail2jira/ to WorkingDirectory and remove it from the ExecStart command
  WorkingDirectory=/opt/atlassian/%i/current/emailprocessing
  
ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python
 testemail2jira/testemail2jira.py
  User=root

  [Install] 
  WantedBy=multi-user.target

  
  Perhaps the problem is that my service file is a template 
(testemail2jira@.service), but I symlinked it as a regular 
'testemail2jira.service'.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jul 16 14:13:06 2020
  InstallationDate: Installed on 2020-05-27 (49 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro 
console=ttyS0,19200n8 net.ifnames=0
  SourcePackage: systemd
  SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 
'Error:'] failed with exit code 1: Failed to get properties: Failed to activate 
service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+subscriptions

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


[Touch-packages] [Bug 1170353] Re: Host names intermittently resolve to 0.0.0.0

2021-01-06 Thread Jeff Turner
It's happened to me a few times on 20.04.1:

$ host support.coinjar.com 
support.coinjar.com has address 0.0.0.0
support.coinjar.com has IPv6 address :: 
   
support.coinjar.com is an alias for coinjar.zendesk.com.
coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com.  

$ sudo resolvectl flush-caches 

$ host support.coinjar.com 
support.coinjar.com has address 0.0.0.0
support.coinjar.com has IPv6 address ::
support.coinjar.com is an alias for coinjar.zendesk.com.
coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com.

$ dig support.coinjar.com

; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12759
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;support.coinjar.com.   IN  A

;; ANSWER SECTION:
support.coinjar.com.34  IN  A   0.0.0.0

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Jan 06 20:23:28 AEDT 2021
;; MSG SIZE  rcvd: 64


Then 2 minutes later the problem resolves itself:


$ dig support.coinjar.com

; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64605
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;support.coinjar.com.   IN  A

;; ANSWER SECTION:
support.coinjar.com.151 IN  CNAME   coinjar.zendesk.com.
coinjar.zendesk.com.900 IN  A   104.16.51.111
coinjar.zendesk.com.900 IN  A   104.16.53.111

;; Query time: 68 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Jan 06 20:25:31 AEDT 2021
;; MSG SIZE  rcvd: 110


Nothing in /var/log/syslog or systemd-resolved's systemd log.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1170353

Title:
  Host names intermittently resolve to 0.0.0.0

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  About 5% of DNS queries resolve to 0.0.0.0.

  A couple of times an hour during normal browsing, Firefox resolves a
  domain to 0.0.0.0. Opening the same site in Chrome has a 50% chance of
  it working, then it normally works after a few reloads. Thunderbird
  has also occasionally resolved googlemail.com to 0.0.0.0. Domains
  include google.com, wikipedia.org, harvestapp.com and many more.

  I couldn't reproduce this with dig/nslookup for a while, but after 5
  minutes of (re)trying random domains) did:

  $ dig mail.google.com

  ; <<>> DiG 9.8.1-P1 <<>> mail.google.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22905
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;mail.google.com. IN  A

  ;; ANSWER SECTION:
  mail.google.com.  60  IN  A   0.0.0.0

  ;; Query time: 0 msec
  ;; SERVER: 127.0.1.1#53(127.0.1.1)
  ;; WHEN: Thu Apr 18 13:57:04 2013
  ;; MSG SIZE  rcvd: 49

  Note the "0 msec", so I'm pretty sure this is dnsmasq's local cache.

  Using Xubuntu 12.10, NetworkManager 0.9.6.0,  Dnsmasq 2.63rc6.

  NetworkManager has DNS servers set to "8.8.8.8, 8.8.4.4" (also tried
  setting it to my router's DNS server, with no effect).

  /etc/resolve.conf just has "nameserver 127.0.1.1"

  dnsmasq is currently running:

  /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-
  interfaces --pid-file=/var/run/sendsigs.omit.d/network-
  manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run
  /nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-
  dbus=org.freedesktop.NetworkManager.dnsmasq --conf-
  dir=/etc/NetworkManager/dnsmasq.d

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Apr 18 14:27:33 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-01-11 (97 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static 
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.10  metric 1 
   169.254.0.0/16 dev eth0  scope