[Bug 1905166] Re: systemd-shutdown cannot detach DM
> for those affected, does this happen every boot/shutdown? Yes, I'm getting the following messages on Hirsute at the end of every shut down (or reboot): [ OK ] Reached target Reboot. [ timestamp] XFS: attr2 mount option is deprecated. [ timestamp] sd-umoun[2337]: Failed to unmount /oldroot: Device or resource busy [ timestamp] sd-umoun[2337]: Failed to unmount /oldroot/sys: Device or resource busy [ timestamp] shutdown[1]: Could not detach DM /dev/dm-1: Device or resource busy [ timestamp] shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy [ timestamp] shutdown[1]: Failed to finalize file systems, DM devices, ignoring. > is this a 'standard' installation, using the standard iso? Yes, this was installed using a nightly hirsute-live-server-amd64.iso, with disk encryption enabled during installation. > what do you have mounted? what's the output of 'mount' and the output of 'lsblk'? # mount ... /dev/mapper/ubuntu--vg-ubuntu--lv on / type xfs (rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/nvme0n1p2 on /boot type ext4 (rw,relatime) /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) ... Full mount output at https://gist.githubusercontent.com/joliss/c13e728ee039a2440e98f7ba6dd7ecd8/raw/25678bdaa17707a41b81b61c0fc648e01968ca90/mount # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 99.2M 1 loop /snap/core/10908 loop1 7:10 25.9M 1 loop /snap/heroku/4037 loop2 7:20 72M 1 loop /snap/lxd/19766 loop3 7:30 55.5M 1 loop /snap/core18/1988 loop4 7:40 32.3M 1 loop /snap/snapd/11107 loop5 7:50 32.3M 1 loop /snap/snapd/11402 loop6 7:60 68.7M 1 loop /snap/lxd/19823 nvme0n1 259:00 1.8T 0 disk ├─nvme0n1p1 259:10 512M 0 part /boot/efi ├─nvme0n1p2 259:201G 0 part /boot └─nvme0n1p3 259:30 1.8T 0 part └─dm_crypt-0 253:00 1.8T 0 crypt └─ubuntu--vg-ubuntu--lv 253:10 1.8T 0 lvm / -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905166 Title: systemd-shutdown cannot detach DM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888280] [NEW] dctrl-tools should be dependency of debian-goodies
Public bug reported: I think dctrl-tools should be a dependency of debian-goodies, not just a recommended package. $ sudo apt-get install --no-install-recommends debian-goodies Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: konqueror libgnome2-bin Recommended packages: dctrl-tools elfutils libipc-system-simple-perl libfile-which-perl popularity-contest The following NEW packages will be installed: debian-goodies 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 69.6 kB of archives. After this operation, 222 kB of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 debian-goodies all 0.84 [69.6 kB] Fetched 69.6 kB in 0s (1,131 kB/s) Selecting previously unselected package debian-goodies. (Reading database ... 138758 files and directories currently installed.) Preparing to unpack .../debian-goodies_0.84_all.deb ... Unpacking debian-goodies (0.84) ... Setting up debian-goodies (0.84) ... Processing triggers for man-db (2.9.1-1) ... $ dpigs /usr/bin/dpigs: 91: grep-status: not found grep-status is part of dctrl-tools, and when I install dctrl-tools, dpigs works fine. I'm using Ubuntu 20.04. ** Affects: debian-goodies (Ubuntu) Importance: Undecided Status: New ** Description changed: I think dctrl-tools should be a dependency of debian-goodies, not just a recommended package. $ sudo apt-get install --no-install-recommends debian-goodies Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: - konqueror libgnome2-bin + konqueror libgnome2-bin Recommended packages: - dctrl-tools elfutils libipc-system-simple-perl libfile-which-perl popularity-contest + dctrl-tools elfutils libipc-system-simple-perl libfile-which-perl popularity-contest The following NEW packages will be installed: - debian-goodies + debian-goodies 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 69.6 kB of archives. After this operation, 222 kB of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 debian-goodies all 0.84 [69.6 kB] Fetched 69.6 kB in 0s (1,131 kB/s) Selecting previously unselected package debian-goodies. (Reading database ... 138758 files and directories currently installed.) Preparing to unpack .../debian-goodies_0.84_all.deb ... Unpacking debian-goodies (0.84) ... Setting up debian-goodies (0.84) ... Processing triggers for man-db (2.9.1-1) ... $ dpigs /usr/bin/dpigs: 91: grep-status: not found grep-status is part of dctrl-tools, and when I install dctrl-tools, dpigs works fine. + + I'm using Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888280 Title: dctrl-tools should be dependency of debian-goodies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-goodies/+bug/1888280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610721] [NEW] Ctrl+S in terminal causes shutdown/reboot (init) to hang
Public bug reported: 1. Boot an Ubuntu 16.04 machine that doesn't have an X server installed 2. When you get the terminal log-in prompt (on tty1), instead of logging in, press Ctrl+S to stop terminal flow 3. Connect to the machine via SSH 4. Run "sudo init 0" via SSH The init command hangs. Only when you press Ctrl+Q in the terminal does the machine shut down. This behavior is confusing when you accidentally hit Ctrl+S. It also means that you cannot shut down or reboot the machine remotely if someone has pressed Ctrl+S locally. Pressing the power button instead of running "init 0" produces the behavior as well - nothing happens until you press Ctrl+Q. I'm attaching a screen recording to illustrate the problem. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "shutdown hangs with Ctrl-S.mp4" https://bugs.launchpad.net/bugs/1610721/+attachment/4716095/+files/shutdown%20hangs%20with%20Ctrl-S.mp4 ** Description changed: 1. Boot an Ubuntu 16.04 machine that doesn't have an X server installed 2. When you get the terminal log-in prompt (on tty1), instead of logging in, press Ctrl+S to stop terminal flow 3. Connect to the machine via SSH 4. Run "sudo init 0" via SSH The init command hangs. Only when you press Ctrl+Q in the terminal does the machine shut down. This behavior is confusing when you accidentally hit Ctrl+S. It also means that you cannot shut down or reboot the machine remotely if someone has pressed Ctrl+S locally. + Pressing the power button instead of running "init 0" produces the + behavior as well - nothing happens until you press Ctrl+Q. + I'm attaching a screen recording to illustrate the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610721 Title: Ctrl+S in terminal causes shutdown/reboot (init) to hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1610721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573974] Re: makepasswd hangs
The "hanging" behavior seems to be happening because makepasswd reads from /dev/random. A workaround is to mash keys or move the mouse to generate entropy. This only works if you have physical access to the machine. It doesn't work if you're logged in via SSH. The man page for makepasswd advertises that makepasswd uses /dev/urandom. I believe/assume that this was the behavior in 14.04, since I've only had this problem in 16.04. I'd like to suggest changing it back to /dev/urandom. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573974 Title: makepasswd hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makepasswd/+bug/1573974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581163] [NEW] "man fuse" refers to non-existent "fuse" group
Public bug reported: `man fuse` from package fuse 2.9.4-1ubuntu3 amd64 on Ubuntu Server Xenial (16.04) says: SECURITY The fusermount program is installed set-user-gid to fuse. This is done to allow users from fuse group to mount their own filesystem implementations. I think this used to be true in 14.04, but it's no longer true in 16.04. `/bin/fusermount` is now set-uid root, and there is no `fuse` group: $ ls -l /bin/fusermount -rwsr-xr-x 1 root root 30800 Mar 11 15:43 /bin/fusermount $ grep fuse /etc/group $ I'm not sure if there *should* be a `fuse` group, or if the man page needs to be updated. ** Affects: fuse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581163 Title: "man fuse" refers to non-existent "fuse" group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1581163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 812423] Re: mysql upstart job hangs if database directory not mounted
*** This bug is a duplicate of bug 711635 *** https://bugs.launchpad.net/bugs/711635 On Sun, Feb 19, 2012 at 01:03, Clint Byrum cl...@fewbar.com wrote: Its possible that the upstart job is respawning over and over rather than just failing, which it should. I think it might be helpful if you could provide us with /var/log/syslog during the time where you seee lines this hang. Usually the job will execute, and the run the post- start which will wait 30 seconds for mysql to be started, and then fail. Just wanted to quickly confirm that that's in fact the case (don't know why I didn't notice earlier). Feb 19 23:29:58 ip-10-204-242-176 kernel: [6052896.375740] type=1400 audit(1329694198.815:32): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25129 comm=apparmor_parser Feb 19 23:29:58 ip-10-204-242-176 kernel: [6052896.514222] init: mysql main process (25133) terminated with status 1 Feb 19 23:29:58 ip-10-204-242-176 kernel: [6052896.514275] init: mysql main process ended, respawning Feb 19 23:30:29 ip-10-204-242-176 kernel: [6052926.587238] init: mysql post-start process (25134) terminated with status 1 Feb 19 23:30:29 ip-10-204-242-176 kernel: [6052926.599364] type=1400 audit(1329694229.040:33): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25318 comm=apparmor_parser Feb 19 23:30:29 ip-10-204-242-176 kernel: [6052926.626133] init: mysql main process (25322) terminated with status 1 Feb 19 23:30:29 ip-10-204-242-176 kernel: [6052926.626184] init: mysql main process ended, respawning Feb 19 23:30:59 ip-10-204-242-176 kernel: [6052956.768819] init: mysql post-start process (25323) terminated with status 1 Feb 19 23:30:59 ip-10-204-242-176 kernel: [6052956.776625] type=1400 audit(1329694259.221:34): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25410 comm=apparmor_parser Feb 19 23:30:59 ip-10-204-242-176 kernel: [6052956.802865] init: mysql main process (25414) terminated with status 1 Feb 19 23:30:59 ip-10-204-242-176 kernel: [6052956.802914] init: mysql main process ended, respawning Feb 19 23:31:29 ip-10-204-242-176 kernel: [6052986.950767] init: mysql post-start process (25415) terminated with status 1 Feb 19 23:31:29 ip-10-204-242-176 kernel: [6052986.962872] type=1400 audit(1329694289.406:35): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25480 comm=apparmor_parser Feb 19 23:31:29 ip-10-204-242-176 kernel: [6052986.988213] init: mysql main process (25484) terminated with status 1 Feb 19 23:31:29 ip-10-204-242-176 kernel: [6052986.988263] init: mysql main process ended, respawning Feb 19 23:31:59 ip-10-204-242-176 kernel: [6053017.133727] init: mysql post-start process (25485) terminated with status 1 Feb 19 23:31:59 ip-10-204-242-176 kernel: [6053017.141439] type=1400 audit(1329694319.583:36): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25559 comm=apparmor_parser Feb 19 23:31:59 ip-10-204-242-176 kernel: [6053017.167105] init: mysql main process (25563) terminated with status 1 Feb 19 23:31:59 ip-10-204-242-176 kernel: [6053017.167152] init: mysql main process ended, respawning etc. Thanks for following up! Jo -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 812423] Re: mysql upstart job hangs if database directory not mounted
*** This bug is a duplicate of bug 711635 *** https://bugs.launchpad.net/bugs/711635 On Sun, Feb 19, 2012 at 01:03, Clint Byrum cl...@fewbar.com wrote: Its possible that the upstart job is respawning over and over rather than just failing, which it should. I think it might be helpful if you could provide us with /var/log/syslog during the time where you seee lines this hang. Usually the job will execute, and the run the post- start which will wait 30 seconds for mysql to be started, and then fail. Just wanted to quickly confirm that that's in fact the case (don't know why I didn't notice earlier). Feb 19 23:29:58 ip-10-204-242-176 kernel: [6052896.375740] type=1400 audit(1329694198.815:32): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25129 comm=apparmor_parser Feb 19 23:29:58 ip-10-204-242-176 kernel: [6052896.514222] init: mysql main process (25133) terminated with status 1 Feb 19 23:29:58 ip-10-204-242-176 kernel: [6052896.514275] init: mysql main process ended, respawning Feb 19 23:30:29 ip-10-204-242-176 kernel: [6052926.587238] init: mysql post-start process (25134) terminated with status 1 Feb 19 23:30:29 ip-10-204-242-176 kernel: [6052926.599364] type=1400 audit(1329694229.040:33): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25318 comm=apparmor_parser Feb 19 23:30:29 ip-10-204-242-176 kernel: [6052926.626133] init: mysql main process (25322) terminated with status 1 Feb 19 23:30:29 ip-10-204-242-176 kernel: [6052926.626184] init: mysql main process ended, respawning Feb 19 23:30:59 ip-10-204-242-176 kernel: [6052956.768819] init: mysql post-start process (25323) terminated with status 1 Feb 19 23:30:59 ip-10-204-242-176 kernel: [6052956.776625] type=1400 audit(1329694259.221:34): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25410 comm=apparmor_parser Feb 19 23:30:59 ip-10-204-242-176 kernel: [6052956.802865] init: mysql main process (25414) terminated with status 1 Feb 19 23:30:59 ip-10-204-242-176 kernel: [6052956.802914] init: mysql main process ended, respawning Feb 19 23:31:29 ip-10-204-242-176 kernel: [6052986.950767] init: mysql post-start process (25415) terminated with status 1 Feb 19 23:31:29 ip-10-204-242-176 kernel: [6052986.962872] type=1400 audit(1329694289.406:35): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25480 comm=apparmor_parser Feb 19 23:31:29 ip-10-204-242-176 kernel: [6052986.988213] init: mysql main process (25484) terminated with status 1 Feb 19 23:31:29 ip-10-204-242-176 kernel: [6052986.988263] init: mysql main process ended, respawning Feb 19 23:31:59 ip-10-204-242-176 kernel: [6053017.133727] init: mysql post-start process (25485) terminated with status 1 Feb 19 23:31:59 ip-10-204-242-176 kernel: [6053017.141439] type=1400 audit(1329694319.583:36): apparmor=STATUS operation=profile_replace name=/usr/sbin/mysqld pid=25559 comm=apparmor_parser Feb 19 23:31:59 ip-10-204-242-176 kernel: [6053017.167105] init: mysql main process (25563) terminated with status 1 Feb 19 23:31:59 ip-10-204-242-176 kernel: [6053017.167152] init: mysql main process ended, respawning etc. Thanks for following up! Jo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924873] Re: Many unnecessary rt_sigprocmask syscalls
Forgot to mention: It doesn't happen without the -i option. And I'm using Oneiric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924873 Title: Many unnecessary rt_sigprocmask syscalls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/924873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924873] [NEW] Many unnecessary rt_sigprocmask syscalls
Public bug reported:
Package: Bash 4.2-0ubuntu4
bash --version: GNU bash, version 4.2.10(1)-release (x86_64-pc-linux-gnu)
The command
strace -o strace bash -i -c :
reports many rt_sigprocmask calls:
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
open(/home/ubuntu/.bash_history, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0600, st_size=1922, ...}) = 0
brk(0x1f68000) = 0x1f68000
read(3, echo bar\n#1328099029\necho 'f\n#13..., 1922) = 1922
close(3)= 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
stat(/home/ubuntu/.set-locale, 0x7fffe1ffcb10) = -1 ENOENT (No such file or
directory)
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
...
This likely has a performance impact. See e.g.
http://timetobleed.com/fix-a-bug-in-rubys-configurein-and-get-a-30
-performance-boost/ which describes (presumably) the same problem with
Ruby.
This might be fixable by changing the build options.
** Affects: bash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924873
Title:
Many unnecessary rt_sigprocmask syscalls
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/924873/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 812423] Re: mysql upstart job hangs if database directory not mounted
Mounted as /dev/xvdf on /mnt/data_joliss type ext3 (rw,noatime,errors=remount-ro) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 812423] Re: mysql upstart job hangs if database directory not mounted
Sure. $ cat /etc/fstab LABEL=cloudimg-rootfs /ext4 defaults0 0 LABEL=data_joliss /mnt/data_joliss auto noatime,errors=remount-ro 0 2 /var/swapfile none swap defaults 0 0 Still happens on Oneiric with mysql-server 5.1.58-1ubuntu1. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 812423] Re: mysql upstart job hangs if database directory not mounted
Sure. $ cat /etc/fstab LABEL=cloudimg-rootfs /ext4 defaults0 0 LABEL=data_joliss /mnt/data_joliss auto noatime,errors=remount-ro 0 2 /var/swapfile none swap defaults 0 0 Still happens on Oneiric with mysql-server 5.1.58-1ubuntu1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 812423] Re: mysql upstart job hangs if database directory not mounted
Mounted as /dev/xvdf on /mnt/data_joliss type ext3 (rw,noatime,errors=remount-ro) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 812423] [NEW] mysql upstart job hangs if database directory not mounted
Public bug reported: [I think this might be a bug. Copied from http://serverfault.com/questions/291003/mysql-upstart-job-hangs-if- database-directory-not-mounted ] I have mysqld pointed to an external volume: $ cat /etc/mysql/conf.d/data_joliss.cnf [mysqld] datadir=/mnt/data_joliss/mysql This is working fine in general. But sometimes the volume is not mounted, for whatever reason. In those cases, mysqld fails like it should: # mysqld 110716 14:17:42 [Warning] Can't create test file /mnt/data_joliss/mysql/opinionated-programmer.lower-test 110716 14:17:42 [Warning] Can't create test file /mnt/data_joliss/mysql/opinionated-programmer.lower-test mysqld: Can't change dir to '/mnt/data_joliss/mysql/' (Errcode: 2) 110716 14:17:42 [ERROR] Aborting 110716 14:17:42 [Note] mysqld: Shutdown complete However, the upstart job on Ubuntu 11.04 (`start mysql` or `service start mysql`) simply waits (hangs) indefinitely without outputting anything. The strace isn't telling me anything, but if anybody cares to take a look: strace -fv start mysql = https://gist.github.com/1086397 I would like the `mysql` upstart job to just report an error and terminate rather than hanging. How do I do this? (Background: I have an EC2 instance with an extra EBS volume to store permanent data. If the EBS volume is not available at boot time, the system hangs waiting for mysql, and I cannot even SSH into it to fix the problem -- so now my instance has become completely unusable. I would like it to just continue booting, even without a MySQL server.) Ubuntu 11.04 on EC2, ami-06ad526f mysql-server-core-5.1: Installed: 5.1.54-1ubuntu4 Candidate: 5.1.54-1ubuntu4 Version table: *** 5.1.54-1ubuntu4 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: upstart 0.9.7-1 ProcVersionSignature: Ubuntu 2.6.38-8.42-virtual 2.6.38.2 Uname: Linux 2.6.38-8-virtual i686 Architecture: i386 Date: Mon Jul 18 17:13:55 2011 Ec2AMI: ami-06ad526f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: t1.micro Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable ExecutablePath: /sbin/initctl ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LC_COLLATE=POSIX LANG=en_US.UTF-8 LC_TIME=POSIX SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.1 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 natty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 812423] Re: mysql upstart job hangs if database directory not mounted
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 812423] Re: mysql upstart job hangs if database directory not mounted
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 812423] [NEW] mysql upstart job hangs if database directory not mounted
Public bug reported: [I think this might be a bug. Copied from http://serverfault.com/questions/291003/mysql-upstart-job-hangs-if- database-directory-not-mounted ] I have mysqld pointed to an external volume: $ cat /etc/mysql/conf.d/data_joliss.cnf [mysqld] datadir=/mnt/data_joliss/mysql This is working fine in general. But sometimes the volume is not mounted, for whatever reason. In those cases, mysqld fails like it should: # mysqld 110716 14:17:42 [Warning] Can't create test file /mnt/data_joliss/mysql/opinionated-programmer.lower-test 110716 14:17:42 [Warning] Can't create test file /mnt/data_joliss/mysql/opinionated-programmer.lower-test mysqld: Can't change dir to '/mnt/data_joliss/mysql/' (Errcode: 2) 110716 14:17:42 [ERROR] Aborting 110716 14:17:42 [Note] mysqld: Shutdown complete However, the upstart job on Ubuntu 11.04 (`start mysql` or `service start mysql`) simply waits (hangs) indefinitely without outputting anything. The strace isn't telling me anything, but if anybody cares to take a look: strace -fv start mysql = https://gist.github.com/1086397 I would like the `mysql` upstart job to just report an error and terminate rather than hanging. How do I do this? (Background: I have an EC2 instance with an extra EBS volume to store permanent data. If the EBS volume is not available at boot time, the system hangs waiting for mysql, and I cannot even SSH into it to fix the problem -- so now my instance has become completely unusable. I would like it to just continue booting, even without a MySQL server.) Ubuntu 11.04 on EC2, ami-06ad526f mysql-server-core-5.1: Installed: 5.1.54-1ubuntu4 Candidate: 5.1.54-1ubuntu4 Version table: *** 5.1.54-1ubuntu4 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: upstart 0.9.7-1 ProcVersionSignature: Ubuntu 2.6.38-8.42-virtual 2.6.38.2 Uname: Linux 2.6.38-8-virtual i686 Architecture: i386 Date: Mon Jul 18 17:13:55 2011 Ec2AMI: ami-06ad526f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: t1.micro Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable ExecutablePath: /sbin/initctl ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LC_COLLATE=POSIX LANG=en_US.UTF-8 LC_TIME=POSIX SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.1 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812423 Title: mysql upstart job hangs if database directory not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/812423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 785670] Re: logrotate cronjob /etc/cron.daily/logrotate throws errors when it is executed for the first time because it expects status file
This is actually a bit of a hassle for cloud users who regularly deploy servers on top of fresh vanilla Ubuntu images, because it means that every time you deploy, you get an error notice emailed from cron. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/785670 Title: logrotate cronjob /etc/cron.daily/logrotate throws errors when it is executed for the first time because it expects status file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/785670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
