[Bug 1607694] Re: Exclusive-Lock Issue
@jdillaman That would be awesome, I'd test this version on our servers to see if it resolves our problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607694 Title: Exclusive-Lock Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1607694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault
Had the same divide error and a hanging server myself. Ubuntu 16.04.1 LTS with "linux-image-4.4.0-31-generic". Now running "linux- image-4.4.0-34-generic". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568729 Title: divide error: [#1] SMP in task_numa_migrate - handle_mm_fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607694] Re: Exclusive-Lock Issue
Thanks for the possible workaround. But fast-diff is a very important feature for us and unfortunately disabling it is not an options for us. The virtual machine gets killed almost every night at the moment. Is there an estimated time window for the fix in sight? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607694 Title: Exclusive-Lock Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1607694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445595] Re: Empty trash from Launcher results in Nautilus window opening
I can confirm that it is still occurring in 15.10. I have this problem since 15.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty trash from Launcher results in Nautilus window opening To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503382] Re: unable to install python3.4 dev on fresh ubuntu cloud image
Same problem here with the newest trusty lxc image/template. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503382 Title: unable to install python3.4 dev on fresh ubuntu cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470778] [NEW] Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines
Public bug reported: We have multiple servers with multiple VMs running. The error only occured on the server with Ubuntu 14.04 LTS. All other servers have Ubuntu 12.04 LTS. libvirt-bin: Installiert: 1.2.2-0ubuntu13.1.12 Installationskandidat: 1.2.2-0ubuntu13.1.12 Versionstabelle: *** 1.2.2-0ubuntu13.1.12 0 500 http://mirror.d9t.de/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu13.1.7 0 500 http://mirror.d9t.de/ubuntu/ trusty-security/main amd64 Packages 1.2.2-0ubuntu13 0 500 http://mirror.d9t.de/ubuntu/ trusty/main amd64 Packages libvirt0: Installiert: 1.2.2-0ubuntu13.1.12 Installationskandidat: 1.2.2-0ubuntu13.1.12 Versionstabelle: *** 1.2.2-0ubuntu13.1.12 0 500 http://mirror.d9t.de/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu13.1.7 0 500 http://mirror.d9t.de/ubuntu/ trusty-security/main amd64 Packages 1.2.2-0ubuntu13 0 500 http://mirror.d9t.de/ubuntu/ trusty/main amd64 Packages Expected behaviour: - Virtual machines keep running while/after the unattended upgrade What happened instead: - All virtual machines were killed ** Affects: libvirt (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/1470778 Title: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470778] Re: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines
Censored server ** Description changed: We have multiple servers with multiple VMs running. The error only occured on the server with Ubuntu 14.04 LTS. All other servers have Ubuntu 12.04 LTS. libvirt-bin: - Installiert: 1.2.2-0ubuntu13.1.12 - Installationskandidat: 1.2.2-0ubuntu13.1.12 - Versionstabelle: - *** 1.2.2-0ubuntu13.1.12 0 - 500 http://mirror.d9t.de/ubuntu/ trusty-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1.2.2-0ubuntu13.1.7 0 - 500 http://mirror.d9t.de/ubuntu/ trusty-security/main amd64 Packages - 1.2.2-0ubuntu13 0 - 500 http://mirror.d9t.de/ubuntu/ trusty/main amd64 Packages + Installiert: 1.2.2-0ubuntu13.1.12 + Installationskandidat: 1.2.2-0ubuntu13.1.12 + Versionstabelle: + *** 1.2.2-0ubuntu13.1.12 0 + 500 http://mirror.server.de/ubuntu/ trusty-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1.2.2-0ubuntu13.1.7 0 + 500 http://mirror.server.de/ubuntu/ trusty-security/main amd64 Packages + 1.2.2-0ubuntu13 0 + 500 http://mirror.server.de/ubuntu/ trusty/main amd64 Packages libvirt0: - Installiert: 1.2.2-0ubuntu13.1.12 - Installationskandidat: 1.2.2-0ubuntu13.1.12 - Versionstabelle: - *** 1.2.2-0ubuntu13.1.12 0 - 500 http://mirror.d9t.de/ubuntu/ trusty-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1.2.2-0ubuntu13.1.7 0 - 500 http://mirror.d9t.de/ubuntu/ trusty-security/main amd64 Packages - 1.2.2-0ubuntu13 0 - 500 http://mirror.d9t.de/ubuntu/ trusty/main amd64 Packages + Installiert: 1.2.2-0ubuntu13.1.12 + Installationskandidat: 1.2.2-0ubuntu13.1.12 + Versionstabelle: + *** 1.2.2-0ubuntu13.1.12 0 + 500 http://mirror.server.de/ubuntu/ trusty-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1.2.2-0ubuntu13.1.7 0 + 500 http://mirror.server.de/ubuntu/ trusty-security/main amd64 Packages + 1.2.2-0ubuntu13 0 + 500 http://mirror.server.de/ubuntu/ trusty/main amd64 Packages Expected behaviour: - Virtual machines keep running while/after the unattended upgrade What happened instead: - All virtual machines were killed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470778 Title: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470778] [NEW] Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines
Public bug reported: We have multiple servers with multiple VMs running. The error only occured on the server with Ubuntu 14.04 LTS. All other servers have Ubuntu 12.04 LTS. libvirt-bin: Installiert: 1.2.2-0ubuntu13.1.12 Installationskandidat: 1.2.2-0ubuntu13.1.12 Versionstabelle: *** 1.2.2-0ubuntu13.1.12 0 500 http://mirror.d9t.de/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu13.1.7 0 500 http://mirror.d9t.de/ubuntu/ trusty-security/main amd64 Packages 1.2.2-0ubuntu13 0 500 http://mirror.d9t.de/ubuntu/ trusty/main amd64 Packages libvirt0: Installiert: 1.2.2-0ubuntu13.1.12 Installationskandidat: 1.2.2-0ubuntu13.1.12 Versionstabelle: *** 1.2.2-0ubuntu13.1.12 0 500 http://mirror.d9t.de/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu13.1.7 0 500 http://mirror.d9t.de/ubuntu/ trusty-security/main amd64 Packages 1.2.2-0ubuntu13 0 500 http://mirror.d9t.de/ubuntu/ trusty/main amd64 Packages Expected behaviour: - Virtual machines keep running while/after the unattended upgrade What happened instead: - All virtual machines were killed ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1470778 Title: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+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 1470778] Re: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines
** Attachment added: libvirtd.log https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+attachment/4423756/+files/libvirtd.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470778 Title: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470778] Re: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines
** Attachment added: term.log https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+attachment/4423757/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470778 Title: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470778] Re: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines
** Attachment added: testvm.log https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+attachment/4423758/+files/testvm.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470778 Title: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470778] Re: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines
** Attachment added: dpkg.log https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+attachment/4423755/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470778 Title: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470778] Re: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines
It seems like the timestamps in libvirtd.log are not correct. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470778 Title: Unattended upgrade of libvirt-bin and libvirt0 killed virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1470778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95853] Re: Nautilus: too easy to move files/folders to Trash (single key press of Delete)
I don't understand whats the problem with giving users the choice of letting nautilus prompt before moving files to trash. It could also be disabled by default but we should be able to choose! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/95853 Title: Nautilus: too easy to move files/folders to Trash (single key press of Delete) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/95853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448229] Re: Launcher Trash icon: Empty Trash option opens nautilus @ home
*** This bug is a duplicate of bug 1445595 *** https://bugs.launchpad.net/bugs/1445595 Same for me. Happening on Ubuntu 15.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448229 Title: Launcher Trash icon: Empty Trash option opens nautilus @ home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445595] Re: Empty Trash Results in File Windows Opening
Me too. Same behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty Trash Results in File Windows Opening To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1445595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399202] Re: Lots of Berkeley DB error: PANIC logentries
An addition to my logs from above: 2014-12-08 11:17:13 1XxvNN-00071k-UC Berkeley DB error: /var/lib/exim4/once/hid...@hidden.com.db page 38 is on free list with type 13 It is always the same error: error: /var/lib/exim4/once/xxx.db page 38 is on free list with type 13 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/1399202 Title: Lots of Berkeley DB error: PANIC logentries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1399202/+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 1399202] Re: Lots of Berkeley DB error: PANIC logentries
** Changed in: exim4 (Ubuntu) Status: New = Invalid ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/1399202 Title: Lots of Berkeley DB error: PANIC logentries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1399202/+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 1399202] Re: Lots of Berkeley DB error: PANIC logentries
** Changed in: exim4 (Ubuntu) Status: New = Invalid ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399202 Title: Lots of Berkeley DB error: PANIC logentries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1399202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399202] Re: Lots of Berkeley DB error: PANIC logentries
An addition to my logs from above: 2014-12-08 11:17:13 1XxvNN-00071k-UC Berkeley DB error: /var/lib/exim4/once/hid...@hidden.com.db page 38 is on free list with type 13 It is always the same error: error: /var/lib/exim4/once/xxx.db page 38 is on free list with type 13 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399202 Title: Lots of Berkeley DB error: PANIC logentries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1399202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399202] [NEW] Lots of Berkeley DB error: PANIC logentries
Public bug reported: For a couple of weeks I have the following messages in /var/log/exim4/mainlog. The temporary workaround is to run the following commands: service exim4 stop rm -r /var/spool/exim4/db service exim4 start. After some hours the messages appear again. I haven't found a solution for this problem, yet. Distributor ID: Ubuntu Description:Ubuntu 12.04.5 LTS Release:12.04 Codename: precise ii exim44.76-3ubuntu3.2 metapackage to ease Exim MTA (v4) installation ii exim4-base 4.76-3ubuntu3.2 support files for all Exim MTA (v4) packages ii exim4-config 4.76-3ubuntu3.2 configuration for the Exim MTA (v4) ii exim4-daemon-heavy 4.76-3ubuntu3.2 Exim MTA (v4) daemon with extended features, including exiscan-acl 2014-12-04 10:04:29 1XwSKo-0006uY-V3 Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:04:29 1XwSKo-0006uY-V3 Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:09:29 1XwSPe-00071S-Lg Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:09:29 1XwSPe-00071S-Lg Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:12:49 1XwSSs-000753-WB Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:12:49 1XwSSs-000753-WB Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:30:19 1XwSjo-0007WA-7h Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:30:19 1XwSjo-0007WA-7h Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:31:30 1XwSkz-0007XR-Tb Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:31:30 1XwSkz-0007XR-Tb Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:43:10 1XwSwF-0007l1-KB Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:43:10 1XwSwF-0007l1-KB Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:44:48 1XwSxl-0007o4-Om Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:44:48 1XwSxl-0007o4-Om Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:56:17 1XwT8w-00086x-VO Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:56:17 1XwT8w-00086x-VO Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 11:26:04 1XwTbl-LD-61 Berkeley DB error: PANIC: Invalid argument 2014-12-04 11:26:04 1XwTbl-LD-61 Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 11:47:25 1XwTwQ-lm-Gi Berkeley DB error: PANIC: Invalid argument 2014-12-04 11:47:25 1XwTwQ-lm-Gi Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 11:50:46 1XwTzg-r3-Bn Berkeley DB error: PANIC: Invalid argument 2014-12-04 11:50:46 1XwTzg-r3-Bn Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 12:08:23 1XwUGg-0001H1-85 Berkeley DB error: PANIC: Invalid argument 2014-12-04 12:08:23 1XwUGg-0001H1-85 Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 12:14:01 1XwUMB-0001Ny-LI Berkeley DB error: PANIC: Invalid argument 2014-12-04 12:14:01 1XwUMB-0001Ny-LI Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 12:39:08 1XwUkS-0001v6-2m Berkeley DB error: PANIC: Invalid argument 2014-12-04 12:39:08 1XwUkS-0001v6-2m Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 13:02:22 1XwV6x-0002Px-Fi Berkeley DB error: PANIC: Invalid argument 2014-12-04 13:02:22 1XwV6x-0002Px-Fi Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 13:45:47 1XwVmz-0003L6-58 Berkeley DB error: PANIC: Invalid argument 2014-12-04 13:45:47 1XwVmz-0003L6-58 Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 13:48:20 1XwVpR-0003Nf-Vl Berkeley DB error: PANIC: Invalid argument 2014-12-04 13:48:20 1XwVpR-0003Nf-Vl Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 14:04:02 1XwW4d-0003mL-6y Berkeley DB error: PANIC: Invalid argument 2014-12-04 14:04:02 1XwW4d-0003mL-6y Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 14:26:33 1XwWQQ-0004IS-8k Berkeley DB error: PANIC: Invalid argument 2014-12-04 14:26:33 1XwWQQ-0004IS-8k Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 14:28:49 1XwWSc-0004Kb-UB Berkeley DB error: PANIC: Invalid argument 2014-12-04 14:28:49 1XwWSc-0004Kb-UB Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 14:40:14 1XwWdb-0004Z1-Qp Berkeley DB error: PANIC: Invalid argument 2014-12-04 14:40:14 1XwWdb-0004Z1-Qp Berkeley DB error: PANIC: fatal region error detected; run recovery Kind regards. ** Affects: exim4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of
[Bug 1399202] [NEW] Lots of Berkeley DB error: PANIC logentries
Public bug reported: For a couple of weeks I have the following messages in /var/log/exim4/mainlog. The temporary workaround is to run the following commands: service exim4 stop rm -r /var/spool/exim4/db service exim4 start. After some hours the messages appear again. I haven't found a solution for this problem, yet. Distributor ID: Ubuntu Description:Ubuntu 12.04.5 LTS Release:12.04 Codename: precise ii exim44.76-3ubuntu3.2 metapackage to ease Exim MTA (v4) installation ii exim4-base 4.76-3ubuntu3.2 support files for all Exim MTA (v4) packages ii exim4-config 4.76-3ubuntu3.2 configuration for the Exim MTA (v4) ii exim4-daemon-heavy 4.76-3ubuntu3.2 Exim MTA (v4) daemon with extended features, including exiscan-acl 2014-12-04 10:04:29 1XwSKo-0006uY-V3 Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:04:29 1XwSKo-0006uY-V3 Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:09:29 1XwSPe-00071S-Lg Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:09:29 1XwSPe-00071S-Lg Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:12:49 1XwSSs-000753-WB Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:12:49 1XwSSs-000753-WB Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:30:19 1XwSjo-0007WA-7h Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:30:19 1XwSjo-0007WA-7h Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:31:30 1XwSkz-0007XR-Tb Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:31:30 1XwSkz-0007XR-Tb Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:43:10 1XwSwF-0007l1-KB Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:43:10 1XwSwF-0007l1-KB Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:44:48 1XwSxl-0007o4-Om Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:44:48 1XwSxl-0007o4-Om Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 10:56:17 1XwT8w-00086x-VO Berkeley DB error: PANIC: Invalid argument 2014-12-04 10:56:17 1XwT8w-00086x-VO Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 11:26:04 1XwTbl-LD-61 Berkeley DB error: PANIC: Invalid argument 2014-12-04 11:26:04 1XwTbl-LD-61 Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 11:47:25 1XwTwQ-lm-Gi Berkeley DB error: PANIC: Invalid argument 2014-12-04 11:47:25 1XwTwQ-lm-Gi Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 11:50:46 1XwTzg-r3-Bn Berkeley DB error: PANIC: Invalid argument 2014-12-04 11:50:46 1XwTzg-r3-Bn Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 12:08:23 1XwUGg-0001H1-85 Berkeley DB error: PANIC: Invalid argument 2014-12-04 12:08:23 1XwUGg-0001H1-85 Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 12:14:01 1XwUMB-0001Ny-LI Berkeley DB error: PANIC: Invalid argument 2014-12-04 12:14:01 1XwUMB-0001Ny-LI Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 12:39:08 1XwUkS-0001v6-2m Berkeley DB error: PANIC: Invalid argument 2014-12-04 12:39:08 1XwUkS-0001v6-2m Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 13:02:22 1XwV6x-0002Px-Fi Berkeley DB error: PANIC: Invalid argument 2014-12-04 13:02:22 1XwV6x-0002Px-Fi Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 13:45:47 1XwVmz-0003L6-58 Berkeley DB error: PANIC: Invalid argument 2014-12-04 13:45:47 1XwVmz-0003L6-58 Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 13:48:20 1XwVpR-0003Nf-Vl Berkeley DB error: PANIC: Invalid argument 2014-12-04 13:48:20 1XwVpR-0003Nf-Vl Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 14:04:02 1XwW4d-0003mL-6y Berkeley DB error: PANIC: Invalid argument 2014-12-04 14:04:02 1XwW4d-0003mL-6y Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 14:26:33 1XwWQQ-0004IS-8k Berkeley DB error: PANIC: Invalid argument 2014-12-04 14:26:33 1XwWQQ-0004IS-8k Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 14:28:49 1XwWSc-0004Kb-UB Berkeley DB error: PANIC: Invalid argument 2014-12-04 14:28:49 1XwWSc-0004Kb-UB Berkeley DB error: PANIC: fatal region error detected; run recovery 2014-12-04 14:40:14 1XwWdb-0004Z1-Qp Berkeley DB error: PANIC: Invalid argument 2014-12-04 14:40:14 1XwWdb-0004Z1-Qp Berkeley DB error: PANIC: fatal region error detected; run recovery Kind regards. ** Affects: exim4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of
[Bug 1339405] Re: Wrong Pidgin Unity integration
This bug still exists in 14.04 almost 4 months after it was reported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1339405 Title: Wrong Pidgin Unity integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin-libnotify/+bug/1339405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186662] Re: isc-dhcp-server fails to renew lease file
The problem persists in saucy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239782] Re: Zabbix 2.0.6 PHP mysql_connect() deprecated warning
I followed James' instruction to get the zabbix webinterface up again. This absolutely is a major issue! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239782 Title: Zabbix 2.0.6 PHP mysql_connect() deprecated warning To manage notifications about this bug go to: https://bugs.launchpad.net/wordpress/+bug/1239782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
After another unattended update of procps has failed this morning I figured out that net.ipv4.tcp_mem in 30-iscsitarget.conf causes an error and prevents procps from starting - like Ryan already said. Commenting out that line is a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] Re: procps (1:3.2.8-11ubuntu6.1) upgrade error
Sorry I fixed it with moving /etc/sysctl.d/30-iscsitarget.conf of the folder and then upgrading. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241376] [NEW] procps (1:3.2.8-11ubuntu6.1) upgrade error
Public bug reported: When trying to upgrade procps on ubuntu 12.04.3 LTS I receive some errors, the package stays in broken state and cannot be upgraded: procps (1:3.2.8-11ubuntu6.1) wird eingerichtet ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: Fehler beim Bearbeiten von procps (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bereits erreicht ist Fehler traten auf beim Bearbeiten von: procps E: Sub-process /usr/bin/dpkg returned an error code (1) Ein Paket konnte nicht installiert werden. Versuch, dies zu lösen: procps (1:3.2.8-11ubuntu6.1) wird eingerichtet ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: Fehler beim Bearbeiten von procps (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: procps The versions of procps: Installiert: 1:3.2.8-11ubuntu6.1 Kandidat:1:3.2.8-11ubuntu6.2 Versionstabelle: 1:3.2.8-11ubuntu6.2 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages *** 1:3.2.8-11ubuntu6.1 0 100 /var/lib/dpkg/status 1:3.2.8-11ubuntu6 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages I also ran cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sudo sysctl -p - without an error. ** Affects: procps (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/1241376 Title: procps (1:3.2.8-11ubuntu6.1) upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1241376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
