This bug was fixed in the package linux - 2.6.38-10.46
---
linux (2.6.38-10.46) natty-proposed; urgency=low
[ Steve Conklin ]
* Release Tracking Bug
- LP: #802464
[ Upstream Kernel Changes ]
* Revert put stricter guards on queue dead checks
* Revert fix oops in
Hi Martin,
2011/6/27 Martin Ewing martin.s.ew...@gmail.com
I have a very similar situation with my Belkin UPS on Natty (worked on
previous release).
See
$ lsb_release -rd
Description:Ubuntu 11.04
Release:11.04
martin@gimli:~$ aptitude show nut
Package: nut
State:
Public bug reported:
I am using logwatch 7.3.6.cvs20090906-1ubuntu4 on oneiric with postfix
2.8.3-1.
Logwatch is reporting quite a few errors while parsing postfix log
entries. Here is a complete list from my latest logwatch report:
- Postfix Begin
** Branch linked: lp:ubuntu/bridge-utils
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/483427
Title:
if-pre-up.d script points to script in /usr
To manage notifications
I am currently discussing this upstream. My impression is that this may
be an intended change to get a sane way of naming the xvd devices when
the configuration may mix hd and sd naming. So there is a 4 device
offset done in the enumeration of xvd devices for disks named sd? in the
configuration.
Arnaud,
Thanks for the reply! I imagine you are correct. I ran the command you
suggested (below). Apparently nut knows the device it should connect to,
but that device is busy. And running as root doesn't overcome the
problem... (And I don't know why I should have to make /var/run/nut,
Hello Jacob,
thank you for your reply. I'm not sure whether the Pacemaker resource
definitions are the real problem as I keep getting the following message
Jul 13 16:18:01 node2 ocfs2_controld[29698]: Unable to open checkpoint
ocfs2:controld: Object does not exist
Jul 13 16:18:53 node2
I know how it might not look like a Pacemaker problem but I believe it
is. Pacemaker is in charge of everything. As I put in the comment
before I believe this line disallows Drbd2 to be master on node 2:
location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1
Since everything else
Ok looks good. No zombie processes. I updated and restarted node 1 -
drbd initiated snapsho on startup, synced properly (wouldn't get that
far before) and then removed them. After doing that on node 1 I updated
and restarted node 2 (causing everything to fail to node 1) and
everything moved and
i agree - it seems exec still doesn't work in lucid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/496922
Title:
Ubuntu snmpd package doesn't include all net-snmpd modules
To
This bug still persists in 10.04.2. I can't be that hard to fix guys.
Can it?
--
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/370542
Title:
Accessing http://localhost gives a 403
2011/7/13 Martin Ewing martin.s.ew...@gmail.com
Arnaud,
Thanks for the reply! I imagine you are correct. I ran the command you
suggested (below). Apparently nut knows the device it should connect to,
but that device is busy. And running as root doesn't overcome the
problem... (And I
Jacob-
This is a warning from lvdisplay unrelated and can be ignored in the
context of this bug. Please see http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=466138#15
** Bug watch added: Debian Bug tracker #466138
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466138
--
You received
Thanks Adam/Andres
I've got to remember: Google first, ask second - always not just mostly!
I'll report in again in about a week on this. I am doing a lot of
reconfig, add resources, testing, and failing of my pacemaker cluster so
I will report on how the snapshot patch holds up. It *should*
@Martin Kucej: It is impossible to fix this bug until its root cause is
known, see comments 13 and 14 for details. Please be patient.
** Tags added: maverick natty
** Tags removed: karmic
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Public bug reported:
right now, if there are multiple network adapters in a system, cloud-
init coudl start running cloud-config jobs before network was really up.
That means installing additional packages could be attempted before the
network required was up. cloud-config could start as early
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/810044
Title:
cloud-init will have race conditions for cloud-config with multiple
network adapters
To manage notifications about
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/810044
Title:
cloud-init will have race conditions for
To let you know that you are not alone.. I experienced the not starting
nmbd in maverick and natty also. My workaround is to restart it via
rc.local like:
sleep 30
service nmbd restart
I am glad to see that you are already investigating this. Thank you!
--
You received this bug notification
Blueprint changed by Scott Moser:
Whiteboard changed:
Work Items:
- rename uec-images.ubuntu.com to cloud-images.ubuntu.com: TODO
+ [smoser] rename uec-images.ubuntu.com to cloud-images.ubuntu.com: INPROGRESS
add chef support to cloud-init: TODO
support system or static Eucalyptus modes in
Blueprint changed by Scott Moser:
Whiteboard changed:
Work Items:
[smoser] rename uec-images.ubuntu.com to cloud-images.ubuntu.com: INPROGRESS
add chef support to cloud-init: TODO
[smoser] support system or static Eucalyptus modes in cloud-init (bug
761847): DONE
[smoser] document
Blueprint changed by Scott Moser:
Whiteboard changed:
Work Items:
[smoser] rename uec-images.ubuntu.com to cloud-images.ubuntu.com: INPROGRESS
add chef support to cloud-init: TODO
- support system or static Eucalyptus modes in cloud-init (bug 761847): TODO
- document 'instance-data'
Now that we got a package that builds successfully, I'm going to layout
the plan.
-Later today: Update the branch to June release (including adding the new patch
attached in the comment above)
-By Sunday: Input on anything that needs to changed in the patch. Stuff that
may cause issues, and
** Branch linked: lp:~n-muench/+junk/open-vm-tools-prep
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/807903
Title:
open-vm-tools failed to build on i386 and amd64
To
Public bug reported:
traditionally, unix commands support a '-' to indicate that content should be
written to stdout rather than a file.
It would be nice if 'nova-manage environment' would do this.
ie:
$ sudo nova-manage project environment test-project admin - | grep NOVA_URL
import
** Also affects: nova
Importance: Undecided
Status: New
** Summary changed:
- support '-' for writing to stdout in nova-manage environment
+ support '-' for writing to stdout in nova-manage environment/zip
** Changed in: nova
Status: New = In Progress
--
You received this bug
** Branch linked: lp:~smoser/nova/lp-810157
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/810157
Title:
support '-' for writing to stdout in nova-manage environment/zip
To manage
I've lost auto screen resize and host/guest copy-and-paste. They worked
before the upgrade. So, the plan is now thrown out. The following
files (in the patch) need to be double checked if I did it right. I
WILL NOT GO ANY FURTHER WITHOUT ANY HELP. I've done 95%, the remaining
5% in your
Thanks for taking the time to submit this bug.
I'm afraid I don't understand the problem. Could y please tell us
exactly what you expect to happen?
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server
Thanks for taking the time to submit this bug and helping to make Ubuntu
better.
It sounds like the package file may be corrupted. Could you clear it
out by doing
sudo apt-get clean
and then re-try the upgrade? Please let us know if that did not help.
** Changed in: bind9 (Ubuntu)
Thanks for taking the time to submit this bug.
In the DpkgTerminalLog, I see:
Starting Postfix Mail Transport Agent postfix [80G postfix: warning:
valid_hostname: invalid character 40(decimal): (none)
postfix: fatal: unable to use my own hostname
What do you see when you do each of the
*** This bug is a duplicate of bug 808653 ***
https://bugs.launchpad.net/bugs/808653
** This bug has been marked a duplicate of bug 808653
package postfix 2.8.2-1ubuntu2.1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
--
You
Thanks for taking the time to submit this bug and helping to make Ubuntu
better.
Bind9 objected to your use of '0xE2' (“) rather than '0x22' () to
designate the string for the filename. Could you try using the
following as your /etc/bind/named.conf.local? Please let us know
whether this works.
Thanks for filing this bug.
Is this issue only in maverick, and not in natty or oneiric?
Do I understand right (from
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750/comments/25)
that the fix is to use 'restart squid' instead of 'reload squid' in
/etc/resolvconf/update-libc.d/squid?
Thanks for submitting this bug and helping to make Ubuntu better.
To help us figure out why bind9 did not start, could you please do
grep named /var/log/syslog /tmp/syslog.bind
and attach /tmp/syslog.bind to this bug?
** Changed in: bind9 (Ubuntu)
Status: New = Incomplete
--
Please explain what Job is already running means when the job is _not_
already running. In the general meaning of already running there
should be, well, something running, a process, yet when this message is
issued there is no libvirt-bin or libvirtd or any related process at
all. Nor is there a
I just want to note that, a couple of hours ago, I pushed the patched
May release (listed as the June release) to see if it was the June
release or the Patch (hell even the new kernel update) was the issues.
So the final analysis is it's the patch. I think I screwed up,
somewhere, and it't up to
Thanks for taking the time to submit this bug.
Googling shows several others have run into this, so it definately
appears to be a real bug, somewhere.
Did you have senmdail previously installed and then delete it? Do you
recall whether you removed it with 'apt-get remove' or 'apt-get purge'?
** Changed in: eucalyptus (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/766983
Title:
package eucalyptus-java-common 2.0.1
Thanks for all your work on this, Nate. I'm out the rest of this week,
but will look at this on Monday.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
** Changed in: open-vm-tools (Ubuntu)
Assignee: Nate Muench (n-muench) = Serge Hallyn (serge-hallyn)
--
You
40 matches
Mail list logo
