Great, thanks for your ack't of the update being available for ppc.
--
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/1556306
Title:
vhost-user: qemu stops processing packets under
it seems that the fix was not applied on ppc build:
https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-1ubuntu3/+build/8842754
https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-1ubuntu3/+build/8842753
neither on arm64:
*** This bug is a duplicate of bug 1556306 ***
https://bugs.launchpad.net/bugs/1556306
It is a duplicate. I just wrongly opened 1556306 into wrong the place.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Side question, will you apply it to qemu-kvm from
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/mitaka-staging/+files/qemu-kvm_2.5+dfsg-5ubuntu5~cloud0_amd64.deb
too?
or should I open another bug?
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: horizon (Ubuntu)
Status: Expired => Confirmed
** Changed in: horizon (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
This is a bug in the maintainer script then, and does not invalidate the
bug report.
The workaround works, but is still a workaround and not a proper fix.
** Changed in: horizon (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of
Public bug reported:
Already described here,
https://bugs.launchpad.net/qemu/+bug/1556306
Description of problem:
- qemu socket becomes full, causing qemu to send incomplete
SET_VRING_CALL messages to vhost-user backend (without proper fd set in
ancillary data).
- after some time, some
It never happened again (and may have been a misuse involving immortal
sudo subprocesses but I'm blurry on the details), marking invalid but
fixed released may be correct as well.
** Changed in: lxc (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are
0.6.3-0ubuntu1.22 works fine for me (tested on CloudStack with basic
networking enabled).
** 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 cloud-init in Ubuntu.
Yes, sure, I'll do it.
--
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/1382481
Title:
[SRU] Support for CloudStack's basic networking in Precise
To manage notifications about
@Chris: Thanks !
I had to implement a different scheme not using nested containers but
still requiring lxc-1.1.2.
I'll give nested containers another shot asap.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I run into the same issue on a vivid host while trying to start a trusty
nested container from inside a trusty container.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
@Chris: Where do you add the ubuntu-lxc/daily ppa ? On the host or on
the outer container ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is
Hi Ben!
I am already using this patch. I can prepare a package with it, test it
and provide a debdiff (if that's what you mean with SRU'ify). I am
unable to test if that still works with advanced networking. Would
somebody be able to do that?
--
You received this bug notification because you
Proposed fix for this issue.
** Description changed:
- cloud-init in Precise is unable to handle CloudStack because it tries to
- query the default gateway instead of the virtual router. This is fixed
- in later versions of cloud-init but it would be convenient to backport
- the fix in the
Hi Ben!
All done. Note that I tagged with verification-done but this should also
be checked to work with advanced networking (I am pretty sure that won't
be a problem, this is just a backport).
The test case may be difficult to execute in real conditions: with the
current VM images, you won't be
Yes, that's correct. It doesn't affect advanced networking where the
vrouter is the default gateway (hence its name).
--
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/1382481
Title:
Here is an updated patch. Please consider it for the next release. It
has been tested on a Cloudstack setup running with basic networking. It
is extracted from what currently is in cloud-init.
** Patch added: lp-1382481-cloudstack-vr.patch
Hey!
I see that there has been some updates to cloud-init in Precise but this
change was not even considered. Without this change, this data source
cannot work when CloudStack is configured with basic networking (in this
case, the virtual router is not the gateway). What should be done for
this
Building on top of the added test (test_cloud_config_archive), using the
following breaks (the yaml can't be parsed):
message = '''#cloud-config-archive
- content: #cloud-config\napt_update: true\napt_upgrade: true\nchpasswd:\n
expire:\
\ false\nmanage_etc_hosts:
** Package changed: snappy (Ubuntu) = snappy-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to snappy in Ubuntu.
https://bugs.launchpad.net/bugs/1443557
Title:
snappy update error message 'already locked' is confusing
To
Public bug reported:
Running 'snappy update' may issue an 'already locked' error message.
mvo explained that this is caued by 'autopilot' running in the
background and 'tail /var/log/syslog' contains more details (indeed it
does).
The message is confusing for a newcomer.
** Affects: snappy
Public bug reported:
cloud-init in Precise is unable to handle CloudStack because it tries to
query the default gateway instead of the virtual router. This is fixed
in later versions of cloud-init but it would be convenient to backport
the fix in the precise-updates. Attached is a patch fixing
Public bug reported:
See https://bitbucket.org/cherrypy/cherrypy/issue/1170/bug-in-
check_port-running-python-33 for upstream bug description and patch,
commited in source in 2012 in this commit:
https://bitbucket.org/cherrypy/cherrypy/commits/9820107d4ffb8058fd507888f90e28c695f6b4c0.
Summary:
Public bug reported:
In the /usr/share/doc/awstats/README.Debian.gz file:
if [ -x /usr/share/awstats/tools/update.sh ]; then
su -l -c /usr/share/awstats/tools/update.sh www-data
fi
However this su line gives the following error with Ubuntu 14.04:
This account is currently
I got the same.
Seems to be related to
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1315888 and
upstreams to https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1315888
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in
Sorry for not providing timely feedback there (nor a reproducing env).
Truth is this hasn't recur so marking invalid seems fair.
Thanks for the help nevertheless, if it happens again, I'll make sure to
have such a reproducing env before re-opening this bug.
--
You received this bug
Public bug reported:
and even 'lxc-stop -k -t timeout' can hang :-/
The context is an automated test run with otto using a lxc-container
trigerring a kernel crash on the host.
The host is still alive and so is the container but trying to implement
a catch-all to stop a container left running is
@Serge: I encounter the issue in
http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-
intel/2465/console
which runs on intel. I will try to reproduce locally (this happened in
the ci lab).
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
Hi all,
Since upgrade to Kubuntu 13.04, the suspend-to-ram option doesn't work.
The error reported in the dmesg | grep PM is Device 3:0:0:0 failed to
suspend async: error 134217730
The dmesg log is :
[ 767.677738] PM: Syncing filesystems ... done.
[ 768.725558] PM:
** Attachment added: pm-suspend.log
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1177967/+attachment/3670147/+files/pm-suspend.log
** Package changed: vsftpd (Ubuntu) = ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Hi all,
I compiled the vsftpd package
** Attachment added: vsftpd_3.0.2-1ubuntu1_amd64_patched.deb
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+attachment/3661388/+files/vsftpd_3.0.2-1ubuntu1_amd64_patched.deb
--
You received this bug notification because you are a member
Here is the patched vsftpd version in 32bits arch.
** Attachment added: vsftpd_3.0.2-1ubuntu1_i386_patched.deb
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1160372/+attachment/3661389/+files/vsftpd_3.0.2-1ubuntu1_i386_patched.deb
--
You received this bug notification because you
Hi all,
Previous messages were sent too fast and I didn't find a way to remove them.
I posted the patched version of vsftpd in both 34 and 32 bits arch : please
feel free to download.
Don't forget to remove the previous installed version on your system or dpkg
will tell you that the package is
Note : you need to build on a 64 bits arch to get a 64bits version of the
package and a 32 bits arch for 32bits one.
I used VM for this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
Testing done, the bug is present in 3.8.4
--
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/1157589
Title:
kvm hangs for freebsd guests since raring upgrade
To manage notifications about
Fixed upstream, great. Rough estimate about when this will land for
raring ?
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
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/1157589
Title:
kvm hangs for freebsd guests since raring upgrade
To
** Attachment added: Freebsd9 xml description
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+attachment/3588233/+files/freebsd9.xml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
** Attachment added: vrish capabilities output
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+attachment/3588234/+files/virsh.capabilities
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
As discussed on IRC, doing:
sudo kvm -hda freebsd-8.0-64bits.qcow2 -serial stdio
doesn't trigger the bug, I'll investigate on which part of the xml is causing
the issue and report here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
apport information
** Tags added: apport-collected third-party-packages
** Description changed:
Until I upgraded to raring, freebsd guest has been one of my most stable
guest under kvm (and previously under vbox for that matter).
Since the upgrade to raring, my existing guest hangs
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1157589/+attachment/3588504/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
Public bug reported:
Until I upgraded to raring, freebsd guest has been one of my most stable
guest under kvm (and previously under vbox for that matter).
Since the upgrade to raring, my existing guest hangs very early in the
boot process ending with the following in
It maybe a kernel bug
Dec 9 08:16:07 ealxs00195 kernel: [1723012.226196] BUG: soft lockup - CPU#2
stuck for 23s! [kworker/2:5:1283]
Vincent Chen
EMC2 | E-Lab Linux team
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Ronald
Moesbergen
Sent
i have applied the fix, however the issue still happened :-(
ii kpartx 0.4.9-3ubuntu5+lp1032250dbg1
create device mappings for partitions
ii multipath-tools 0.4.9-3ubuntu5+lp1032250dbg1
maintain multipath block device access
sorry, my mistake. i should have request update on another case.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1030040
Title:
multipath-tools create duplicate device
To
Any update, Peter
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1030040
Title:
multipath-tools create duplicate device
To manage notifications about this bug go to:
@peter
I have change the filter and update into new init ram disk, thanks.
For powerpath issue, i reproduce by shutdown FC switch port. Here is new
complete syslog of whole prodefure and multipath result.
1)multipath_before_port_down -- multipath status before shutdown port
Public bug reported:
when shutdown switch port of host HBA, multippath-tool can't get
correct information of subpath. by check the multipath output, some
storage device type info disapppear and the failed path always stay in
path group and don't be clear out.
mpath2
Here is OS and Packge info also attach log and configuration.
root@Linux51:/var/tmp# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04 LTS
Release:12.04
Codename: precise
root@Linux51:/var/tmp# dpkg -s multipath-tools
Package:
Thanks, peter. Please close this case
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1030040
Title:
multipath-tools create duplicate device
To manage notifications about
** Attachment added: multipath configureation file
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1030040/+attachment/3241572/+files/multipath_conf_2012-07-29164937.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Hi,
I can't reproduce this issue now. It only happen once. As my first
description, i use multipath -f to remove the duplicate device. then
everything is ok.
Here is the log,configuratin file as requested. Due to no duplicated
devices are produced, maybe these log can't help debuging.
**
Public bug reported:
I am testing Ubuntu12.04LTS and find multipath-tools could create
duplicate device on same device.
root@Linux51:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04 LTS
Release:12.04
Codename: precise
Public bug reported:
update will not install
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: clamav-milter 0.97.5+dfsg-1ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu10
Architecture: amd64
Date:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1015828
Title:
package clamav-milter 0.97.5+dfsg-1ubuntu0.12.04.1 failed to
install/upgrade: subprocess installed post-installation
I encounter the same issue while trying to use the same image for juju.
If I use a precise image, cloud-init-output.log ends with:
Installed /usr/lib/juju/juju
Processing dependencies for juju==0.5
Finished processing dependencies for juju==0.5
% Total% Received % Xferd Average Speed
Thanks, guru:-)
Vincent Chen
EMC2 | E-Lab Linux team
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Cruz
Bishop
Sent: Sunday, April 29, 2012 5:49 AM
To: Chen, Vincent
Subject: [Bug 985741] Re: multipath can't show device on which is setup lvm
Yes, Peter, you are right.
After I update initramfs, this issue is resolved.
Thanks for your strong support.
Vincent Chen
EMC2 | E-Lab Linux team
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Peter
Petrakis
Sent: Friday, April 27, 2012 9:54
Ubuntu will have a fix or patch on major release 11?
Vincent Chen
EMC2 | E-Lab Linux team
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of David
Duffey
Sent: Friday, April 27, 2012 3:35 AM
To: Chen, Vincent
Subject: [Bug 985741] Re: multipath can't
Hi
Here is the multipath-tools version
/ Name VersionDescription
+++-==-==-
ii multipath-tool 0.4.9-2ubuntu1 maintain multipath block device access
Vincent Chen
EMC2 | E-Lab Linux team
-Original Message
creation of LVM
And also reboot host.
Vincent Chen
EMC2 | E-Lab Linux team
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of David
Duffey
Sent: Thursday, April 26, 2012 8:47 AM
To: Chen, Vincent
Subject: [Bug 985741] Re: multipath can't show device
Sorry. Miss a test file.
Vincent Chen
EMC2 | E-Lab Linux team
-Original Message-
From: Chen, Vincent
Sent: Thursday, April 26, 2012 12:56 PM
To: 'Bug 985741'
Subject: RE: [Bug 985741] Re: multipath can't show device on which is setup lvm
Hi David
1)What do mean storage module
Public bug reported:
root@SGELLIN119:~# lsb_release -rd
Description:Ubuntu 11.10
Release:11.10
affect package: multipath-tools, lvm2
If creating logical volume with Multipath on disk primary partition 1,
multipath can’t find the
disks. Syslog show such error when booting system
@Adam: Confirmed, using DEBUG produces output \o/
But DEBUG may not be appropriate in the long run ?
Anyway, I'm out of trouble.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
For the record, trying to apply the moral equivalent of the proposed
patch to my config files I still don't get anything written to the log
file :-/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
Public bug reported:
While trying to uninstall keystone (to start from a clean slate),
synaptic complains:
(Reading database ... 304179 files and directories currently installed.)
Removing keystone ...
dpkg: error processing keystone (--remove):
subprocess installed pre-removal script returned
Forget the re-install part, I renamed /etc/keystone while hammering,
restoring its proper name allow the re-installation to complete.
Removing the package is still not possible
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone
@Soren: Sorry for the confusing bug report, keystone-manage is called
while re-installing, not while removing.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/961277
Title:
Cannot
** Changed in: keystone (Ubuntu)
Assignee: (unassigned) = Vincent Ladeuil (vila)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/922954
Title:
keystone has a missing dep
Please re-open this bug as the dependency was added to the wrong
section, see
https://code.launchpad.net/~vila/ubuntu/precise/keystone/fix-922954/+merge/91457
for an hopefully proper fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Hmm,
I have blown this system away.
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Rob
Larson
Sent: Saturday, February 12, 2011 8:44 PM
To: vincent.kressev...@gmail.com
Subject: [Bug 633725] Re: mysql thread_stack parameter too low, causing
got a really ugly fix that make nis finally working... at this to your
/etc/rc.local :
while [ ! `/bin/pidof ypbind` ]
do
/etc/init.d/nis restart
sleep 2
done
exit 0
that should do it!
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You
I've been struggling with this in a brand new 8.10 server myself that I
just setup yesterday. Not sure how or why, but i got this magic
incantation to work (do note however, I'm storing the passwords in
plaintext in mySQL):
Directory /home/dae51d/public_html/examples/crimson
AuthName
SOLVED:
THIS IS STUPID!! The Where clause requires that YOU put an additional
AND in there.
Auth_MySQL_Where AND type = 'Admin' AND enabled = 1
So the auth_mysql code must be making a SELECT * FROM user WHERE
username = 'foo' AND password = 'bar' WHERE 1 or some other
Hi, thanks for your answer
yes autodeploying is just put war file in the appbase dir.
It works witout errors if you don't have a context file to be copied in the
Catalina dir.
but webapp without databases are not very common also you have many cases of
webapps with a database connection using a
Hi,
I confirm this bug.
I had to add the missing jar tomcat-dbcp.jar manually copied from another
tomcat 6.
After adding it was successfully loading datasource settings.
And my webapp is fully working.
To solve the problem waiting for a fix, just get the tomcat-dbcp.jar
from another tomcat 6
Public bug reported:
Binary package hint: tomcat6
Hi,
On ubuntu 8.10, the conf directory for tomcat6 is located in /etc/tomcat6, and
this directory is not writable for tomcat6 user, which one tomcat6 process is
executed under.
Tomcat 6 version is 6.0.18-0ubuntu3
However, if you try to deploy
*** This bug is a duplicate of bug 224945 ***
https://bugs.launchpad.net/bugs/224945
It seems to be fixed now (upgrade of Tue, 13 May 2008 08:46:01).
Thank you, it was the same bug (#224945).
** This bug has been marked a duplicate of bug 224945
[SRU] memory leaks in apache2 when running
80 matches
Mail list logo
