[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic

2024-02-01 Thread Dominic Raferd 
Despite my comment above, I still have this problem when using netplan.
Here is my /etc/netplan/config.yaml (external IP quatrains have been
changed), the setup is that enp8s1 provides internet access (with metric
49) and enp7s0 provides local lan access *and* (with metric 51) fallback
internet access:

network:
  version: 2
  renderer: networkd
  ethernets:
enp8s1:
  dhcp4: false
  wakeonlan: true
  addresses: [111.94.100.80/24]
  nameservers:
addresses: [111.94.100.1]
  # makes this the default route - deprecated
  #gateway4: 111.94.100.1
  link-local: []
  routes:
  - to: default
via: 111.94.100.1
metric: 49
on-link: true
enp7s0:
  dhcp4: false
  wakeonlan: true
  addresses: [192.168.20.88/24]
  nameservers:
addresses: [192.168.20.1]
  link-local: []
  routes:
  - to: default
via: 192.168.20.1
metric: 51
on-link: true
# to avoid conflict with enp8s1 default route, but makes no difference
#table: 76
  - to: 192.168.20.0/24
via: 192.168.20.1
metric: 48

When working properly:
# ip route show to default
default via 111.94.100.1 dev enp8s1 proto static metric 49 onlink
default via 192.168.20.1 dev enp7s0 proto static metric 51 onlink

But after systemd reconfiguration we have two default routes with a
metric of 0! We have to delete one of them to restore the correct setup
(as above) and get internet access via enp8s1 again. My workaround is
continuous monitoring of syslog for a line indicating that the network
has been (re)configured by systemd and then running some bash code like
this (extract):

if [[ -n $(ip route show to default metric 0 via 192.168.20.1) ]]; then
  NUM_DEFAULT_ROUTES=$(ip route show to default|wc -l)
  if [[ $NUM_DEFAULT_ROUTES -gt 2 ]]; then
ip route delete to default metric 0 via 192.168.20.1
  fi
fi

-- 
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/1782709

Title:
  Updating systemd kills network on bionic

Status in linux package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I do have an ubuntu bionic server installation without a graphical interface. 
The server
  has two active network adapters, both connected to the internet. One is used 
for outgoing
  internet traffic, the other for incoming. The incoming adapter lives on a 
public network segment
  (something like 88.236.133.104/29). I do have multiple servers within this 
segment.

  Typically, I update the server regularly, meaning:

  * ssh to the incoming adapter: ssh 88.236.133.108
  * apt-get update
  * apt-get upgrade
  * apt-get dist-upgrade
  * apt-get clean
  * reboot

  It used to work ok.

  BUT: Today, "apt-get upgrade" seem to take really long when updating systemd.
  After a could of minutes, I realized that the ssh session became inactive. I 
couldn't type
  into it, I had to abort it via ~. .

  * ssh from the internet to the incoming adapter was not working anymore - ssh 
88.236.133.108
  * ssh via another server within the public network segment worked
  * ssh 88.236.133.106 -> ssh 88.236.133.108
  * After running "netplan apply" everything was fine again

  Here my netplan configuration (I changed the ip addresses):

  network:
version: 2
renderer: networkd
ethernets:
  eno1:
dhcp4: yes
  eno2:
dhcp4: no
addresses: [88.236.133.108/29]
#gateway4: 88.236.133.105
routes:
 - to: 0.0.0.0/0
   via: 88.236.133.105
   table: 120
routing-policy:
 - from: 88.236.133.108/32
   table: 120
 - to: 88.236.133.108/32
   table: 120

  Unfortunately, I don't have the console output avalable anymore.
  Shall I provide additional info?

  Best regards, Uli
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 20 08:10 seq
   crw-rw 1 root audio 116, 33 Jul 20 08:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-14 (5 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM IBM System x -[794582G]-
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine:

[Touch-packages] [Bug 1977689] Re: Wrong error msg: "state file /var/lib/logrotate/status is world-readable" although it is not

2022-06-09 Thread Dominic Raferd 
+1

I see the same after upgrading to Ubuntu 22.04. Two problems I think:
- it is not really an error since the file is *not* world-readable
- if the file was world-readable the message should I think say 'cannot', not 
'can'

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

Title:
  Wrong error msg: "state file /var/lib/logrotate/status is world-
  readable" although it is not

Status in logrotate package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04
  logrotate 3.19.0-1ubuntu1.1

  Every hour, I receive this wrong message:

  Subject:  Cron >cd / && run-parts --report 
/etc/cron.hourly
  /etc/cron.hourly/logrotate:
  error: state file /var/lib/logrotate/status is world-readable and thus can be 
locked from other unprivileged users. Skipping lock acquisition...

  despite:

  # ls -al /var/lib/logrotate
  total 40
  drwxr-x---  2 root root  4096 Jun  5 17:17 .
  drwxr-xr-x 66 root root  4096 Jun  3 20:02 ..
  -rw-r-  1 root root 31974 Jun  5 17:17 status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1977689/+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 1782709] Re: Updating systemd kills network on bionic

2021-08-30 Thread Dominic Raferd 
I changed my networking setup to use netplan and the problem
disappeared.

-- 
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/1782709

Title:
  Updating systemd kills network on bionic

Status in linux package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I do have an ubuntu bionic server installation without a graphical interface. 
The server
  has two active network adapters, both connected to the internet. One is used 
for outgoing
  internet traffic, the other for incoming. The incoming adapter lives on a 
public network segment
  (something like 88.236.133.104/29). I do have multiple servers within this 
segment.

  Typically, I update the server regularly, meaning:

  * ssh to the incoming adapter: ssh 88.236.133.108
  * apt-get update
  * apt-get upgrade
  * apt-get dist-upgrade
  * apt-get clean
  * reboot

  It used to work ok.

  BUT: Today, "apt-get upgrade" seem to take really long when updating systemd.
  After a could of minutes, I realized that the ssh session became inactive. I 
couldn't type
  into it, I had to abort it via ~. .

  * ssh from the internet to the incoming adapter was not working anymore - ssh 
88.236.133.108
  * ssh via another server within the public network segment worked
  * ssh 88.236.133.106 -> ssh 88.236.133.108
  * After running "netplan apply" everything was fine again

  Here my netplan configuration (I changed the ip addresses):

  network:
version: 2
renderer: networkd
ethernets:
  eno1:
dhcp4: yes
  eno2:
dhcp4: no
addresses: [88.236.133.108/29]
#gateway4: 88.236.133.105
routes:
 - to: 0.0.0.0/0
   via: 88.236.133.105
   table: 120
routing-policy:
 - from: 88.236.133.108/32
   table: 120
 - to: 88.236.133.108/32
   table: 120

  Unfortunately, I don't have the console output avalable anymore.
  Shall I provide additional info?

  Best regards, Uli
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 20 08:10 seq
   crw-rw 1 root audio 116, 33 Jul 20 08:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-14 (5 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM IBM System x -[794582G]-
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/07/2014
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E162AUS-1.20]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 00D4062
  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-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.family: System x
  dmi.product.name: IBM System x -[794582G]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+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 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

2021-01-07 Thread Dominic Raferd 
my problem is I think likely better covered by
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709

-- 
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/1803391

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  
  [Impact] 

   * Installation of latest systemd update in -security hangs with
  current versions of unattended-upgrades in supported releases. The
  u-u-side fix is tracked in LP: #1778219.

  
  [Regression Potential] 

   * The daemons, shipped in deb:systemd, are not attempted to be
  restarted because despite package installation the system is in the
  middle of shutting down. This means that currently running daemons may
  be helding up open files on the filesystem, however all process are
  being stopped and killed as part of shutdown. Hence the worst possible
  regression from this, is an unclean shutdown, but even that shouldn't
  happen with this update.

  [Test Case]

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
  root@uu-systemd-onshutdown:~# reboot

  Session terminated, terminating shell...Terminated
  root@uu-systemd-
  rbalint@yogi:~$
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
  Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up systemd (237-3ubuntu10.6) ...
  Failed to try-restart systemd-networkd.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-networkd.service' for

[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

2021-01-07 Thread Dominic Raferd 
TTFN: 
To add to (and correct) my earlier comments: after the updating shown there, 
the machine had to be rebooted manually. Checking /var/log/apt/term.log it 
appears that the upgrade did complete successfully:

Log started: 2021-01-07  13:28:19
(Reading database ... 151099 files and directories currently installed.)
Preparing to unpack .../libnss-systemd_237-3ubuntu10.43_i386.deb ...
Unpacking libnss-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ...
Preparing to unpack .../libpam-systemd_237-3ubuntu10.43_i386.deb ...
Unpacking libpam-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ...
Preparing to unpack .../systemd_237-3ubuntu10.43_i386.deb ...
Unpacking systemd (237-3ubuntu10.43) over (237-3ubuntu10.42) ...
Preparing to unpack .../libsystemd0_237-3ubuntu10.43_i386.deb ...
Unpacking libsystemd0:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ...
Setting up libsystemd0:i386 (237-3ubuntu10.43) ...
Setting up systemd (237-3ubuntu10.43) ...
Setting up libnss-systemd:i386 (237-3ubuntu10.43) ...
Setting up libpam-systemd:i386 (237-3ubuntu10.43) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for dbus (1.12.2-1ubuntu1.2) ...
Processing triggers for ureadahead (0.100.0-21) ...
Log ended: 2021-01-07  13:29:10

... this even though the (ssh) interface died at the point where systemd
was being set up. The system now runs systemd 237-3ubuntu10.43. But
based on past experience I think the same thing will happen the next
time there is a version upgrade of systemd.

-- 
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/1803391

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  
  [Impact] 

   * Installation of latest systemd update in -security hangs with
  current versions of unattended-upgrades in supported releases. The
  u-u-side fix is tracked in LP: #1778219.

  
  [Regression Potential] 

   * The daemons, shipped in deb:systemd, are not attempted to be
  restarted because despite package installation the system is in the
  middle of shutting down. This means that currently running daemons may
  be helding up open files on the filesystem, however all process are
  being stopped and killed as part of shutdown. Hence the worst possible
  regression from this, is an unclean shutdown, but even that shouldn't
  happen with this update.

  [Test Case]

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]

[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

2021-01-07 Thread Dominic Raferd 
I have this problem with Ubuntu 18.04 system set up with 'encrypted LVM'
(standard Ubuntu recipe as per the alternate installer). Whenever there
is systemd upgrade it hangs (whole machine crashes - other logins not
possible) and has to be manually rebooted (which is not ideal as the
machine is 1500 miles away). Note the installed version of systemd seems
to be 237-3ubuntu10.42, obviously I am unable to update it.

I have another machine also Ubuntu 18.04 system set up with 'encrypted
LVM' which has systemd 237-3ubuntu10.43 and does not have this problem.

Latest instance of this problem:
# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libnss-systemd libpam-systemd libsystemd0 systemd
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,414 kB of archives.
After this operation, 7,168 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libnss-systemd 
i386 237-3ubuntu10.43 [111 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libpam-systemd 
i386 237-3ubuntu10.43 [114 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 systemd i386 
237-3ubuntu10.43 [2,964 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libsystemd0 
i386 237-3ubuntu10.43 [225 kB]
Fetched 3,414 kB in 1s (3,309 kB/s)
(Reading database ... 151099 files and directories currently installed.)
Preparing to unpack .../libnss-systemd_237-3ubuntu10.43_i386.deb ...
Unpacking libnss-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ...
Preparing to unpack .../libpam-systemd_237-3ubuntu10.43_i386.deb ...
Unpacking libpam-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ...
Preparing to unpack .../systemd_237-3ubuntu10.43_i386.deb ...
Unpacking systemd (237-3ubuntu10.43) over (237-3ubuntu10.42) ...
Preparing to unpack .../libsystemd0_237-3ubuntu10.43_i386.deb ...
Unpacking libsystemd0:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ...
Setting up libsystemd0:i386 (237-3ubuntu10.43) ...
Setting up systemd (237-3ubuntu10.43) ...

[system dies]

-- 
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/1803391

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  
  [Impact] 

   * Installation of latest systemd update in -security hangs with
  current versions of unattended-upgrades in supported releases. The
  u-u-side fix is tracked in LP: #1778219.

  
  [Regression Potential] 

   * The daemons, shipped in deb:systemd, are not attempted to be
  restarted because despite package installation the system is in the
  middle of shutting down. This means that currently running daemons may
  be helding up open files on the filesystem, however all process are
  being stopped and killed as part of shutdown. Hence the worst possible
  regression from this, is an unclean shutdown, but even that shouldn't
  happen with this update.

  [Test Case]

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64

[Touch-packages] [Bug 1802090] Re: update overwrites sshd_config

2018-11-07 Thread Dominic Raferd 
attached: /var/log/apt/term.log

** Attachment added: "term.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+attachment/5210010/+files/term.log.gz

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

Title:
  update overwrites sshd_config

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  The latest update for Bionic (18.04.1) either overwrote or modified my
  /etc/ssh/sshd_config with the result that I could no longer access my
  machine using ssh.

  A specific
  Port [x]
  line was removed and replaced by:
  #Port 22

  This was the only change. It happened as part of an automated process
  this morning  - presumably a security update.

  Was this behaviour intended?!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+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

Re: [Touch-packages] [Bug 1802090] Re: update overwrites sshd_config

2018-11-07 Thread Dominic Raferd 
The update to 18.04 was a long time ago, the problem occurred this
morning...

On Wed, 7 Nov 2018 at 13:01, Marc Deslauriers <
marc.deslauri...@canonical.com> wrote:

> It looks like you upgraded from Ubuntu 16.04 to Ubuntu 18.04.
> >From the log file:
>
> Unpacking openssh-server (1:7.6p1-4) over (1:7.2p2-4ubuntu2.4) ...
>
> Then the upgrade asked you what to do with the modified conffile, again,
> from the log:
>
> Configuring openssh-server
> sshd_config: A new version (/tmp/filerMG8sJ) of configuration file
> /etc/ssh/sshd_config is available, but the
> version installed currently has been locally modified.
> What do you want to do about modified configuration file sshd_config?
>  install the package maintainer's
> version
> keep the local version currently installed
> show the differences between the versions
> show a side-by-side difference between the versions
> start a new shell to examine the situation
> 
> # nano /tmp/filerMG8sJ
> 
> Replacing config file /etc/ssh/sshd_config with new version
>
> At which point you edited the file and instructed the upgrade process to
> use the new package version.
>
> I'm not quite sure what you expect this bug to resolve, the package
> seems to be acting as it should.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1802090
>
> Title:
>   update overwrites sshd_config
>
> Status in openssh package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The latest update for Bionic (18.04.1) either overwrote or modified my
>   /etc/ssh/sshd_config with the result that I could no longer access my
>   machine using ssh.
>
>   A specific
>   Port [x]
>   line was removed and replaced by:
>   #Port 22
>
>   This was the only change. It happened as part of an automated process
>   this morning  - presumably a security update.
>
>   Was this behaviour intended?!
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+subscriptions
>

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

Title:
  update overwrites sshd_config

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  The latest update for Bionic (18.04.1) either overwrote or modified my
  /etc/ssh/sshd_config with the result that I could no longer access my
  machine using ssh.

  A specific
  Port [x]
  line was removed and replaced by:
  #Port 22

  This was the only change. It happened as part of an automated process
  this morning  - presumably a security update.

  Was this behaviour intended?!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+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 1802090] Re: update overwrites sshd_config

2018-11-07 Thread Dominic Raferd 
It was an automatic update, file attached

** Attachment added: "apt-term.log"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+attachment/5209992/+files/apt-term.log.gz

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

Title:
  update overwrites sshd_config

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  The latest update for Bionic (18.04.1) either overwrote or modified my
  /etc/ssh/sshd_config with the result that I could no longer access my
  machine using ssh.

  A specific
  Port [x]
  line was removed and replaced by:
  #Port 22

  This was the only change. It happened as part of an automated process
  this morning  - presumably a security update.

  Was this behaviour intended?!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+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 1802090] [NEW] update overwrites sshd_config

2018-11-07 Thread Dominic Raferd 
Public bug reported:

The latest update for Bionic (18.04.1) either overwrote or modified my
/etc/ssh/sshd_config with the result that I could no longer access my
machine using ssh.

A specific
Port [x]
line was removed and replaced by:
#Port 22

This was the only change. It happened as part of an automated process
this morning  - presumably a security update.

Was this behaviour intended?!

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

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

Title:
  update overwrites sshd_config

Status in openssh package in Ubuntu:
  New

Bug description:
  The latest update for Bionic (18.04.1) either overwrote or modified my
  /etc/ssh/sshd_config with the result that I could no longer access my
  machine using ssh.

  A specific
  Port [x]
  line was removed and replaced by:
  #Port 22

  This was the only change. It happened as part of an automated process
  this morning  - presumably a security update.

  Was this behaviour intended?!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+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 1085766] Re: /var/log/upstart/ureadahead.log contains garbage

2016-10-07 Thread Dominic Raferd 
I have this too with Xenial. Looking at yesterday's syslog:

$ sudo grep -c "Ignored relative path" /var/log/syslog.1
19728

and here are the first few lines:

$ sudo grep -m30 ureadahead /var/log/syslog.1
Oct  6 08:00:20 dl1 systemd[1]: Stopped Stop ureadahead data collection 45s 
after completed startup.
Oct  6 08:01:02 dl1 systemd[1]: Started Stop ureadahead data collection 45s 
after completed startup.
Oct  6 08:01:47 dl1 systemd[1]: Starting Stop ureadahead data collection...
Oct  6 08:01:47 dl1 systemd[1]: Started Stop ureadahead data collection.
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:events/fs/open_exec/enable: 
Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:buffer_size_kb: Ignored 
relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:tracing_on: Ignored relative 
path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:binfmt_misc: Ignored relative 
path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:dm/uuid: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: message repeated 11 times: [ 
ureadahead:dm/uuid: Ignored relative path]
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:.: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:1/stat: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:1/cmdline: Ignored relative path

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

Title:
  /var/log/upstart/ureadahead.log contains garbage

Status in linux package in Ubuntu:
  Fix Released
Status in ureadahead package in Ubuntu:
  Fix Released

Bug description:
  After an upgrade to Raring (as of today) from Quantal I'm seeing tons
  of these in /var/log/upstart/ureadahead.log:

  Counted 8 CPUs

  ureadahead:  ��&a��w: Ignored relative path
  ureadahead:  : Ignored relative path
  ureadahead:  �=%���n�T9: Ignored relative path
  ureadahead:  �=%v9T9: Ignored relative path
  ureadahead:  �=%���U�Ek�: Ignored relative path
  ureadahead:  �=%���`�a: Ignored relative path

  
  (the boot was wonderfully fast - not sure if that's because ureadahead was 
working well or if it's because it didn't do anything).

  Dave

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ureadahead 0.100.0-12build1
  ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
  Uname: Linux 3.7.0-4-generic x86_64
  ApportVersion: 2.6.3-0ubuntu2
  Architecture: amd64
  Date: Mon Dec  3 02:06:14 2012
  InstallationDate: Installed on 2012-07-17 (138 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120717)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: Upgraded to raring on 2012-12-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085766/+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 1614215] Re: "md5sums differ" message seems to indicate an install problem

2016-08-19 Thread Dominic Raferd 
Agree with OP on both points, but also note that when I check the two
supposedly different files afterwards they are in fact identical except
for timestamp:

$ sudo diff /var/lib/dpkg/info/apparmor.md5sums 
/var/lib/apparmor/profiles/.apparmor.md5sums; echo $?
0

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

Title:
  "md5sums differ" message seems to indicate an install problem

Status in apparmor package in Ubuntu:
  New

Bug description:
  Upon applying the latest Ubuntu routine-update, I observed these
  messages:

  Setting up apparmor (2.10.95-0ubuntu2.2) ...
  Installing new version of config file 
/etc/apparmor.d/abstractions/dbus-session-strict ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Files /var/lib/dpkg/info/apparmor.md5sums and 
/var/lib/apparmor/profiles/.apparmor.md5sums differ

  "The reason why I am filing a bug report" is the LAST line.  I presume
  that if md5sums do not agree, something was probably done improperly
  in preparing this particular software-update blast.

  However, in-passing, I would also point out line #3, about "start and
  stop actions no longer supported." That seems to me to be something
  (of much less importance, obviously) that might have been overlooked.
  (I've seen =that= message for some time now.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug 17 14:22:55 2016
  InstallationDate: Installed on 2016-03-02 (168 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=/dev/mapper/hostname--vg-root ro
  SourcePackage: apparmor
  Syslog:
   Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is 
enabled
   Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is 
enabled
   Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is 
enabled
   Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is 
enabled
  UpgradeStatus: Upgraded to xenial on 2016-05-11 (98 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614215/+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 1237042] Re: ureadahead source needs "tracing_enabled" changed to "tracing_on" for 12.04.3

2016-01-29 Thread Dominic Raferd 
I also have this problem with Ubuntu 15.10, same output as Nicolas:

$ sudo systemctl status ureadahead
● ureadahead.service - Read required files in advance
   Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sat 2016-01-30 07:07:07 GMT; 15min 
ago
  Process: 233 ExecStart=/sbin/ureadahead (code=exited, status=5)
 Main PID: 233 (code=exited, status=5)

Jan 30 07:07:07 dicer2 ureadahead[233]: ureadahead: Error while tracing: No 
such file or directory
Jan 30 07:07:07 dicer2 ureadahead[233]: Counted 2 CPUs
Jan 30 07:08:19 dicer2 systemd[1]: Stopped Read required files in advance.

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

Title:
  ureadahead source needs "tracing_enabled" changed to "tracing_on" for
  12.04.3

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of Ubuntu 12.04.3 (64-bit), ureadahead was always
  exiting with status code 5.

  When manually run as:  sudo /sbin/ureadahead --force-trace --debug
  The output is:
  Counted 4 CPUs
  trace: Missing uselib tracing: No such file or directory
  ureadahead: Error while tracing: No such file or directory

  The uselib tracing notice is not important.  The "error while tracing" notice 
lead me to compare ureadahead sources between 12.04.3 and 13.04.  Note that 
ureadahead in 13.04 works.  I noticed this difference on lines 195 and 232:
if (set_value (dfd, "tracing_enabled",
  vs:
if (set_value (dfd, "tracing_on",

  This change is mentioned in the changelog as:

  ureadahead (0.100.0-13) raring; urgency=low
* src/trace.c: tracing_enabled is deprecated and gone, switch to tracing_on
  (LP: #1085766).
   -- Andy Whitcroft   Fri, 11 Jan 2013 12:05:17 +

  I suspect that this issue occurs in 12.04.3 because it is now using
  the newer raring kernel 3.8.0-31.  Previous flavors of 12.04 such as
  12.04.2 do not seem to exhibit this ureadahead issue, probably because
  the kernel is older 3.5.xx.

  As a proof-of-concept test, I hex edited the 12.04.3 /sbin/ureadahead
  to change "tracing_enabled" to "tracing_on".  Upon reboot, now
  ureadahead works, generates the /var/lib/ureadahead/pack file, and it
  does not report status code 5.

  Another workaround is to use the ureadahead binary from 13.04, but the
  updated /lib/x86_64-linux-gnu/libext2fs.so.2.4 is also required from
  13.04.

  
  $ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  $ apt-cache policy ureadahead
  ureadahead:
Installed: 0.100.0-12
Candidate: 0.100.0-12
Version table:
   *** 0.100.0-12 0
  500 http://mirror.peer1.net/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1237042/+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 613273] Re: run-init: nuking initramfs contents: directory not empty

2015-10-31 Thread Dominic Raferd 
I have been having this problem (intermittently) with Ubuntu Server
15.04 and now with 15.10 on my Intel NUC5CPYH for the last 3 months
(since I bought it in fact). It only seems to happen when rebooting
(never from a cold boot), and it doesn't always happen. I've attached an
image of the console output. As my machine is normally headless it is
particularly frustrating!

I use LVM but not for the root/system partition, only for /home. My
system/root is at /dev/sda1 and formatted with ext4.

I am using latest kernels downloaded from Ubuntu's
http://kernel.ubuntu.com/~kernel-ppa/mainline/ (currently 4.2.5) - but
as discussed here it doesn't seem to be a kernel issue.

** Attachment added: "Image of the console output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/613273/+attachment/4509728/+files/IMG_20151017_072019871.jpg

-- 
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/613273

Title:
  run-init: nuking initramfs contents: directory not empty

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Lucid:
  Invalid
Status in linux source package in Lucid:
  Invalid
Status in udev source package in Lucid:
  Fix Released
Status in initramfs-tools source package in Maverick:
  Invalid
Status in linux source package in Maverick:
  Invalid
Status in udev source package in Maverick:
  Invalid
Status in initramfs-tools source package in Natty:
  Invalid
Status in linux source package in Natty:
  Invalid
Status in udev source package in Natty:
  Invalid

Bug description:
  In testing alpha-3 build 20100813.2, I found the following kernel oops:
  [0.473264] Kernel panic - not syncing: Attempted to kill init!^M
  [0.473277] Pid: 1, comm: run-init Not tainted 2.6.35-14-virtual 
#19-Ubuntu^M
  [0.473284] Call Trace:^M
  [0.473294]  [] panic+0x90/0x111^M
  [0.473303]  [] ? 
__raw_callee_save_xen_irq_enable+0x11/0x26^M
  [0.473312]  [] forget_original_parent+0x33d/0x350^M
  [0.473318]  [] ? put_files_struct+0xc4/0xf0^M
  [0.473325]  [] exit_notify+0x1b/0x190^M
  [0.473330]  [] do_exit+0x1c5/0x3f0^M
  [0.473336]  [] ? 
__raw_callee_save_xen_irq_disable+0x11/0x1e^M
  [0.473343]  [] sys_exit+0x17/0x20^M
  [0.473349]  [] system_call_fastpath+0x16/0x1b^M

  This happened only once in my testing so far today (dozens of boots).
  I'm attaching the console log of failed instance.  The instance that reported 
this bug is same ami/region different instance.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-image-2.6.35-14-virtual 2.6.35-14.19
  Regression: Yes
  Reproducible: No
  ProcVersionSignature: User Name 2.6.35-14.19-virtual 2.6.35
  Uname: Linux 2.6.35-14-virtual x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   12.900041] eth0: no IPv6 routers present
  Date: Wed Aug  4 01:19:11 2010
  Ec2AMI: ami-09c3bc5b
  Ec2AMIManifest: 
ubuntu-images-testing-ap-southeast-1/ubuntu-maverick-daily-amd64-server-20100803.2.manifest.xml
  Ec2AvailabilityZone: ap-southeast-1b
  Ec2InstanceType: m1.large
  Ec2Kernel: aki-11d5aa43
  Ec2Ramdisk: unavailable
  Frequency: Once a week.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcCmdLine: root=LABEL=uec-rootfs ro
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcModules: acpiphp 18752 0 - Live 0xa000
  SourcePackage: linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/613273/+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 1130611] Re: Upstart never closes /var/log/upstart/mysql.log

2015-03-07 Thread Dominic Raferd 
oops, looks like I spoke too soon. The report from dmesg mentioned in my
previous comment has gone away on reboot. I believe the cause may have
been a fault in my /etc/rc.local file, which may not have been
completing. This is fixed now.

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

Title:
  Upstart never closes /var/log/upstart/mysql.log

Status in upstart package in Ubuntu:
  New

Bug description:
  I ran init u after noticing a lingering FD to a log file that lsof
  showed as (deleted). However because the file handle is never
  closed, and the log files get logrotate'd it keeps happening, like so:

  init  1 root   11w   REG  252,0 3532  394558
  /var/log/upstart/mysql.log.1 (deleted)

  It's possible this might be fixed by a version update, as I noticed
  there were closed bugs relating to leaked file descriptors?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1130611/+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 1130611] Re: Upstart never closes /var/log/upstart/mysql.log

2015-03-05 Thread Dominic Raferd 
I confirm this problem in ubuntu 14.04:
$ sudo lsof|grep deleted|grep -Ev /(dev|tmp|run)
init  1 root   10w  REG  252,4   778
 131190 /var/log/upstart/mysql.log.1 (deleted)

An effect (and how I noticed it) is that when I take LVM snapshot of the 
underlying volume I get warning messages in dmesg:
$ dmesg -T
...
[Fri Mar  6 06:02:19 2015] bio: create slab bio-1 at 1
[Fri Mar  6 06:02:19 2015] EXT4-fs (dm-6): 1 orphan inode deleted
[Fri Mar  6 06:02:19 2015] EXT4-fs (dm-6): recovery complete
...

So the orphan inode in the snapshot (i.e. dm-6) gets deleted but it
remains in the underlying volume.

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

Title:
  Upstart never closes /var/log/upstart/mysql.log

Status in upstart package in Ubuntu:
  New

Bug description:
  I ran init u after noticing a lingering FD to a log file that lsof
  showed as (deleted). However because the file handle is never
  closed, and the log files get logrotate'd it keeps happening, like so:

  init  1 root   11w   REG  252,0 3532  394558
  /var/log/upstart/mysql.log.1 (deleted)

  It's possible this might be fixed by a version update, as I noticed
  there were closed bugs relating to leaked file descriptors?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1130611/+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