[Bug 1732411] Re: On upgrade, daemon-reexec should only be issued if safe
A fix [1] in LXC was pushed recently and actually allows systemd daemon- reexec without the cap sys_admin in a container. We tested that it totally solved the issue for us. Would it possible to move this bug report to the LXC project? And to ask for a backport of such fix to Xenial LXC? Thanks! [1] https://github.com/lxc/lxc/commit/af949cc1938ff3a4e06148867a64d7715ce89a50 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732411 Title: On upgrade, daemon-reexec should only be issued if safe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1732411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732411] Re: On upgrade, daemon-reexec should only be issued if safe
>From our analysis, we indeed agree with the fact that it has nothing to do >with LXC (hence the report in the systemd tracker). We believe that only the package is faulty here and should not attempt to blindly reexec systemd on upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732411 Title: On upgrade, daemon-reexec should only be issued if safe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1732411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732411] [NEW] On upgrade, daemon-reexec should only be issued if safe
Public bug reported: Dear all, Following up the bug report #1713674, when executing systemd in a hardened LXC context, it might not be suitable to reexec systemd daemon, that would not be able to perform. For instance, in our LXC, we drop several capabilities, including sys_admin and we set /sys to read-only (in which, systemd will find its cgroups). This means, systemd cannot be reexecuted, it will fail to restart and will freeze (properly) at restart making the LXC container in frozen state (still working, but no new services startable, no interaction with systemd possible anymore). When upgrading systemd the debian package, as postinst, will always attempt to reexecute systemd, possibly breaking every other upgrade where a daemon restart is made in postinst, and leaving the system in a degraded state. It would likely be appropriate the check whether the reexecute can work will before performing it: checking capabilities, sys mount point perms, etc. If not applicable, not performing a reexucte and possibly print a message to the user. Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21. Cheers ** Affects: systemd (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/1732411 Title: On upgrade, daemon-reexec should only be issued if safe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713674] [NEW] Starting Xenial lxc without cap_sysadmin fails
Public bug reported: Dear all, When trying to start an LXC container with Xenial on both host and container, if sys_admin capability is dropped (lxc.cap.drop = sys_admin in the config file), the container fails to start, because systemd fails to mount the cgroup filesystem in the container. The workaround is to manually mount the cgroup filesystem before starting the container (using the lxc.mount.entry in the config file), but, LXC performs the mount too early, before being in the container cgroup namespace, that means what's mounted matches host cgroup namespace, not container namespace. The bug was already reported upstream[1][2], but didn't make it to Ubuntu yet, AFAIK. A fix was merged in master[3], would it be possible to have it in Ubuntu Xenial? So far, we manually patch Ubuntu LXC packages with that patch and observed no régressions. Thanks! Cheers, P. Schweitzer [1]: https://github.com/lxc/lxc/pull/1597 [2]: https://github.com/lxc/lxc/pull/1606 [3]: https://github.com/lxc/lxc/commit/c1cecfdd050818865653d7941d7bae5d755246ae ** Affects: lxc (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/1713674 Title: Starting Xenial lxc without cap_sysadmin fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1713674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541678] Re: if-post-down.d/vlan and if-pre-up.d/vlan should support predictable NIC names
Dear all, We have also faced such issue while migrating some servers from Ubuntu 14.04.5 to Ubuntu 16.04.3. Are there any plans to get a correct fix so that we can properly plan our migration to Xenial? Meanwhile, we used the workaround provided by Brian Candler - thanks! - which works well. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541678 Title: if-post-down.d/vlan and if-pre-up.d/vlan should support predictable NIC names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1541678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594422] [NEW] Lambdas with variadic template fail to build
Public bug reported: Dear all, All the G++ shipped with Ubuntu 14.04 (including the latest 4.8 package) are suffering a bug from G++ in the C++11 implementation. It is not possible to build code that contains variadic templates with variadic lambda. The bug was fixed upstream. Would it be possible to backport the fix? As an example, you'll find the upstream bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41933 It provides examples about how to reproduce the bug. The output of the compiler is slightly different though, as it is made by G++-4.8. Cheers ** Affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594422 Title: Lambdas with variadic template fail to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1594422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534779] [NEW] Trusty has higher release than Vivid - breaks upgrading
Public bug reported: Dear all, With the upgrade to GCC 4.9 packages that occurred recently on Trusty (upgrading to 4.9.3-0ubuntu4), Vivid now provides an older GCC 4.9 release (4.9.2-10ubuntu13) [1]. The side effect of that thing is that it's not possible to upgrade from Trusty to Vivid any longer, due to the needed 'downgrade' of GCC. Aptitude will output unmet dependencies such as: libasan1 : Depends: gcc-4.9-base (= 4.9.2-10ubuntu13) but 4.9.3-0ubuntu4 is installed. libquadmath0 : Depends: gcc-4.9-base (= 4.9.2-10ubuntu13) but 4.9.3-0ubuntu4 is installed. [1]: http://packages.ubuntu.com/search?keywords=gcc-4.9-base=names=all=all Cheers, ** Affects: gcc-4.9 (Ubuntu) Importance: Undecided Status: New ** Tags: vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534779 Title: Trusty has higher release than Vivid - breaks upgrading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.9/+bug/1534779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524743] Re: Lucid packages is not updated to 4.3.34 as virtualbox
Affected by such bug on Ubuntu 14.04 LTS, which seems to be what the original author reports in spite of what of the title reads. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524743 Title: Lucid packages is not updated to 4.3.34 as virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-guest-additions-iso/+bug/1524743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422307] Re: qemu-nbd corrupts files
Tested 2.0.0+dfsg-2ubuntu1.18. Cannot reproduce the issue. TEST CASE 1: Attempt several times to copy files on a VDI disk, and couldn't trigger any corruption (nor deadlock - no regression). Given my test scenario, previously, I would already have hit the corruption. TEST CASE 2: Tested with test scenario provided in comment #4. Couldn't reproduce, and no regression. TEST CASE 3: Tested with test scenario provided in comment #5. Couldn't reproduce, and no regression. Marking as verification-done -- 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/1422307 Title: qemu-nbd corrupts files To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422307/+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 1422307] Re: qemu-nbd corrupts files
Tested 2.0.0+dfsg-2ubuntu1.18. Cannot reproduce the issue. TEST CASE 1: Attempt several times to copy files on a VDI disk, and couldn't trigger any corruption (nor deadlock - no regression). Given my test scenario, previously, I would already have hit the corruption. TEST CASE 2: Tested with test scenario provided in comment #4. Couldn't reproduce, and no regression. TEST CASE 3: Tested with test scenario provided in comment #5. Couldn't reproduce, and no regression. Marking as verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422307 Title: qemu-nbd corrupts files To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422307] Re: qemu-nbd corrupts files
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1422307 Title: qemu-nbd corrupts files To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422307/+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 1422307] Re: qemu-nbd corrupts files
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422307 Title: qemu-nbd corrupts files To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422307] Re: qemu-nbd corrupts files
Please find attach a proposed debdiff for fixing the issue in Ubuntu Trusty by backporting the fix which is now in Wily. ** Description changed: + [Impact] + A race condition in the VDI block driver of Qemu leads to image (and thus file system) corruption under certain circumstances. + This makes Qemu tools usage for VDI formatted images particularly dangerous (qemu-img, qemu-nbd). + The bug fix introduces locks to prevent such race condition. + + + [Test Case] + A simple test case was provided in comment #5 (https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1422307/comments/5): + + $ ./qemu-img create -f vdi test.vdi 2G + Formatting 'test.vdi', fmt=vdi size=2147483648 static=off + $ ./qemu-img create -f raw test.raw 2G + Formatting 'test.raw', fmt=raw size=2147483648 + $ x86_64-softmmu/qemu-system-x86_64 -enable-kvm -drive if=virtio,file=blkverify:test.raw:test.vdi,format=raw -drive if=virtio,file=data.img,format=raw,format=raw -cdrom ~/tmp/arch.iso -m 512 -boot d + blkverify: read sector_num=810976 nb_sectors=256 contents mismatch in sector 811008 + + Operations in the guest: + $ dd if=/dev/vdb of=/dev/vda + $ dd if=/dev/vda of=/dev/null + + [Regression Potential] + In case of bugs affecting the way locks are used, deadlocks could be a regression, but they would only affect VDI images. + + + Original bug report: Dear all, On Trusty, in certain situations, try to copy files over a qemu-nbd mounted file system leads to write errors (and thus, file corruption). Here is the last example I tried: - virtual disk is a VDI disk - It has only one partition, in FAT Here is my mount process: # modprobe nbd max_part=63 # qemu-nbd -c /dev/nbd0 virtual_disk.vdi # partprobe /dev/nbd0 # mount /dev/nbd0p1 /tmp/mnt/ Partition is properly mounted at that point: /dev/nbd0p1 on /tmp/mnt type vfat (rw) Now, when I copy a file (rather big, ~28MB): # cp file_to_copy /tmp/mnt/ ; sync # md5sum /tmp/mnt/file_to_copy 2efc9f32e4267782b11d63d2f128a363 /tmp/mnt/file_to_copy - # umount /tmp/mnt + # umount /tmp/mnt # mount /dev/nbd0p1 /tmp/mnt/ # md5sum /tmp/mnt/file_to_copy 42b0a3bf73f704d03ce301716d7654de /tmp/mnt/file_to_copy The first hash was obviously the right one. On a previous attempt I did, I spotted thanks to vbindiff that parts of the file were just filed with 0s instead of actual data. It will randomly work after several attempts to write. Version information: # qemu-nbd --version qemu-nbd version 0.0.1 Written by Anthony Liguori. Cheers, ** Patch added: qemu_2.0.0+dfsg-2ubuntu1.17.diff https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1422307/+attachment/4448189/+files/qemu_2.0.0%2Bdfsg-2ubuntu1.17.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422307 Title: qemu-nbd corrupts files To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422307] Re: qemu-nbd corrupts files
Please find attach a proposed debdiff for fixing the issue in Ubuntu Trusty by backporting the fix which is now in Wily. ** Description changed: + [Impact] + A race condition in the VDI block driver of Qemu leads to image (and thus file system) corruption under certain circumstances. + This makes Qemu tools usage for VDI formatted images particularly dangerous (qemu-img, qemu-nbd). + The bug fix introduces locks to prevent such race condition. + + + [Test Case] + A simple test case was provided in comment #5 (https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1422307/comments/5): + + $ ./qemu-img create -f vdi test.vdi 2G + Formatting 'test.vdi', fmt=vdi size=2147483648 static=off + $ ./qemu-img create -f raw test.raw 2G + Formatting 'test.raw', fmt=raw size=2147483648 + $ x86_64-softmmu/qemu-system-x86_64 -enable-kvm -drive if=virtio,file=blkverify:test.raw:test.vdi,format=raw -drive if=virtio,file=data.img,format=raw,format=raw -cdrom ~/tmp/arch.iso -m 512 -boot d + blkverify: read sector_num=810976 nb_sectors=256 contents mismatch in sector 811008 + + Operations in the guest: + $ dd if=/dev/vdb of=/dev/vda + $ dd if=/dev/vda of=/dev/null + + [Regression Potential] + In case of bugs affecting the way locks are used, deadlocks could be a regression, but they would only affect VDI images. + + + Original bug report: Dear all, On Trusty, in certain situations, try to copy files over a qemu-nbd mounted file system leads to write errors (and thus, file corruption). Here is the last example I tried: - virtual disk is a VDI disk - It has only one partition, in FAT Here is my mount process: # modprobe nbd max_part=63 # qemu-nbd -c /dev/nbd0 virtual_disk.vdi # partprobe /dev/nbd0 # mount /dev/nbd0p1 /tmp/mnt/ Partition is properly mounted at that point: /dev/nbd0p1 on /tmp/mnt type vfat (rw) Now, when I copy a file (rather big, ~28MB): # cp file_to_copy /tmp/mnt/ ; sync # md5sum /tmp/mnt/file_to_copy 2efc9f32e4267782b11d63d2f128a363 /tmp/mnt/file_to_copy - # umount /tmp/mnt + # umount /tmp/mnt # mount /dev/nbd0p1 /tmp/mnt/ # md5sum /tmp/mnt/file_to_copy 42b0a3bf73f704d03ce301716d7654de /tmp/mnt/file_to_copy The first hash was obviously the right one. On a previous attempt I did, I spotted thanks to vbindiff that parts of the file were just filed with 0s instead of actual data. It will randomly work after several attempts to write. Version information: # qemu-nbd --version qemu-nbd version 0.0.1 Written by Anthony Liguori. Cheers, ** Patch added: qemu_2.0.0+dfsg-2ubuntu1.17.diff https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1422307/+attachment/4448189/+files/qemu_2.0.0%2Bdfsg-2ubuntu1.17.diff -- 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/1422307 Title: qemu-nbd corrupts files To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1422307/+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 1471836] [NEW] qemu-nbd corrupts files
Public bug reported: A bug exists in Ubuntu 14.04 LTS which leads qemu-nbd to corrupt image files that are mounted. The bug report done for Qemu is here: https://bugs.launchpad.net/qemu/+bug/1422307 They fixed it with: http://git.qemu.org/?p=qemu.git;a=commit;h=f0ab6f109630940146cbaf47d0cd3ddba824 Would it be possible to have a backport of the bugfix? With my best regards, ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471836 Title: qemu-nbd corrupts files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1471836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471836] [NEW] qemu-nbd corrupts files
Public bug reported: A bug exists in Ubuntu 14.04 LTS which leads qemu-nbd to corrupt image files that are mounted. The bug report done for Qemu is here: https://bugs.launchpad.net/qemu/+bug/1422307 They fixed it with: http://git.qemu.org/?p=qemu.git;a=commit;h=f0ab6f109630940146cbaf47d0cd3ddba824 Would it be possible to have a backport of the bugfix? With my best regards, ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream trusty -- 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/1471836 Title: qemu-nbd corrupts files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1471836/+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 1465663] [NEW] libata Samsung SSD 8 series TRIM blacklist
Public bug reported: Dear all, In order to be able to upgrade one of our servers to the latest LTS (14.04), we need that the Samsung SSD 8 series to be blacklisted from the libata for the TRIM command. Due to the bug described here [1], not having the SSD blacklisted would lead to data corruption which we cannot afford. The Samsung SSD was blacklisted with that commit [2]. I checked, it's not present in current Trusty kernel. Could you please backport it? With my best regards, [1]: https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ [2]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ** Description changed: Dear all, In order to be able to upgrade one of our servers to the latest LTS (14.04), we need that the Samsung SSD 8 series to be blacklisted from the libata for the TRIM command. Due to the bug described here [1], not having the SSD blacklisted would lead to data corruption which we cannot afford. - The Samsung SSD was blacklisted with that commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81 + The Samsung SSD was blacklisted with that commit [2]. I checked, it's not present in current Trusty kernel. Could you please backport it? With my best regards, - [1]: https://blog.algolia.com/when-solid-state-drives-are-not-that- - solid/ + [1]: https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ + [2]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465663 Title: libata Samsung SSD 8 series TRIM blacklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465663] Re: libata Samsung SSD 8 series TRIM blacklist
As we are anticipating the issue, based on others feedback, we don't have logs. And having logs for data corruption sounds highly difficult to obtain. So, confirming it. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465663 Title: libata Samsung SSD 8 series TRIM blacklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436755] Re: Memory violation in cf-agent
** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436755 Title: Memory violation in cf-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cfengine3/+bug/1436755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436755] [NEW] Memory violation in cf-agent
Public bug reported: Dear all, In a setup where cf-agent is started by cf-execd and where cf-agent updates its promises from a remote location, if network connection fails for whatever reason during the cf-agent run, cf-agent will crash. I cannot say exactly when though... Audit always reports such error: node=rose-playground type=ANOM_ABEND msg=audit(1427331215.144:55001): auid=0 uid=0 gid=0 ses=114 pid=24294 comm=cf-agent reason=memory violation sig=6 While the email sent by cf-execd can be: !! Could not close socket !!! System error for cf_closesocket: Bad file descriptor *** Error in `/var/lib/cfengine3/bin/cf-agent': free(): invalid pointer: 0x01b37110 *** Aborted Or: *** Error in `/var/lib/cfengine3/bin/cf-agent': double free or corruption (!prev): 0x01620ab0 *** Aborted ** Affects: cfengine3 (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436755 Title: Memory violation in cf-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cfengine3/+bug/1436755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433960] [NEW] log rotate script broken
Public bug reported: Dear all, The logrotate configuration script in Trusty is broken. It uses the following command as postrotate script: invoke-rc.d php5-fpm reopen-logs /dev/null Whereas the reopen-logs command isn't supported: # invoke-rc.d php5-fpm reopen-logs initctl: invalid command: reopen-logs Try `initctl --help' for more information. invoke-rc.d: initscript php5-fpm, action reopen-logs failed. ** Affects: php5-fpm (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/1433960 Title: log rotate script broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5-fpm/+bug/1433960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433960] Re: log rotate script broken
*** This bug is a duplicate of bug 1230917 *** https://bugs.launchpad.net/bugs/1230917 ** This bug has been marked a duplicate of bug 1230917 [SRU] php5-fpm logrotate errors after package switched to upstart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433960 Title: log rotate script broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5-fpm/+bug/1433960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181777] Re: kvm: freeze a guest with a NIC PCI passthrough
This also affects Trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181777 Title: kvm: freeze a guest with a NIC PCI passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1181777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181777] Re: kvm: freeze a guest with a NIC PCI passthrough
This also affects Trusty. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to seabios in Ubuntu. https://bugs.launchpad.net/bugs/1181777 Title: kvm: freeze a guest with a NIC PCI passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1181777/+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 1400453] Re: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed.
So, after discussing with the devs, when called from a SVN hook, a leading / is added to the path and it produces the error. If removed, it doesn't hit the assert. So, the bug is that kgb-client should chomp the leadng / if any. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400453 Title: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kgb-bot/+bug/1400453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400453] Re: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed.
** Bug watch added: Debian Bug tracker #772735 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772735 ** Also affects: kgb-bot (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772735 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400453 Title: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kgb-bot/+bug/1400453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400453] [NEW] svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed.
Public bug reported: Dear all, KGB-client is totally broken on Ubuntu 14.04 LTS with SVN repository. When invoking it as it would be from a hook: kgb-client --conf /etc/kgb-client/kgb-reactos.conf --repository svn /srv/svn/reactos/ 65590 given is experimental at /usr/bin/kgb-client line 245. when is experimental at /usr/bin/kgb-client line 246. when is experimental at /usr/bin/kgb-client line 247. given is experimental at /usr/bin/kgb-client line 265. when is experimental at /usr/bin/kgb-client line 266. when is experimental at /usr/bin/kgb-client line 267. given is experimental at /usr/bin/kgb-client line 293. when is experimental at /usr/bin/kgb-client line 294. when is experimental at /usr/bin/kgb-client line 295. perl: /build/buildd/subversion-1.8.8/subversion/libsvn_subr/dirent_uri.c:972: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed. Aborted Googled a bit, and found this: http://svn.haxx.se/dev/archive-2014-01/0161.shtml So, this is related to subversion 1.8.8. A kind of fix is proposed here: http://svn.haxx.se/dev/archive-2014-01/0162.shtml Cheers, Pierre ** Affects: kgb-bot (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/1400453 Title: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kgb-bot/+bug/1400453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400453] Re: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed.
I also tried with package 1.33-2ubuntu1 (from Vivid), nothing better, still the same error (less verbose though :-)): kgb-client --conf /etc/kgb-client/kgb-reactos.conf --repository svn /srv/svn/reactos/ 65590 perl: /build/buildd/subversion-1.8.8/subversion/libsvn_subr/dirent_uri.c:972: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed. Aborted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400453 Title: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kgb-bot/+bug/1400453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400453] Re: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed.
It's interestingg to note that with the latest package, the assertion still fails BUT it can display a bit of information: commiter name, files changed. But it eats the commit message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400453 Title: svn_dirent_join: Assertion `svn_dirent_is_canonical(base, pool)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kgb-bot/+bug/1400453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358305] Re: harden default ssl settings
Disabling SSLv3 is WIP on Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=765347 ** Bug watch added: Debian Bug tracker #765347 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765347 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1358305 Title: harden default ssl settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1358305/+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 1358305] Re: harden default ssl settings
Disabling SSLv3 is WIP on Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=765347 ** Bug watch added: Debian Bug tracker #765347 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765347 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358305 Title: harden default ssl settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1358305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189436] Re: php5 SIGSEGV on XCache vars query
Unfortunately, I cannot reproduce with the up to date release of php5 on Ubuntu 12.04 LTS. So I guess it's resolved. Version being now: # php5 -v PHP 5.3.10-1ubuntu3.13 with Suhosin-Patch (cli) (built: Jul 7 2014 18:54:55) Copyright (c) 1997-2012 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies ** Changed in: xcache (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189436 Title: php5 SIGSEGV on XCache vars query To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xcache/+bug/1189436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] Re: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic
We cannot unfortunately test upstream kernel due to a regression in recent kernels we couldn't track yet (in connections bridging). Furthermore, this crash happened only once in several months in production. And finally, this is a production server on which we're pretty not willing doing tests. It has to remain stable. ** Tags added: kernel-unable-to-test-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] Re: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic
** Changed in: linux (Ubuntu) Status: Incomplete = New ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] [NEW] Null pointer dereference in mmu_set_spte.isra
Public bug reported: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of our hypervisors (running several KVM VMs). This lead us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). ** Affects: kvm (Ubuntu) Importance: Undecided Status: New ** Attachment added: Kernel oops https://bugs.launchpad.net/bugs/1352794/+attachment/4170197/+files/syslog -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1352794/+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 1352794] Re: Null pointer dereference in mmu_set_spte.isra
** Description changed: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of - our hypervisors (running several KVM VMs). This lead us to a serie of + our hypervisors (running several KVM VMs). This led us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1352794/+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 1352794] [NEW] Null pointer dereference in mmu_set_spte.isra
Public bug reported: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of our hypervisors (running several KVM VMs). This lead us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). ** Affects: kvm (Ubuntu) Importance: Undecided Status: New ** Attachment added: Kernel oops https://bugs.launchpad.net/bugs/1352794/+attachment/4170197/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] Re: Null pointer dereference in mmu_set_spte.isra
** Description changed: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of - our hypervisors (running several KVM VMs). This lead us to a serie of + our hypervisors (running several KVM VMs). This led us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170588/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170587/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] Re: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic
apport information ** Tags added: apport-collected precise ** Description changed: Dear all, We faced a kernel oops on KVM from a null pointer derefence on one of our hypervisors (running several KVM VMs). This led us to a serie of kernel oops affecting all the VMs and finally, the host crash. We couldn't really establish where from the first oops was comming (in order to reproduce the crash). You'll find attach the extract of syslog where you have the really first oops, and all the followings. - We're using Ubuntu 12.04LTS. We're using latest releases available on - it, including for KVM. We're using kernel 3.8 due to hardware - constraints. And we're using kernel 3.8.0-33-generic due to regressions - in newer kernels (not yet reported). + We're using Ubuntu 12.04LTS. We're using latest releases available on it, including for KVM. We're using kernel 3.8 due to hardware constraints. And we're using kernel 3.8.0-33-generic due to regressions in newer kernels (not yet reported). + --- + AlsaDevices: + total 0 + crw-rw---T 1 root audio 116, 1 Aug 4 14:07 seq + crw-rw---T 1 root audio 116, 33 Aug 4 14:07 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.0.1-0ubuntu17.6 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + DistroRelease: Ubuntu 12.04 + HibernationDevice: RESUME=UUID=27b2f2d3-0ec2-4f22-9f6d-c857b6830ab6 + InstallationMedia: + + IwConfig: Error: [Errno 2] No such file or directory + MachineType: MSI MS-7816 + MarkForUpload: True + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-33-generic root=UUID=4ee4d8b4-6b60-4800-b449-a22259277145 ro quiet elevator=deadline + ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 + RelatedPackageVersions: + linux-restricted-modules-3.8.0-33-generic N/A + linux-backports-modules-3.8.0-33-generic N/A + linux-firmware1.79.16 + RfKill: Error: [Errno 2] No such file or directory + Tags: precise + Uname: Linux 3.8.0-33-generic x86_64 + UpgradeStatus: Upgraded to precise on 2012-05-10 (817 days ago) + UserGroups: + + WifiSyslog: + Aug 5 06:25:17 rose kernel: [58628.862288] device eth0 left promiscuous mode + Aug 5 06:25:33 rose kernel: [58644.253374] device eth0 entered promiscuous mode + dmi.bios.date: 08/23/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: V2.14B6 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H87-G43 (MS-7816) + dmi.board.vendor: MSI + dmi.board.version: 1.0 + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: MSI + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.14B6:bd08/23/2013:svnMSI:pnMS-7816:pvr1.0:rvnMSI:rnH87-G43(MS-7816):rvr1.0:cvnMSI:ct3:cvr1.0: + dmi.product.name: MS-7816 + dmi.product.version: 1.0 + dmi.sys.vendor: MSI ** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170586/+files/AcpiTables.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170590/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170595/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170593/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170591/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170589/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170592/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1352794] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1352794/+attachment/4170594/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1352794 Title: Null pointer dereference in mmu_set_spte.isra on 3.8.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181777] Re: kvm: freeze a guest with a NIC PCI passthrough
We're also affected by this bug here. You can actually see my questioning on libvirt-users about this: https://www.redhat.com/archives/libvirt-users/2014-July/msg00134.html Using rom bar='off'/ fixes it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to seabios in Ubuntu. https://bugs.launchpad.net/bugs/1181777 Title: kvm: freeze a guest with a NIC PCI passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1181777/+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 1181777] Re: kvm: freeze a guest with a NIC PCI passthrough
This workaround unfortunately appear to totally break the network card in the VM making it unusable. TG3 driver (which is supposed to handle it) cannot properly communicate with it. The kernel outputs the following lines: Jul 30 13:32:03 carrier-commander kernel: [0.981658] tg3 :00:05.0: PCI INT B - Link[LNKB] - GSI 10 (level, high) - IRQ 10 Jul 30 13:32:03 carrier-commander kernel: [0.981722] tg3 :00:05.0: setting latency timer to 64 Jul 30 13:32:03 carrier-commander kernel: [0.988207] tg3 :00:05.0: phy probe failed, err -19 Jul 30 13:32:03 carrier-commander kernel: [0.993954] tg3 :00:05.0: Problem fetching invariants of chip, aborting Jul 30 13:32:03 carrier-commander kernel: [1.047883] tg3 :00:05.0: Refused to change power state, currently in D0 Jul 30 13:32:03 carrier-commander kernel: [1.047916] tg3 :00:05.0: PCI INT B disabled The weird thing being this -19 error, ie, -ENODEV. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to seabios in Ubuntu. https://bugs.launchpad.net/bugs/1181777 Title: kvm: freeze a guest with a NIC PCI passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1181777/+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 1181777] Re: kvm: freeze a guest with a NIC PCI passthrough
We're also affected by this bug here. You can actually see my questioning on libvirt-users about this: https://www.redhat.com/archives/libvirt-users/2014-July/msg00134.html Using rom bar='off'/ fixes it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181777 Title: kvm: freeze a guest with a NIC PCI passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1181777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181777] Re: kvm: freeze a guest with a NIC PCI passthrough
This workaround unfortunately appear to totally break the network card in the VM making it unusable. TG3 driver (which is supposed to handle it) cannot properly communicate with it. The kernel outputs the following lines: Jul 30 13:32:03 carrier-commander kernel: [0.981658] tg3 :00:05.0: PCI INT B - Link[LNKB] - GSI 10 (level, high) - IRQ 10 Jul 30 13:32:03 carrier-commander kernel: [0.981722] tg3 :00:05.0: setting latency timer to 64 Jul 30 13:32:03 carrier-commander kernel: [0.988207] tg3 :00:05.0: phy probe failed, err -19 Jul 30 13:32:03 carrier-commander kernel: [0.993954] tg3 :00:05.0: Problem fetching invariants of chip, aborting Jul 30 13:32:03 carrier-commander kernel: [1.047883] tg3 :00:05.0: Refused to change power state, currently in D0 Jul 30 13:32:03 carrier-commander kernel: [1.047916] tg3 :00:05.0: PCI INT B disabled The weird thing being this -19 error, ie, -ENODEV. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181777 Title: kvm: freeze a guest with a NIC PCI passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1181777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318948] [NEW] Snort daily report doesn't include IPv6 events
Public bug reported: By default, Snort sends a daily report by email about events that occurred during last day. Unfortunately, even when Snort is configured to watch both IPv4 IPv6 networks, this email only contains IPv4 events. I could check with Prelude that Snort properly catches IPv6 events and forwards them to Prelude. They are only missing in daily report. Using: 2.9.2-3ubuntu1 on Ubuntu 12.04LTS. ** Affects: snort (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/1318948 Title: Snort daily report doesn't include IPv6 events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snort/+bug/1318948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297487] Re: MTU not honored in virtio vnet
ii libselinux1 2.1.0-4.1ubuntu1 SELinux runtime shared libraries ii linux-firmware 1.79.12 Firmware for Linux kernel drivers ii linux-headers-3.2.0-60 3.2.0-60.91 Header files related to Linux kernel version 3.2.0 ii linux-headers-3.2.0-60-generic 3.2.0-60.91 Linux kernel headers for version 3.2.0 on 64 bit x86 SMP ii linux-headers-3.2.0-61 3.2.0-61.92 Header files related to Linux kernel version 3.2.0 ii linux-headers-3.2.0-61-generic 3.2.0-61.92 Linux kernel headers for version 3.2.0 on 64 bit x86 SMP ii linux-headers-server 3.2.0.61.72 Linux kernel headers on Server Equipment. rc linux-image-2.6.32-21-server 2.6.32-21.32 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-22-server 2.6.32-22.36 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-24-server 2.6.32-24.43 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-25-server 2.6.32-25.45 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-26-server 2.6.32-26.48 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-27-server 2.6.32-27.49 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-29-server 2.6.32-29.58 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-30-server 2.6.32-30.59 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-33-server 2.6.32-33.72 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-34-server 2.6.32-34.77 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-35-server 2.6.32-35.78 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-37-server 2.6.32-37.81 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-38-server 2.6.32-38.83 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-39-server 2.6.32-39.86 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-40-server 2.6.32-40.87 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-41-server 2.6.32-41.88 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-3.2.0-24-generic 3.2.0-24.39 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-25-generic 3.2.0-25.40 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-26-generic 3.2.0-26.41 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-27-generic 3.2.0-27.43 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-29-generic 3.2.0-29.46 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-30-generic 3.2.0-30.48 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-31-generic 3.2.0-31.50 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-32-generic 3.2.0-32.51 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-33-generic 3.2.0-33.52 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-34-generic 3.2.0-34.53 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-35-generic 3.2.0-35.55 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-36-generic 3.2.0-36.57 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-37-generic 3.2.0-37.58 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-38-generic 3.2.0-38.61 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-39-generic 3.2.0-39.62 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-40-generic 3.2.0-40.64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-41-generic 3.2.0-41.66
[Bug 1297487] Re: MTU not honored in virtio vnet
ii libselinux1 2.1.0-4.1ubuntu1 SELinux runtime shared libraries ii linux-firmware 1.79.12 Firmware for Linux kernel drivers ii linux-headers-3.2.0-60 3.2.0-60.91 Header files related to Linux kernel version 3.2.0 ii linux-headers-3.2.0-60-generic 3.2.0-60.91 Linux kernel headers for version 3.2.0 on 64 bit x86 SMP ii linux-headers-3.2.0-61 3.2.0-61.92 Header files related to Linux kernel version 3.2.0 ii linux-headers-3.2.0-61-generic 3.2.0-61.92 Linux kernel headers for version 3.2.0 on 64 bit x86 SMP ii linux-headers-server 3.2.0.61.72 Linux kernel headers on Server Equipment. rc linux-image-2.6.32-21-server 2.6.32-21.32 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-22-server 2.6.32-22.36 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-24-server 2.6.32-24.43 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-25-server 2.6.32-25.45 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-26-server 2.6.32-26.48 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-27-server 2.6.32-27.49 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-29-server 2.6.32-29.58 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-30-server 2.6.32-30.59 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-33-server 2.6.32-33.72 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-34-server 2.6.32-34.77 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-35-server 2.6.32-35.78 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-37-server 2.6.32-37.81 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-38-server 2.6.32-38.83 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-39-server 2.6.32-39.86 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-40-server 2.6.32-40.87 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-2.6.32-41-server 2.6.32-41.88 Linux kernel image for version 2.6.32 on x86_64 rc linux-image-3.2.0-24-generic 3.2.0-24.39 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-25-generic 3.2.0-25.40 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-26-generic 3.2.0-26.41 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-27-generic 3.2.0-27.43 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-29-generic 3.2.0-29.46 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-30-generic 3.2.0-30.48 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-31-generic 3.2.0-31.50 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-32-generic 3.2.0-32.51 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-33-generic 3.2.0-33.52 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-34-generic 3.2.0-34.53 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-35-generic 3.2.0-35.55 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-36-generic 3.2.0-36.57 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-37-generic 3.2.0-37.58 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-38-generic 3.2.0-38.61 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-39-generic 3.2.0-39.62 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-40-generic 3.2.0-40.64 Linux kernel image for version 3.2.0 on 64 bit x86 SMP rc linux-image-3.2.0-41-generic 3.2.0-41.66
[Bug 1170585] Re: whitelist incorrect rule
Well, now that I use the tool above, I don't have the WL issue anylonger (yeah, I forgot to say it in the first place). The only issue I could find up to now is WL with vars having '[', ']' in their names. There's an open bug report on their Google code place. And even applying the workaround from there fails. Likely a told old naxsi release. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1170585 Title: whitelist incorrect rule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170585/+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 1170585] Re: whitelist incorrect rule
Well, now that I use the tool above, I don't have the WL issue anylonger (yeah, I forgot to say it in the first place). The only issue I could find up to now is WL with vars having '[', ']' in their names. There's an open bug report on their Google code place. And even applying the workaround from there fails. Likely a told old naxsi release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170585 Title: whitelist incorrect rule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170585] Re: whitelist incorrect rule
I've been successfully using nx_utils.py from here: http://naxsi.googlecode.com/svn/tags/0.50/contrib/nx_util/nx_lib/ with 1.1.19. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1170585 Title: whitelist incorrect rule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170585/+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 1170585] Re: whitelist incorrect rule
I've been successfully using nx_utils.py from here: http://naxsi.googlecode.com/svn/tags/0.50/contrib/nx_util/nx_lib/ with 1.1.19. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170585 Title: whitelist incorrect rule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297487] Re: MTU not honored in virtio vnet
Also affected by this bug with Ubuntu 12.04LTS kvm. A tracepath in a VM with virtio network card ends with: Resume: pmtu 65535. While with pcnet or rtl8139 it properly ends with: Resume: pmtu 1500 This is pretty blocking given some servers are failing to communicate because of the wrong MTU (I've the case with a mail server). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1297487 Title: MTU not honored in virtio vnet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1297487/+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 1297487] Re: MTU not honored in virtio vnet
Also affected by this bug with Ubuntu 12.04LTS kvm. A tracepath in a VM with virtio network card ends with: Resume: pmtu 65535. While with pcnet or rtl8139 it properly ends with: Resume: pmtu 1500 This is pretty blocking given some servers are failing to communicate because of the wrong MTU (I've the case with a mail server). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297487 Title: MTU not honored in virtio vnet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1297487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170586] Re: [SRU] Naxsi package lacking Stub Status
Hi, Deployed with success on our infrastructure. Everything is working fine. Munin is properly reading status. Web server is properly serving data. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170586 Title: [SRU] Naxsi package lacking Stub Status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170586] Re: Naxsi package lacking Stub Status
Any potential ETA regarding the fix for Precise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170586 Title: Naxsi package lacking Stub Status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170586] Re: Naxsi package lacking Stub Status
Dunno what kind of test case you want, but basically try to start nginx with
this in your config:
server {
listen 127.0.0.1;
server_name localhost;
location /nginx_status {
stub_status on;
access_log off;
allow 127.0.0.1;
deny all;
}
}
If it refuses to start due to stub_status line, then it's not fixed.
Otherwise, it will just start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170586
Title:
Naxsi package lacking Stub Status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170586/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232672] Re: Trigger taking forever
Hi, it will be available through precise-backports? Any idea about the ETA? Regards, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232672 Title: Trigger taking forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/buildbot/+bug/1232672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170586] Re: Naxsi package lacking Stub Status
Well looking at Debian package page (http://packages.debian.org/wheezy /nginx-naxsi) regarding the first version available (1.2.1-2), it is providing Stub Status. Maybe it can help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170586 Title: Naxsi package lacking Stub Status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170586] Re: Naxsi package lacking Stub Status
Thanks for your answer, I fully get your point! Then, in case 1.1.9 never had such module, I'd support for having it in Ubuntu. Additionnal features it adds are rather limited and harmless. The main purpose of this module (which has to explicitly be activated through config file) is to provide data about the server (memory pool, number of connections, and so on). Basically, it can be easily interfaced with Munin plugins to provide an overview of the server. The main purpose of such module is not really providing more features to the end user/web devs, it's just about monitoring. If you think this could make discussions with the MOTUs eaiser... I can provide you even more data about its output or its configuration if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170586 Title: Naxsi package lacking Stub Status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232672] [NEW] Trigger taking forever
Public bug reported: Hi, with the upgrade to 0.8.5 in Ubuntu Precise 12.04LTS, it appears that we are facing several bugs where buildbot waits just forever. Especially on trigger steps (for example: http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/4307). Looking at buildbot trac, shows this bug which explains the problem: http://trac.buildbot.net/ticket/2177, which itself redirects to: http://trac.buildbot.net/ticket/2005. It appears that the bug was last fixed with latest commit and release 0.8.6. Would it be possible to either backport 0.8.6 or at least the fix? With my best regards, Pierre Schweitzer ** Affects: buildbot (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, - with the upgrade to 0.8.5 in Ubuntu, it appears that we are facing several bugs where buildbot waits just forever. Especially on trigger steps (for example: http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/4307). + with the upgrade to 0.8.5 in Ubuntu Precise 12.04LTS, it appears that we are facing several bugs where buildbot waits just forever. Especially on trigger steps (for example: http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/4307). Looking at buildbot trac, shows this bug which explains the problem: http://trac.buildbot.net/ticket/2177, which itself redirects to: http://trac.buildbot.net/ticket/2005. It appears that the bug was last fixed with latest commit and release 0.8.6. Would it be possible to either backport 0.8.6 or at least the fix? With my best regards, Pierre Schweitzer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232672 Title: Trigger taking forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/buildbot/+bug/1232672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189436] [NEW] php5 SIGSEGV on XCache vars query
Public bug reported: Hi, Using the following config: # php5 -v PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626/apc.so' - /usr/lib/php5/20090626/apc.so: cannot open shared object file: No such file or directory in Unknown on line 0 PHP 5.3.10-1ubuntu3.6 with Suhosin-Patch (cli) (built: Mar 11 2013 14:31:48) Copyright (c) 1997-2012 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies with XCache v1.3.2, Copyright (c) 2005-2011, by mOo XCache package installed being: Version: 1.3.2-1 When using munin_xcache.php from http://www.ohardt.net/dev/munin/, php5 crashes with SIGSEGV: [10-Jun-2013 11:50:23] WARNING: [pool www] child 1449 exited on signal 11 (SIGSEGV - core dumped) after 1206.035654 seconds from start Please find attached XCache config. You can find core dump here: http://fc.isima.fr/~schweitz/schweitz/core Regards, ** Affects: xcache (Ubuntu) Importance: Undecided Status: New ** Attachment added: XCache config https://bugs.launchpad.net/bugs/1189436/+attachment/3699769/+files/xcache.ini -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189436 Title: php5 SIGSEGV on XCache vars query To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xcache/+bug/1189436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170585] [NEW] whitelist incorrect rule
Public bug reported: Hi, when importing this wl rule into naxsi: # total_count:2186 (1.37%), peer_count:297 (25.94%) | sql keywords BasicRule wl:1000 mz:$URL_VAR:cookie; nginx can't be restarted anylonger and displays the error: Restarting nginx: nginx: [emerg] Naxsi-Config : Incorrect line BasicRule wl:1000 (/build/buildd/nginx-1.1.19/debian/modules/naxsi/naxsi_src/naxsi_skeleton.c/329)... in /etc/nginx/mynaxsi.rules:7 nginx: configuration file /etc/nginx/nginx.conf test failed This rule was generated by nx_util.py. nginx release in use is the one in Ubuntu 12.04LTS, fully updated. # nginx -V nginx version: nginx/1.1.19 TLS SNI support enabled configure arguments: --prefix=/etc/nginx --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-log-path=/var/log/nginx/access.log --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --lock-path=/var/lock/nginx.lock --pid-path=/var/run/nginx.pid --with-http_ssl_module --without-mail_pop3_module --without-mail_smtp_module --without-mail_imap_module --without-http_uwsgi_module --without-http_scgi_module --with-ipv6 --add-module=/build/buildd/nginx-1.1.19/debian/modules/nginx-upstream-fair --add-module=/build/buildd/nginx-1.1.19/debian/modules/nginx-cache-purge --add-module=/build/buildd/nginx-1.1.19/debian/modules/naxsi/naxsi_src This looks similar to: https://code.google.com/p/naxsi/issues/detail?id=30 Regards, ** Affects: nginx (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/1170585 Title: whitelist incorrect rule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170586] [NEW] Naxsi package lacking Stub Status
Public bug reported: Hi, The nginx-naxsi package provided in Ubuntu 12.04 LTS lacks the Stub Status module which somehow mandatory in production environment. Plus, if Ubuntu follows Debian philosophy regarding those packages, it is supposed to be shipped with in Debian: http://wiki.debian.org/Nginx. Current nginx -V: # nginx -V nginx version: nginx/1.1.19 TLS SNI support enabled configure arguments: --prefix=/etc/nginx --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-log-path=/var/log/nginx/access.log --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --lock-path=/var/lock/nginx.lock --pid-path=/var/run/nginx.pid --with-http_ssl_module --without-mail_pop3_module --without-mail_smtp_module --without-mail_imap_module --without-http_uwsgi_module --without-http_scgi_module --with-ipv6 --add-module=/build/buildd/nginx-1.1.19/debian/modules/nginx-upstream-fair --add-module=/build/buildd/nginx-1.1.19/debian/modules/nginx-cache-purge --add-module=/build/buildd/nginx-1.1.19/debian/modules/naxsi/naxsi_src Regards, P. Schweitzer ** Affects: nginx (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/1170586 Title: Naxsi package lacking Stub Status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926156] Re: Warning: Hidden file found: /dev/.initramfs: symbolic link to `/run/initramfs' (fixed upstream)
Hi, is there a chance that rkhunter is updated in Precise, as it has not been in Oneric? This bug also affects it. Which is really annoying for a LTS used on servers... Regards, Pierre S. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926156 Title: Warning: Hidden file found: /dev/.initramfs: symbolic link to `/run/initramfs' (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rkhunter/+bug/926156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
