[Bug 582443] Re: Syslog socket missing from chroot.
I've discovered that a chroot can be escaped by chrooting to any file. I'm interested on how this plays on attempting to protect /dev/log? From what I can gather is that chroots should not be used as a security measure(as they are in this case), but only as a device to run multiple distributions at the same time. Am I wrong? -- 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/582443 Title: Syslog socket missing from chroot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/582443/+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 908614] [NEW] /run: Too many levels of symbolic links
Public bug reported: root@ubuntu:~# ls /run ls: cannot access /run: Too many levels of symbolic links root@ubuntu:~# ls -alrt /run /var/run lrwxrwxrwx 1 root root 8 Dec 24 14:58 /run - /var/run lrwxrwxrwx 1 root root 4 Dec 25 14:42 /var/run - /run ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dnsmasq-base 2.59-4 ProcVersionSignature: Ubuntu 3.2.0-6.12-generic-pae 3.2.0-rc6 Uname: Linux 3.2.0-6-generic-pae i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 CasperVersion: 1.296 Date: Sun Dec 25 20:54:20 2011 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20111220) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: debian-base-files Importance: Undecided Status: New ** Affects: sysvinit Importance: Undecided Status: New ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/908614 Title: /run: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/debian-base-files/+bug/908614/+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 908614] Re: /run: Too many levels of symbolic links
** Also affects: debian-base-files Importance: Undecided Status: New ** Also affects: sysvinit Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/908614 Title: /run: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/debian-base-files/+bug/908614/+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 908614] Re: /run: Too many levels of symbolic links
root@ubuntu:~# dpkg -S /var/run base-files, initscripts: /run base-files, dnsmasq-base: /var/run -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/908614 Title: /run: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/debian-base-files/+bug/908614/+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 908614] Re: /run: Too many levels of symbolic links
I made both into a directory with no symlinks. For the time being /var/run is a link to /run, should be ../run if any thing. I believe that if /var/run is needed prior to /var being mounted that /tmp should be used. After var is mounted /tmp can hold symlinks into /var/run. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/908614 Title: /run: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/debian-base-files/+bug/908614/+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 908614] Re: /run: Too many levels of symbolic links
This was all done using apt-get. After do-release-upgrade had failed to find an upgrade path, I ran `find /etc/apt -type f -exec sed -i -e 's/lucid/precise/g'` and then I manually went through and downgraded a few packages to help satisfy dependencies. I understand that /run is likely needed in cases where /var is on another file system from root. However I believe that /tmp/shm/run would be a better candidate as / should be mostly read-only. /var/run should have symbolic links pointed to /tmp/shm/run for use after boot and applications that run during boot should be configured to make use of /tmp/shm/run and then create these links after /var is mounted for it's brethren. This seams like a cleaner solution then for parts of /var to be mapped to a filesystem for which they don't belong. As for how things got this way, it has to be because one package created one of these symbolic links and another package created the other. I would look for a package that creates a /run - var/run link. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/908614 Title: /run: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/debian-base-files/+bug/908614/+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 908614] Re: /run: Too many levels of symbolic links
Vary well. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/908614 Title: /run: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/debian-base-files/+bug/908614/+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 1030520] [NEW] logwatch: Makes use of $^X, broken under overlayfs.
Public bug reported: Bug number 1030519 tracks this issue in perl and Bug number 1007089 is the root cause. In Ubuntu perl is located in /usr/bin/perl, so using $^X isn't necessarily needed. Also you should investigate using eval() or other methods to get a sub-perl instance. One solution may be to copy stdin to another handle and then close stdin and open STDIN $(cat ... |). A pipepare can be used to get an actual system filedescriptor. Then the perl code can be run in an eval, instead of a system. I would be willing to help with development. /etc/cron.daily/00logwatch: sh: 1: /bin/perl: not found sh: 1: /bin/perl: not found system 'cat '/var/log/mail.log' '/var/log/mail.log.1' | /bin/perl /usr/share/logwatch/scripts/shared/expandrepeats ''| /bin/perl /usr/share/logwatch/scripts/shared/applystddate ''/tmp/logwatch.BMbdlb_J/maillog' failed: 32512 at /usr/sbin/logwatch line 871. run-parts: /etc/cron.daily/00logwatch exited with return code 2 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: logwatch 7.4.0+svn20111221rev79-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.31-lowlatency-pae 3.2.14 Uname: Linux 3.2.0-23-lowlatency-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Sun Jul 29 09:12:38 2012 PackageArchitecture: all SourcePackage: logwatch UpgradeStatus: Upgraded to precise on 2012-01-03 (208 days ago) ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1030520 Title: logwatch: Makes use of $^X, broken under overlayfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1030520/+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 1030520] Re: logwatch: Makes use of $^X, broken under overlayfs.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1030520 Title: logwatch: Makes use of $^X, broken under overlayfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1030520/+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 1030519] Re: /proc/self/exe is not necessarily correct on overlayfs
That's only some what reasonable. One would expect a perl API to work always(but it doesn't)... However the same is not true of kernel APIs, the opposite is vary much the case. You don't call open() and then turn right around and operate on the new file handle, no you don't even do this usually in perl. The same could be true of files in proc and actually using stuff in proc is a vary bad API to begin with and perl should migrate to using another API for this. With open you test the return code and based on that you 'trust' the file handle is iether usable or not usable. The same is true of proc, you need to at the vary least see if this is a file that's executable, a simple test. I believe that every application using proc should be modified to not depend on the API, as it CAN be changed at any time. It's not supposed to be used by applications, that's why /sys was written. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1030519 Title: /proc/self/exe is not necessarily correct on overlayfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1030519/+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 908614] Re: /run: Too many levels of symbolic links
There are plenty of other important bugs to work on: https://bugs.launchpad.net/~cheako Not everyone who posted on this bug saying it effected them marked it as having effected them, too sad. The count should be at least 3, but one wonders how many noobs read the fix and didn't know to at least trip the this effects me. Cheers. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/908614 Title: /run: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/debian-base-files/+bug/908614/+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 780820] [NEW] kadmin: IPv6 support binds IPv4 socket leading to EAFNOSUPPORT.
Public bug reported:
Package: krb5-user
Version: 1.8.3+dfsg-4
Severity: important
File: /usr/bin/kadmin
Here is a small bit of strace output:
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 4
bind(4, {sa_family=AF_INET, sin_port=htons(775),
sin_addr=inet_addr(0.0.0.0)}, 16) = 0
connect(4, {sa_family=AF_INET6, sin6_port=htons(749),
inet_pton(AF_INET6, ::, sin6_addr), sin6_flowinfo=0,
sin6_scope_id=0}, 16) = -1 EAFNOSUPPORT (Address family not supported
by protocol)
Obviously the bind needs to be made IPv6 aware. I hope this is self
explanitory, the initial connection to the admin server falis as a
result and kadmin exits. Also the addres in the connect seams wrong.
This is run on localhost and the '-s 127.0.0.1' option is ignored.
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (900, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.35.4-rscloud (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages krb5-user depends on:
ii krb5-config 2.2 Configuration files for Kerberos V
ii libc6 2.11.2-10Embedded GNU C Library: Shared lib
ii libcomerr2 1.41.12-2common error description library
ii libgssapi-krb5-21.8.3+dfsg-4 MIT Kerberos runtime libraries - k
ii libgssrpc4 1.8.3+dfsg-4 MIT Kerberos runtime libraries - G
ii libk5crypto31.8.3+dfsg-4 MIT Kerberos runtime libraries - C
ii libkadm5clnt-mit7 1.8.3+dfsg-4 MIT Kerberos runtime libraries - A
ii libkeyutils11.4-1Linux Key Management Utilities (li
ii libkrb5-3 1.8.3+dfsg-4 MIT Kerberos runtime libraries
ii libkrb5support0 1.8.3+dfsg-4 MIT Kerberos runtime libraries - S
ii libss2 1.41.12-2command-line interface parsing lib
krb5-user recommends no packages.
krb5-user suggests no packages.
-- no debconf information
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: krb5-user 1.8.1+dfsg-5ubuntu0.7 [modified: usr/bin/kadmin
usr/bin/kdestroy usr/bin/kinit usr/bin/klist usr/bin/kpasswd usr/bin/ksu
usr/bin/ktutil usr/bin/kvno]
Uname: Linux 2.6.39-020639rc1-generic i686
Architecture: i386
Date: Tue May 10 19:27:38 2011
ProcEnviron:
LANGUAGE=C:en
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
SourcePackage: krb5
** Affects: krb5 (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 maverick
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/780820
Title:
kadmin: IPv6 support binds IPv4 socket leading to EAFNOSUPPORT.
--
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 780820] Re: kadmin: IPv6 support binds IPv4 socket leading to EAFNOSUPPORT.
** Bug watch added: Debian Bug tracker #624710 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624710 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/780820 Title: kadmin: IPv6 support binds IPv4 socket leading to EAFNOSUPPORT. -- 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 780820] Re: kadmin: IPv6 support binds IPv4 socket leading to EAFNOSUPPORT.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624710 Version 1.9 adds IPv6 support for kadmind and kadmin. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/780820 Title: kadmin: IPv6 support binds IPv4 socket leading to EAFNOSUPPORT. -- 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 591423] [NEW] qemu -drive boot=on flag causes boot to hang.
Public bug reported: Binary package hint: qemu-kvm I'm working on getting a UI to start qemu. In debugging I am working exclusively on the command line. I'm able to reproduce and correct this bug from the command line. The UI is libvirt. The testing I did was to remove part of the command each part at a time and add it back in until I discovered the one option that caused the problem. This command boot's just fine. /usr/bin/qemu -snapshot -M pc-0.12 -no-kvm -m 1024 -smp 1 -localtime -boot c -drive file=/dev/sda,if=ide,index=0 -serial none -parallel none -usb -usbdevice tablet -vga cirrus These commands do not: /usr/bin/qemu -snapshot -M pc-0.12 -no-kvm -m 1024 -smp 1 -localtime -boot c -drive file=/dev/sda,if=ide,index=0,boot=on -serial none -parallel none -usb -usbdevice tablet -vga cirrus /usr/bin/qemu -snapshot -M pc-0.12 -no-kvm -m 1024 -smp 1 -localtime -drive file=/dev/sda,if=ide,index=0,boot=on -serial none -parallel none -usb -usbdevice tablet -vga cirrus /usr/bin/qemu -snapshot -boot c -drive file=/dev/sda,boot=on /usr/bin/qemu -snapshot -drive file=/dev/sda,boot=on /usr/bin/qemu -boot c -drive file=/dev/sda,boot=on /usr/bin/qemu -drive file=/dev/sda,boot=on The boot hangs presumably when the BIOS passes control to the MBR or during the MBR load, ect, ect, ect. In other words the BIOS parts seam to work, except it never boots anything. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: qemu 0.12.3+noroms-0ubuntu9 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic-pae i686 Architecture: i386 Date: Tue Jun 8 14:17:31 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427.1) KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD MachineType: Dell Inc. OptiPlex GX620 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic-pae root=/dev/mapper/Chrome-root ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: qemu-kvm dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0HH807 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0HH807:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/49966398/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/49966399/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/49966400/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/49966401/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/49966402/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/49966403/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/49966404/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/49966405/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/49966406/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/49966407/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/49966408/UdevLog.txt -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
I wrote a little script that should have solved my problems, however
libvirt has other ideas.
http://pastebin.com/HgwtQ3iL
#!/bin/bash
out_args=( )
while (( $# ))
do if [[ $1 = -drive ]]
then out_args+=( $1 $($2 sed \
-e s/,boot=on//g \
-e s/boot=on,//g \
-e s/boot=on//g \
) )
shift 2
else out_args+=( $1 )
shift
fi
done
exec ${0}-original ${out_ar...@]}
http://pastebin.com/7SKxnJGV
Some strace output, the exec on line 15 fails with a permission problem.
--
qemu -drive boot=on flag causes boot to hang.
https://bugs.launchpad.net/bugs/591423
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
(04:12:14 PM) cheako: operation=exec pid=24359 parent=1 profile=libvirt-02e3d7e8-79e5-6dc3-2954-d43fe1130cdf requested_mask=x:: denied_mask=x:: fsuid=0 ouid=0 name=/usr/bin/qemu-original (04:12:25 PM) cheako: operation=mknod pid=24361 parent=24360 profile=libvirt-02e3d7e8-79e5-6dc3-2954-d43fe1130cdf requested_mask=c:: denied_mask=c:: fsuid=0 ouid=0 name=/tmp/sh-thd-1276031548 (04:12:39 PM) cheako: operation=open pid=24359 parent=1 profile=libvirt-02e3d7e8-79e5-6dc3-2954-d43fe1130cdf requested_mask=r:: denied_mask=r:: fsuid=0 ouid=0 name=/usr/bin/qemu-original -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
This bug is about qemu's option, if it's not a bug in qemu then this is a bug in libvirt for using this option. As for the selinux and apparmor issues these are bugs in my solution and have nothing to do with the bug being reported, but instead are related to one of it's /incomplete/ solutions. -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
That was simple add the following to the apparmor file: /usr/bin/qemu-original rmix, /bin/sed rmix, /tmp/sh-thd-* rw, Also the dmsg statements that apparmor makes are not recognized by the SELinux ppl, they should all indicate from whence they hail. -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
The BUG here in qemu is that it starts, but then hangs! ** Bug watch added: SourceForge.net Tracker #1977971 http://sourceforge.net/support/tracker.php?aid=1977971 ** Also affects: libvirt via http://sourceforge.net/support/tracker.php?aid=1977971 Importance: Unknown Status: Unknown -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
After reading the posted email thread, I've come to the conclusion that the -boot argument is missdocumented/missleading. In actuality it's c parameter is more like the boot from first or selected hard disk and d would be boot from first or selected cdrom. I think it would be best to remove this parameter, perhaps replacing it with a parameter to force a particular behavior(like the option to what format a block device is in). The boot sequence should attempt a cdrom boot, since this would fail quickly I'd imagine if the image was not an iso. Then booting the device like a hard disk or crash trying. -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
I made a change to my script.
#!/bin/bash
out_args=( )
while (( $# ))
do if [[ $1 = -drive ]]
then out_args+=( $1 $($2 sed \
-e s/,boot=on//g \
-e s/boot=on,//g \
-e s/boot=on//g \
) )
shift 2
else out_args+=( $1 )
shift
fi
done
exec -a $0 ${0}-original ${out_ar...@]}
--
qemu -drive boot=on flag causes boot to hang.
https://bugs.launchpad.net/bugs/591423
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
Now I see the true bug here. I setup WindowsXP to use the virtio block driver and now as predicted I can't boot from it. After removing the wrapper script it seams that GRUB hangs during boot. Could there be a problem with the int13h driver? -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
After doing some digging I've made the assumption that this is a missing feature of the BIOS(seabios). I've build the latest code from GIT and am getting the same result. Using KVM this is working, can that be used to correct QEMU? -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
Fails to boot is described above, however a recap here would be nice. The boot process hangs(idle for ever) during the BIOS and/or MBR stage of the boot. -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
ilia, What SF project, a link would be nice. The current link is kinda fun it links to that number locally. -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
I have this working at home under KVM, it's the software emulator that this is broken on. http://sourceforge.net/tracker/index.php?func=detailaid=1977971group_id=180599atid=893831 This is also something to keep in mind, with or w/o -boot c it's the same. -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 591423] Re: qemu -drive boot=on flag causes boot to hang.
Just to be clear the bug was reported while using GRUB, not the Windows XP loader. Grub did not start, so the config entry for XP shouldn't be an issue. Though I can see where the BIOS would need to have the drive attached(and fully detected) if it's going to boot to it. -- qemu -drive boot=on flag causes boot to hang. https://bugs.launchpad.net/bugs/591423 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 582443] Re: Syslog socket missing from chroot.
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48675413/Dependencies.txt -- Syslog socket missing from chroot. https://bugs.launchpad.net/bugs/582443 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 582443] [NEW] Syslog socket missing from chroot.
Public bug reported: Hello, sshd attempts to open /var/run/sshd/dev/log in order to log events, but this file did not exist. I ran mkdir /var/run/sshd/dev and added $AddUnixListenSocket /var/run/sshd/dev/log to /etc/rsyslog.d/75-ssh.conf. That should fix things up. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openssh-server 1:5.3p1-3ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic-pae i686 Architecture: i386 Date: Tue May 18 13:44:27 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SSHDConfig: Error: command ['gksu', '-D', 'Apport', '--', '/usr/sbin/sshd', '-T'] failed with exit code 1: GNOME_SUDO_PASSSorry, try again. sudo: 3 incorrect password attempts SourcePackage: openssh ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- Syslog socket missing from chroot. https://bugs.launchpad.net/bugs/582443 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 582443] Re: Syslog socket missing from chroot.
My strace revealed that sshd was indeed attempting to open this socket and failing. I can see where if a user can inject into sshd that injecting into rsyslog would be trial for this person. I don't fully understand the ramifications of extra code lying around to do things like: 1. Test for the existence of this socket. a. Act on config option enabling/disabling this. 2. Test for the existence of a /var/log folder or /var/log/auth.log file. a. Act on config option enabling/disabling this. Though the current code might not have anything wrong with it, AFAIK. If by default this file should not exist then there should be a config option set to disable it's use, with instructions on enabling syslog for testing. Perhaps this should be something only done in testing and should be disable by default. If one wanted a filtering proxy to be vary strict about the messages passed through this socket, then perhaps the solution is for sshd to provide such a proxy. This way messages could be limited to only the messages sshd itself would generate. -- Syslog socket missing from chroot. https://bugs.launchpad.net/bugs/582443 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 1282099] [NEW] package snmpd 5.7.2~dfsg-8ubuntu1 [modified: usr/sbin/snmpd usr/sbin/snmptrapd] failed to install/upgrade: subprocess installed post-installation script returned error exit status
Public bug reported: Upgrading to saucy. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: snmpd 5.7.2~dfsg-8ubuntu1 [modified: usr/sbin/snmpd usr/sbin/snmptrapd] ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 AptOrdering: myspell-cs-cz: Remove snmpd: Configure Architecture: i386 Date: Mon Feb 17 22:50:22 2014 DpkgTerminalLog: Removing myspell-cs-cz ... Setting up snmpd (5.7.2~dfsg-8ubuntu1) ... rmdir: failed to remove '/usr/share/doc/snmpd': Directory not empty dpkg: error processing snmpd (--configure): subprocess installed post-installation script returned error exit status 1 DuplicateSignature: package:snmpd:5.7.2~dfsg-8ubuntu1 [modified: usr/sbin/snmpd usr/sbin/snmptrapd]:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 MarkForUpload: True SNMPVersion: NET-SNMP version: 5.7.2 Web: http://www.net-snmp.org/ Email: net-snmp-cod...@lists.sourceforge.net SourcePackage: net-snmp SyslogSnmpd: SyslogSnmptrapd: Title: package snmpd 5.7.2~dfsg-8ubuntu1 [modified: usr/sbin/snmpd usr/sbin/snmptrapd] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to saucy on 2014-02-18 (1 days ago) ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1282099 Title: package snmpd 5.7.2~dfsg-8ubuntu1 [modified: usr/sbin/snmpd usr/sbin/snmptrapd] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1282099/+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
