[Bug 1435428] Re: disconnecting qemu-nbd leaves device node behind
Martin, After a lot more testing, both synthetic and normally using my day-to- day tools, I haven't been able to reproduce the disconnect problem, so I'm writing that off as a fluke or as some silly error on my part. As far as I can tell, the original qemu-nbd mounting bug has been solidly fixed. Thanks for all your hard work! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1435428 Title: disconnecting qemu-nbd leaves device node behind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428/+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 1435428] Re: vivid: systemd breaks qemu-nbd mounting
@didrocks - yup, it's working now! Thank you! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1435428 Title: vivid: systemd breaks qemu-nbd mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428/+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 1435428] Re: vivid: systemd breaks qemu-nbd mounting
Hmm, and one more thing: qemu-nbd --disconnect (at least sometimes) doesn't seem to be working when booting with systemd: $ ls /dev/nbd0* /dev/nbd0 /dev/nbd0p1 /dev/nbd0p2 /dev/nbd0p5 $ sudo qemu-nbd --disconnect /dev/nbd0 /dev/nbd0 disconnected $ echo $? 0 $ ls /dev/nbd0* /dev/nbd0 /dev/nbd0p1 /dev/nbd0p2 /dev/nbd0p5 After running qemu-nbd --disconnect, the exported nbd0p1, nbd0p2, nbd0p5 partitions should disappear (that's what happens when booting with Upstart). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1435428 Title: vivid: systemd breaks qemu-nbd mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428/+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 1435428] Re: vivid: systemd breaks qemu-nbd mounting
Hmmm, there may still be an issue, as I didn't encounter this yesterday when doing my task multiple times after booting with Upstart. I'm mounting these qcow2 disk images in order to export a tarball of the filesystem. First three tarballs exported swimmingly, but the fourth time it seemed to hang, so I checked dmesg and saw this: [ 6009.696624] INFO: task jbd2/nbd0p1-8:26664 blocked for more than 120 seconds. [ 6009.696625] Tainted: P OE 3.19.0-10-generic #10-Ubuntu [ 6009.696625] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 6009.696625] jbd2/nbd0p1-8 D 8800c59d7b28 0 26664 2 0x [ 6009.696627] 8800c59d7b28 8803beab3110 00014200 8800c59d7fd8 [ 6009.696628] 00014200 88040c6da740 8803beab3110 8803f0914d40 [ 6009.696629] 88041ed94af8 88041efc89a0 0002 817c44f0 [ 6009.696630] Call Trace: [ 6009.696631] [817c44f0] ? bit_wait_timeout+0x70/0x70 [ 6009.696632] [817c3c20] io_schedule+0xa0/0x130 [ 6009.696633] [817c451b] bit_wait_io+0x2b/0x50 [ 6009.696634] [817c40c7] __wait_on_bit+0x67/0x90 [ 6009.696636] [81380f40] ? generic_make_request+0xc0/0x110 [ 6009.696637] [817c44f0] ? bit_wait_timeout+0x70/0x70 [ 6009.696638] [817c4162] out_of_line_wait_on_bit+0x72/0x80 [ 6009.696639] [810b6240] ? autoremove_wake_function+0x40/0x40 [ 6009.696640] [81227d46] __wait_on_buffer+0x36/0x40 [ 6009.696641] [812c8df0] jbd2_write_superblock+0xa0/0x190 [ 6009.696643] [812cb373] jbd2_journal_update_sb_log_tail+0x33/0x80 [ 6009.696645] [812c39fa] jbd2_journal_commit_transaction+0x57a/0x1820 [ 6009.696646] [810ab9c0] ? dequeue_entity+0x140/0x680 [ 6009.696648] [8109ea5d] ? ttwu_do_wakeup+0x1d/0xe0 [ 6009.696649] [810ac2e6] ? dequeue_task_fair+0x3e6/0x6a0 [ 6009.696650] [810ad111] ? put_prev_entity+0x31/0x430 [ 6009.696652] [810b04ab] ? pick_next_task_fair+0x1ab/0x8a0 [ 6009.696653] [810ad53f] ? put_prev_task_fair+0x2f/0x50 [ 6009.696654] [810dc35b] ? lock_timer_base.isra.36+0x2b/0x50 [ 6009.696655] [810dd44f] ? try_to_del_timer_sync+0x4f/0x70 [ 6009.696656] [812c85bb] kjournald2+0xbb/0x250 [ 6009.696657] [810b6200] ? wait_woken+0x90/0x90 [ 6009.696658] [812c8500] ? commit_timeout+0x10/0x10 [ 6009.696660] [81094679] kthread+0xc9/0xe0 [ 6009.696661] [810945b0] ? kthread_create_on_node+0x1c0/0x1c0 [ 6009.696662] [817c8198] ret_from_fork+0x58/0x90 [ 6009.696663] [810945b0] ? kthread_create_on_node+0x1c0/0x1c0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1435428 Title: vivid: systemd breaks qemu-nbd mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428/+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 1435428] Re: vivid: systemd breaks qemu-nbd mounting
Hmm, maybe something else was going on. In an isolated test script, I haven't reproduced the disconnect problem again yet. I attached the script I'm using in case anyone else what's to give it ago. ** Attachment added: qemu-nbd-test.py https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428/+attachment/4356000/+files/qemu-nbd-test.py -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1435428 Title: vivid: systemd breaks qemu-nbd mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428/+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 1435428] Re: vivid: systemd breaks qemu-nbd mounting
** Summary changed: - vivid: mounting with qemu-nbd fails + vivid: systemd breaks qemu-nbd mounting ** Description changed: On Trusty and Utopic, this works: $ sudo modprobe nbd $ sudo qemu-nbd --snapshot -c /dev/nbd0 my.qcow2 $ sudo mount /dev/nbd0p1 /mnt $ sudo umount /mnt But on Vivid, even though the mount command exits with 0, something goes awry and the mount point gets unmounted immediately. No files will actually be available, and umount will exit with 32 (umount: /mnt: not mounted). + + However, if I reboot using the Upstart grub entry (in Advanced options + for Ubuntu), this works on Vivid. + + I'm at a loss for how exactly systemd is interacting with qemu-nbd, but + somehow it is. Possibly useful bits from dmesg: [ 172.010766] kvm [2750]: vcpu0 disabled perfctr wrmsr: 0xc1 data 0x [ 208.379278] nbd0: p1 p2 p5 [ 208.395989] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) [ 532.601057] block nbd0: NBD_DISCONNECT [ 532.601150] block nbd0: Receive control failed (result -32) [ 532.601177] block nbd0: queue cleared [ 671.892460] nbd0: p1 p2 p5 [ 697.575545] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) [ 775.331402] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 793.632005] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qemu-utils 1:2.2+dfsg-5expubuntu8 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 10:45:24 2015 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S 0 0 486 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 3105 1618 0.0 qemu-nbd --snapshot -c /dev/nbd0 -t /home/tribble/vivid-server-amd64.qcow2 MachineType: Notebook P750ZM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=db0af986-9e96-441e-a383-e5b3ba2e837b ro quiet splash SourcePackage: qemu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.09aRSCC dmi.board.asset.tag: Tag 12345 dmi.board.name: P750ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.09aRSCC:bd02/25/2015:svnNotebook:pnP750ZM:pvrNotApplicable:rvnNotebook:rnP750ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: P750ZM dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Tags added: systemd-boot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1435428 Title: vivid: systemd breaks qemu-nbd mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428/+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 1435428] [NEW] vivid: mounting with qemu-nbd fails
Public bug reported: On Trusty and Utopic, this works: $ sudo modprobe nbd $ sudo qemu-nbd --snapshot -c /dev/nbd0 my.qcow2 $ sudo mount /dev/nbd0p1 /mnt $ sudo umount /mnt But on Vivid, even though the mount command exists with 0, something goes awry and the mount point gets unmounted immediately. No files will actually be available, and umount will exit with 32 (umount: /mnt: not mounted). Possibly useful bits from dmesg: [ 172.010766] kvm [2750]: vcpu0 disabled perfctr wrmsr: 0xc1 data 0x [ 208.379278] nbd0: p1 p2 p5 [ 208.395989] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) [ 532.601057] block nbd0: NBD_DISCONNECT [ 532.601150] block nbd0: Receive control failed (result -32) [ 532.601177] block nbd0: queue cleared [ 671.892460] nbd0: p1 p2 p5 [ 697.575545] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) [ 775.331402] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 793.632005] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qemu-utils 1:2.2+dfsg-5expubuntu8 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 10:45:24 2015 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S 0 0 486 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 3105 1618 0.0 qemu-nbd --snapshot -c /dev/nbd0 -t /home/tribble/vivid-server-amd64.qcow2 MachineType: Notebook P750ZM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=db0af986-9e96-441e-a383-e5b3ba2e837b ro quiet splash SourcePackage: qemu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.09aRSCC dmi.board.asset.tag: Tag 12345 dmi.board.name: P750ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.09aRSCC:bd02/25/2015:svnNotebook:pnP750ZM:pvrNotApplicable:rvnNotebook:rnP750ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: P750ZM dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Description changed: On Trusty and Utopic, this works: $ sudo modprobe nbd $ sudo qemu-nbd --snapshot -c /dev/nbd0 my.qcow2 $ sudo mount /dev/nbd0p1 /mnt $ sudo umount /mnt But on Vivid, even though the mount command exists with 0, something goes awry and the mount point gets unmounted immediately. No files will actually be available, and umount will exit with 32 (umount: /mnt: not mounted). - Possibly use bits from dmesg: + Possibly useful bits from dmesg: [ 172.010766] kvm [2750]: vcpu0 disabled perfctr wrmsr: 0xc1 data 0x [ 208.379278] nbd0: p1 p2 p5 [ 208.395989] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) [ 532.601057] block nbd0: NBD_DISCONNECT [ 532.601150] block nbd0: Receive control failed (result -32) [ 532.601177] block nbd0: queue cleared [ 671.892460] nbd0: p1 p2 p5 [ 697.575545] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) [ 775.331402] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 793.632005] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qemu-utils 1:2.2+dfsg-5expubuntu8 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 10:45:24 2015 KvmCmdLine: - COMMAND STAT EUID RUID PID PPID %CPU COMMAND - kvm-irqfd-clean S 0 0 486 2 0.0 [kvm-irqfd-clean] - qemu-nbdSsl 0 0 3105 1618 0.0 qemu-nbd --snapshot -c /dev/nbd0 -t /home/tribble/vivid-server-amd64.qcow2 + COMMAND STAT EUID RUID PID PPID %CPU COMMAND + kvm-irqfd-clean S 0 0 486 2 0.0 [kvm-irqfd-clean] + qemu-nbdSsl 0 0 3105 1618 0.0 qemu-nbd --snapshot -c /dev/nbd0 -t /home/tribble/vivid-server-amd64.qcow2 MachineType: Notebook P750ZM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=db0af986-9e96-441e-a383-e5b3ba2e837b ro quiet splash SourcePackage: qemu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh
[Bug 1435428] Re: vivid: mounting with qemu-nbd fails
** Description changed: On Trusty and Utopic, this works: $ sudo modprobe nbd $ sudo qemu-nbd --snapshot -c /dev/nbd0 my.qcow2 $ sudo mount /dev/nbd0p1 /mnt $ sudo umount /mnt - But on Vivid, even though the mount command exists with 0, something - goes awry and the mount point gets unmounted immediately. No files will + But on Vivid, even though the mount command exits with 0, something goes + awry and the mount point gets unmounted immediately. No files will actually be available, and umount will exit with 32 (umount: /mnt: not mounted). Possibly useful bits from dmesg: [ 172.010766] kvm [2750]: vcpu0 disabled perfctr wrmsr: 0xc1 data 0x [ 208.379278] nbd0: p1 p2 p5 [ 208.395989] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) [ 532.601057] block nbd0: NBD_DISCONNECT [ 532.601150] block nbd0: Receive control failed (result -32) [ 532.601177] block nbd0: queue cleared [ 671.892460] nbd0: p1 p2 p5 [ 697.575545] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) [ 775.331402] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 793.632005] EXT4-fs (nbd0p1): mounted filesystem with ordered data mode. Opts: (null) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qemu-utils 1:2.2+dfsg-5expubuntu8 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 10:45:24 2015 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S 0 0 486 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 3105 1618 0.0 qemu-nbd --snapshot -c /dev/nbd0 -t /home/tribble/vivid-server-amd64.qcow2 MachineType: Notebook P750ZM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=db0af986-9e96-441e-a383-e5b3ba2e837b ro quiet splash SourcePackage: qemu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.09aRSCC dmi.board.asset.tag: Tag 12345 dmi.board.name: P750ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.09aRSCC:bd02/25/2015:svnNotebook:pnP750ZM:pvrNotApplicable:rvnNotebook:rnP750ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: P750ZM dmi.product.version: Not Applicable dmi.sys.vendor: Notebook -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1435428 Title: vivid: mounting with qemu-nbd fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428/+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 1429938] Re: stopping ssh.service closes existing ssh connections
Hmm, now I'm thinking this has nothing to do with openssh-server. I think the problem is actually that when I run this over SSH: # shutdown -h now My ssh client exists with status 255... whereas running the same thing prior to the flip-over to systemd would exit with status 0. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: stopping ssh.service closes existing ssh connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+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 1429938] Re: stopping ssh.service closes existing ssh connections
So interestingly, this isn't happening when I just type these commands into an SSH session. But if you create a script like this in say /tmp/test.sh: #!/bin/bash apt-get -y purge openssh-server ssh-import-id apt-get -y autoremove shutdown -h now And then execute this through an ssh call like this: $ ssh root@whatever /tmp/test.sh I get the disconnection problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: stopping ssh.service closes existing ssh connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+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 1429938] Re: stopping ssh.service closes existing ssh connections
Also, on Vivid there will be this error: Connection to localhost closed by remote host. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: stopping ssh.service closes existing ssh connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+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 1429938] Re: stopping ssh.service closes existing ssh connections
Same problem when running `reboot`, which I'd say is even more important for automation. Port 2204 is forwarding to a qemu VM running Utopic, port 2207 is running Vivid: jderose@jgd-kudp1:~$ ssh root@localhost -p 2204 reboot jderose@jgd-kudp1:~$ echo $? 0 jderose@jgd-kudp1:~$ ssh root@localhost -p 2207 reboot Connection to localhost closed by remote host. jderose@jgd-kudp1:~$ echo $? 255 jderose@jgd-kudp1:~$ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: stopping ssh.service closes existing ssh connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+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 1429938] Re: stopping ssh.service closes existing ssh connections
Okay, here's a simple way to reproduce: $ ssh root@whatever shutdown -h now $ echo $? On Vivid, the exist status from the ssh client will be 255. On Trusty and Utopic it will be 0. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: stopping ssh.service closes existing ssh connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+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 1429938] [NEW] systemd changes behavior of apt-get remove openssh-server
Public bug reported: On Trusty and Utopic, when you run `apt-get remove openssh-server` over an SSH connection, your existing SSH connection remains open, so it's possible to run additional commands afterward. However, on Vivid now that the switch to systemd has been made, `apt- get remove openssh-server` closes the existing SSH connection immediately, causing your SSH client to exit with a non-zero status. I have a hunch there's a lot of automation tooling out there that relies on the old behavior. For what it's worth, this change breaks the internal image mastering tools that System76 uses. Prior to exporting an image tarball, I spin up a golden VM with qemu, rysnc a script to it, and then execute this script over SSH. The important step is that I need to remove openssh-server prior to shutting down the VM, so these scripts always end with something like this: apt-get -y purge openssh-server ssh-import-id apt-get -y autoremove shutdown -h now As far as I can tell, this behavior change will likewise be a problem when running `do-release-upgrade` on a remote server over SSH. Or more generally, anytime you run apt-get upgrade/dist-upgrade via SSH, it seems this would be a problem whenever the openssh-server package happens to be updated. ** Affects: openssh (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: systemd-boot vivid ** Tags added: systemd vivid ** Tags removed: systemd ** Tags added: systemd-boot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: systemd changes behavior of apt-get remove openssh-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+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 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
Being able to run a script like this over SSH: apt-get -y remove openssh-server shutdown -h now Can be extremely useful in automation tooling, but the switch to systemd breaks this: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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 1429938] Re: systemd changes behavior of apt-get remove openssh-server
Also, just to clarify, this is definitely a change (or in my mind regression) introduced by systemd. Yesterday, the System76 image master tool worked fine and dandy with an up-to-date Vivid VM, as it has throughout the rest of the previous Vivid dev cycle. Today things broke. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1429938 Title: systemd changes behavior of apt-get remove openssh-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
This also affects the `gnome-keyring` package. The System76 imaging system (Tribble) uses a tar-based approach similar to the MAAS fast-path installer, and we've had to add a work-around for /usr/bin/gnome- keyring-daemon on our desktop images: $ getcap /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon = cap_ipc_lock+ep I reckon there are other imaging systems out there likewise affected by this. I strongly feel that the correct fix is to fix tar so its --xattrs option works as expected. But in the meantime, it might be good to switch back to using suid on /usr/bin/gnome-keyring-daemon. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
Stéphane, Gotcha, thanks for the feedback! So am I correct in thinking that the --xattrs option is currently broken in tar on 14.04? If so, is there any chance this could be fixed in an SRU? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
Clint, Ah, thanks for bringing up --xattrs-include=*, I didn't notice this option! I agree this is really a bug/misfeature in tar... if I use --xattrs both when creating and unpacking a tarball, I expect it to just work. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 623144] Re: chkutmp assert failure: *** stack smashing detected ***: ./chkutmp terminated
+1 Intell 2.6.32-33-generic #72-Ubuntu SMP Ubuntu 10.04.4 LTS /etc/cron.daily/chkrootkit: *** stack smashing detected ***: ./chkutmp terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x50)[0x1f2390] /lib/tls/i686/cmov/libc.so.6(+0xe233a)[0x1f233a] ./chkutmp[0x8048bb5] [0x30322d62] === Memory map: 0011-00263000 r-xp 08:12 197003 /lib/tls/i686/cmov/libc-2.11.1.so 00263000-00264000 ---p 00153000 08:12 197003 /lib/tls/i686/cmov/libc-2.11.1.so 00264000-00266000 r--p 00153000 08:12 197003 /lib/tls/i686/cmov/libc-2.11.1.so 00266000-00267000 rw-p 00155000 08:12 197003 /lib/tls/i686/cmov/libc-2.11.1.so 00267000-0026a000 rw-p 00:00 0 004e7000-00502000 r-xp 08:12 164255 /lib/ld-2.11.1.so 00502000-00503000 r--p 0001a000 08:12 164255 /lib/ld-2.11.1.so 00503000-00504000 rw-p 0001b000 08:12 164255 /lib/ld-2.11.1.so 007f5000-007f6000 r-xp 00:00 0 [vdso] 00acd000-00aea000 r-xp 08:12 164240 /lib/libgcc_s.so.1 00aea000-00aeb000 r--p 0001c000 08:12 164240 /lib/libgcc_s.so.1 00aeb000-00aec000 rw-p 0001d000 08:12 164240 /lib/libgcc_s.so.1 08048000-0804a000 r-xp 08:12 2479228/usr/lib/chkrootkit/chkutmp 0804a000-0804b000 r--p 1000 08:12 2479228/usr/lib/chkrootkit/chkutmp 0804b000-0804c000 rw-p 2000 08:12 2479228/usr/lib/chkrootkit/chkutmp 09ea8000-09ec9000 rw-p 00:00 0 [heap] b787-b7871000 rw-p 00:00 0 b788e000-b789 rw-p 00:00 0 bfa06000-bfb7c000 rw-p 00:00 0 [stack] Aborted -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/623144 Title: chkutmp assert failure: *** stack smashing detected ***: ./chkutmp terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/623144/+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 563973] Re: vsftpd fails to start on boot when using pasv_addr_resolve
Problem still exists vsftpd: version 2.2.2 May 16 00:15:01 vps3532 init: vsftpd main process ended, respawning May 16 00:15:01 vps3532 init: vsftpd main process (11238) terminated with status 1 May 16 00:15:01 vps3532 init: vsftpd main process ended, respawning May 16 00:15:01 vps3532 init: vsftpd main process (11241) terminated with status 1 May 16 00:15:01 vps3532 init: vsftpd main process ended, respawning May 16 00:15:01 vps3532 init: vsftpd main process (11244) terminated with status 1 May 16 00:15:01 vps3532 init: vsftpd main process ended, respawning May 16 00:15:01 vps3532 init: vsftpd main process (11247) terminated with status 1 May 16 00:15:01 vps3532 init: vsftpd main process ended, respawning May 16 00:15:01 vps3532 init: vsftpd main process (11250) terminated with status 1 May 16 00:15:01 vps3532 init: vsftpd respawning too fast, stopped ** Changed in: vsftpd (Ubuntu) Status: Fix Released = Incomplete -- vsftpd fails to start on boot when using pasv_addr_resolve https://bugs.launchpad.net/bugs/563973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. -- 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 394365] [NEW] package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: le sous-processus post-installation script a retourn? une erreur de sortie d'?tat 1
Public bug reported: boot process fail ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 9.04 ErrorMessage: le sous-processus post-installation script a retourné une erreur de sortie d'état 1 NonfreeKernelModules: nvidia Package: mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 SourcePackage: mysql-dfsg-5.0 Title: package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: le sous-processus post-installation script a retourné une erreur de sortie d'état 1 Uname: Linux 2.6.28-13-generic i686 ** Affects: mysql-dfsg-5.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: le sous-processus post-installation script a retourn? une erreur de sortie d'?tat 1 https://bugs.launchpad.net/bugs/394365 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 394365] Re: package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: le sous-processus post-installation script a retourn? une erreur de sortie d'?tat 1
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/28601273/Dependencies.txt ** Attachment added: DpkgTerminalLog.gz http://launchpadlibrarian.net/28601274/DpkgTerminalLog.gz -- package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: le sous-processus post-installation script a retourn? une erreur de sortie d'?tat 1 https://bugs.launchpad.net/bugs/394365 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 282298] Re: [SRU] Intrepid: No Access to NAS (samba=2.2.x) shares any more
http://launchpadlibrarian.net/19559308/libsmbclient_3.2.3-1ubuntu3_i386.deb worked for me too, thanks. -- [SRU] Intrepid: No Access to NAS (samba=2.2.x) shares any more https://bugs.launchpad.net/bugs/282298 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 185729] Re: nautilus is unable to copy folders from samba
Sorry guys - I have to me too on this one. I have a similar setup using a D-Link NAS. Gutsy was working fine, Hardy is no good. What I did notice was in ~/.gvfs the volume exists and I can copy etc from there ok. it is only through the normal file management that I get the same result as mentioned here. That is what makes me suspect gvfs. Good luck. -- nautilus is unable to copy folders from samba https://bugs.launchpad.net/bugs/185729 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 222234] Re: Hardy Heron: samba has quit unexpectedly
Hello Yes I've got an entry which says, when I pass the mouse over it, create, modify and erase samba shares. see screenshot below In French: créer, modifier et supprimer les partages samba ** Attachment added: samba entry in admin menu http://launchpadlibrarian.net/13956351/samba%20entry%20in%20admin%20menu.png -- Hardy Heron: samba has quit unexpectedly https://bugs.launchpad.net/bugs/34 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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
