So the same deadlock issue was hit again:
root 1378 1 0 1031 560 0 17:28 ?00:00:00
/lib/udev/watershed sh -c /sbin/lvm vgscan; /sbin/lvm vgchange -a y
root 1379 1378 0 1055 588 0 17:28 ?00:00:00 sh -c /sbin/lvm
vgscan; /sbin/lvm vgchange -a y
root
Reinstalling fixes the issue on Maverick, but not fully tested on 11.04,
which could be a different issue.
--
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/765275
Title:
metadata
Reinstalling fixes the issue on Maverick, but not fully tested on 11.04,
which could be a different issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/765275
Title:
metadata server cannot be
Hi,
Not sure which bug to comment, but seeing the exact same issue here with
nfs-common 1:1.2.2-1ubuntu1.1 on Ubuntu 10.10. Was this bug re-
introduced somehow?
Setting up nfs-common (1:1.2.2-1ubuntu1.1) ...
statd start/running, process 15149
start: Unknown job: gssd
invoke-rc.d: initscript
Hi Steve,
Thanks for the quick answer. /etc/init/gssd.conf is present and
untouched as far as I am aware.
wc -l /etc/init/gssd.conf
70 /etc/init/gssd.conf
md5sum /etc/init/gssd.conf
Steve,
Forget it, start on and stop on were commented, removed the comments
and a sudo dpkg --configure -a sorted the machine. Sorry for the
noise, fix released it is ;-)
Thanks again !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I am curious to know if anything special was used when on EXT4?
(specific options when mounting or did you use default options?)
--
kernel panic with 'rejecting i/o to offline device'
https://bugs.launchpad.net/bugs/665163
You received this bug notification because you are a member of Ubuntu
Apparently pcie_aspm=off as a kernel parameter fixes the issue. Not sure what
this implies regarding PM.
From : https://bugzilla.redhat.com/show_bug.cgi?id=538920#c78
Trying to reproduce here. Will report back.
--
NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Torsten,
Possibly related to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/259028
( upstream https://bugzilla.gnome.org/show_bug.cgi?id=594085 )
Seems we might need the usb_modeswitch udev helper to run on wake up
from suspend.
Hope this helps,
** Bug watch added: GNOME
Public bug reported:
Binary package hint: upstart
Steps to reproduce:
Install Ubuntu 10.04 LTS, install apache and apache ssl, create a certificate
for SSL, protect the certificate with a passphrase.
Reboot the machine.
Results:
Graphical console (Plymouth) display a password entry field ...
Thanks Yannick for your comments, we will be trying and reporting as
indicated asap.
--
Ekiga crashes during incoming and outgoing SIP calls when registered with Cisco
CM
https://bugs.launchpad.net/bugs/563698
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As far as the new package containing the eucalyptus-interface jar file,
this is verified, and also fixes this escalation bug (package respin).
--
Missing jar file when Walrus/S3 runs on different host than CLC
https://bugs.launchpad.net/bugs/516083
You received this bug notification because you
As far as the new package containing the eucalyptus-interface jar file,
this is verified, and also fixes this escalation bug (package respin).
--
Missing jar file when Walrus/S3 runs on different host than CLC
https://bugs.launchpad.net/bugs/516083
You received this bug notification because you
Agreed for Karmic.
It was mainly filed to make sure we test the most common and rapid way
to 'try' UEC which is to download and launch the 'default' image from
the store, and run it in the default instance size.
Is 192 meg a requisite for current uec lucid images?
--
default karmic image from
Agreed for Karmic.
It was mainly filed to make sure we test the most common and rapid way
to 'try' UEC which is to download and launch the 'default' image from
the store, and run it in the default instance size.
Is 192 meg a requisite for current uec lucid images?
--
default karmic image from
Ok, Verified and confirmed fixing.
I effectively get the right hostname without even a reboot.
Thanks !!
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are
Public bug reported:
When creating users in the WebUI, there is no way to remove those users.
Only an edit button, but i cluld not find any way to deactivate or remove an
user.
Reproducable: Always
Steps:
Install UEC, connect to the web management interface (https:/IP:8443/) and
create many
Indeed, this solves it.
Thank you very much.
--
Cannot remove UEC/Eucalyptus users from webUI
https://bugs.launchpad.net/bugs/532700
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing
Ok, Verified and confirmed fixing.
I effectively get the right hostname without even a reboot.
Thanks !!
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are
Public bug reported:
When creating users in the WebUI, there is no way to remove those users.
Only an edit button, but i cluld not find any way to deactivate or remove an
user.
Reproducable: Always
Steps:
Install UEC, connect to the web management interface (https:/IP:8443/) and
create many
Indeed, this solves it.
Thank you very much.
--
Cannot remove UEC/Eucalyptus users from webUI
https://bugs.launchpad.net/bugs/532700
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
euca-run-instances emi-DFE5107D is the command line, after sourcing the
.euca/eucarc file.
The entity testing is only plainly following the docs there:
https://help.ubuntu.com/community/UEC/CDInstall
(Specifically Chapter 7)
apart that he omitted the -t c1.medium (which, funnily, does not run
Mathias Gug wrote:
On Wed, Mar 03, 2010 at 11:45:13AM -, Boris Devouge wrote:
euca-run-instances emi-DFE5107D is the command line, after sourcing the
.euca/eucarc file.
Could add the command line used to register the image (emi-DFE5107D)?
This the image from the image-proxy-store
euca-run-instances emi-DFE5107D is the command line, after sourcing the
.euca/eucarc file.
The entity testing is only plainly following the docs there:
https://help.ubuntu.com/community/UEC/CDInstall
(Specifically Chapter 7)
apart that he omitted the -t c1.medium (which, funnily, does not run
Mathias Gug wrote:
On Wed, Mar 03, 2010 at 11:45:13AM -, Boris Devouge wrote:
euca-run-instances emi-DFE5107D is the command line, after sourcing the
.euca/eucarc file.
Could add the command line used to register the image (emi-DFE5107D)?
This the image from the image-proxy-store
Public bug reported:
This bug does not present a good initial experience to UEC new commers:
- When running the first instance, downloading the default Ubuntu 9.10
image from the Image Proxy, and try to simply launch it with all default
settings, fails to run the instance.
It seems the disk
Public bug reported:
This bug does not present a good initial experience to UEC new commers:
- When running the first instance, downloading the default Ubuntu 9.10
image from the Image Proxy, and try to simply launch it with all default
settings, fails to run the instance.
It seems the disk
Thanks Dustin. I hope to be able to get hardware for a Lucid cloud soon,
in the meantime i have not reproduced it yet, but i have verified as you
have that eucalyptus-interface-1.6.2.jar is indeed packaged in
eucalyptus-java-common_1.6.2.
As for Karmic, this is only about repackaging
Thanks Dustin. I hope to be able to get hardware for a Lucid cloud soon,
in the meantime i have not reproduced it yet, but i have verified as you
have that eucalyptus-interface-1.6.2.jar is indeed packaged in
eucalyptus-java-common_1.6.2.
As for Karmic, this is only about repackaging
Public bug reported:
Grub2 (grub-pc) fails when installing on a KVM virtual machine running
virtio disks.
The disk appears as /dev/vda and it seems the installer tries against
/dev/sda and /dev/hda, fails to find the disk, and proposes to continue
without a bootloader.
Step to reproduce:
-
Public bug reported:
Started with a 9.10 karmic fully updated as of yesterday UEC working
install, with one CLC/CC/SC and 2 NCs.
I proceed as follow:
- ssh in the NCs and stopped eucalyptus related services.
- ssh in the CLC and did the same
- updated my sources.list to lucid on all machines
** Attachment added: euca-debug.log
http://launchpadlibrarian.net/38944263/euca-debug.log
--
UEC upgrade from 9.10 karmic to Lucid fails
https://bugs.launchpad.net/bugs/519513
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus
Version info (after upgrade)
=
ii eucalyptus-cc1.6~bzr931-0ubuntu7.4
ii eucalyptus-cloud 1.6~bzr931-0ubuntu7.4
ii eucalyptus-common 1.6~bzr931-0ubuntu7.4
As additional comment, we understand Lucid is moving target, so the
importance of this bug should be well diminished as the upgrade will
need retesting with final lucid release.
--
UEC upgrade from 9.10 karmic to Lucid fails
https://bugs.launchpad.net/bugs/519513
You received this bug
I did not thought the 'do-release-upgrade -d' method worked until we
release Lucid, or does it? Do you think it could have avoided the
breakage?
--
UEC upgrade from 9.10 karmic to Lucid fails
https://bugs.launchpad.net/bugs/519513
You received this bug notification because you are a member of
Public bug reported:
Started with a 9.10 karmic fully updated as of yesterday UEC working
install, with one CLC/CC/SC and 2 NCs.
I proceed as follow:
- ssh in the NCs and stopped eucalyptus related services.
- ssh in the CLC and did the same
- updated my sources.list to lucid on all machines
** Attachment added: euca-debug.log
http://launchpadlibrarian.net/38944263/euca-debug.log
--
UEC upgrade from 9.10 karmic to Lucid fails
https://bugs.launchpad.net/bugs/519513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Version info (after upgrade)
=
ii eucalyptus-cc1.6~bzr931-0ubuntu7.4
ii eucalyptus-cloud 1.6~bzr931-0ubuntu7.4
ii eucalyptus-common 1.6~bzr931-0ubuntu7.4
As additional comment, we understand Lucid is moving target, so the
importance of this bug should be well diminished as the upgrade will
need retesting with final lucid release.
--
UEC upgrade from 9.10 karmic to Lucid fails
https://bugs.launchpad.net/bugs/519513
You received this bug
I did not thought the 'do-release-upgrade -d' method worked until we
release Lucid, or does it? Do you think it could have avoided the
breakage?
--
UEC upgrade from 9.10 karmic to Lucid fails
https://bugs.launchpad.net/bugs/519513
You received this bug notification because you are a member of
Dustin,
Which version of UEC are you using? Not managed to get internal DNS
working here (up2date 9.10 UEC). Cheers.
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification
Dustin,
Which version of UEC are you using? Not managed to get internal DNS
working here (up2date 9.10 UEC). Cheers.
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification
Public bug reported:
Please see initial issue reported here:
http://open.eucalyptus.com/forum/walrus-configuration-failed-contact-
server
When running Walrus/S3 services of a different machine than the Cloud
controller (CLC), we are missing some jar files. We seems to assume that the
Sorry, this is fully updated Ubuntu 9.10 amd64 as of 01 Feb 2010.
--
Missing jar file when Walrus/S3 runs on different host than CLC
https://bugs.launchpad.net/bugs/516083
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Thanks for all comment and explanations for the DNS services of
eucalyptus, however it is not accepted/possible in all cases, and not
the whole issue.
There is still an issue where we do not get an full IP attributed as a
hostname (which would help already assuming the uniqueness of hostnames
and
To be clear, i understand Eucalytus has a mapping as described in the
url Dan Nurmi provided, but i am trying to understand if it is the job
of UEC to assign a proper hostname to its instances (even when DNS is
missing), or if it sole responsibility is to launch the instances, even
if they all end
Public bug reported:
Please see initial issue reported here:
http://open.eucalyptus.com/forum/walrus-configuration-failed-contact-
server
When running Walrus/S3 services of a different machine than the Cloud
controller (CLC), we are missing some jar files. We seems to assume that the
Sorry, this is fully updated Ubuntu 9.10 amd64 as of 01 Feb 2010.
--
Missing jar file when Walrus/S3 runs on different host than CLC
https://bugs.launchpad.net/bugs/516083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Thanks for all comment and explanations for the DNS services of
eucalyptus, however it is not accepted/possible in all cases, and not
the whole issue.
There is still an issue where we do not get an full IP attributed as a
hostname (which would help already assuming the uniqueness of hostnames
and
To be clear, i understand Eucalytus has a mapping as described in the
url Dan Nurmi provided, but i am trying to understand if it is the job
of UEC to assign a proper hostname to its instances (even when DNS is
missing), or if it sole responsibility is to launch the instances, even
if they all end
I am affected by this and have a 50 % failure rate (or success rate) ar
running images. One out of 2 of my launched instances from my 'custom'
image exhibits the same issue.
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification because you
This also badly breaks JBoss. I am not sure this is specific to Jboss,
as other java app servers will also most likely grab the wrong hostname.
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data
https://bugs.launchpad.net/bugs/475354
You received this
I am affected by this and have a 50 % failure rate (or success rate) ar
running images. One out of 2 of my launched instances from my 'custom'
image exhibits the same issue.
--
Official UEC image fails to boot
https://bugs.launchpad.net/bugs/464418
You received this bug notification because you
This also badly breaks JBoss. I am not sure this is specific to Jboss,
as other java app servers will also most likely grab the wrong hostname.
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data
https://bugs.launchpad.net/bugs/475354
You received this
As suggested, tried editing /etc/ec2-init/templates/hosts.tmpl and
replacing the $hostname var with a fixed value (ubuntu), rebundling and
restarted the instance still landed me in a shell: ubu...@172
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data
ubu...@172:~$ cat /etc/ec2-init/templates/hosts.tmpl
127.0.0.1 localhost
127.0.1.1 ubuntu
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
As suggested, tried editing /etc/ec2-init/templates/hosts.tmpl and
replacing the $hostname var with a fixed value (ubuntu), rebundling and
restarted the instance still landed me in a shell: ubu...@172
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data
ubu...@172:~$ cat /etc/ec2-init/templates/hosts.tmpl
127.0.0.1 localhost
127.0.1.1 ubuntu
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
But this is Java ... not really directly relating to debian packages policies,
no?
Majority of java apps (read enterprise software) require it to be set, and it
will be nice that something like update-alternatives or some other mechanism
takes care of it, or is this totally out of scope?
--
It seems turning off AA makes the 'drag and drop' of slides fast and non
blocking, could we please ship OO.org by default with AA turn off until we find
out the real issue?
It will really improve the 'initial' experience and impressions of the users.
--
[upstream] OpenOffice.org 3.1 Impress
This bug (along with the one moving slides order in the slide sorter)
makes OpenOffice very frustrating to use.
This happening on amd64 / x86_64 machine, 4 gigs ram, 2 months old,
running fully up2date Karmic 9.10.
Happy to provide more info and test anything possible.
--
[upstream] OOImpress,
Autofs5 was created as it originally allowed to remove a limitation of
the numbers of anonymous bind against ldap one could do with autofs4.
The rationale of this MIR is that majority of customers will set up
autofs5 rather than 4, and that in 9.04 Jaunty we had a situation where
autofs4 was in
SRU:
https://wiki.ubuntu.com/StableReleaseUpdates
--
PKCS#11 signing does not work
https://bugs.launchpad.net/bugs/495410
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Any news on this issue?
--
NSS using LDAP on Karmic breaks 'su' and 'sudo'
https://bugs.launchpad.net/bugs/423252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
My experience on fully updated karmic amd64 kvm host:
- an ubuntu 8.04 LTS i386 guest crashes constantly (VM simply goes *poof* and
disappears after 5 to 10 minutes uptime)
- 9.10 amd64 guest lives
Now what is interesting relating to the 'acpi' suggested cause is:
- All 2 guests have acpi/
#63, you missed ~rtg/ dir in the second url. Thank very much, testing it
now.
--
agpgart-intel not loaded before drm sometimes, causes KMS to fail
https://bugs.launchpad.net/bugs/430694
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
on 2.6.31-12-generic #39:
5 reboots, 3 black screens after GDM login. When it works, its accelerated and
fast, and displays this in the logs:
[8.270350] agpgart-intel :00:00.0: Intel Mobile Intel® GM45 Express
Chipset
[8.272230] agpgart-intel :00:00.0: detected 32764K stolen
This works for KMS here, however GDM and booting into gnome is slow,
giving me an load average of 2.85 right after finishing to load gnome.
in gnome glxinfo shows it is using hw rendering. and the desktop is
snappy again. I cat'd the 2 files requested in one attachment.
** Attachment added:
autofs5 on jaunty, and we have not managed specific
reproduction of this issue.
I have a call scheduled with the customer tomorrow at 18.00BST/10.00PST
to find out more details.
--
Boris Devouge boris.devo...@canonical.com
Sales Engineer +44 (0)20 7630 2476
Canonical
--
autofs5
Private bug reported:
Binary package hint: autofs5
Ubuntu release: Jaunty x86_64 Server, fully up2date as of 12/06/2009
apt-cache policy autofs5
autofs5:
Installed: 5.0.3-3
Candidate: 5.0.3-3
Version table:
*** 5.0.3-3 0
500 http://ubuntu-repo.XX jaunty/universe Packages
** Attachment added: core
http://launchpadlibrarian.net/27812882/core
** Visibility changed to: Private
--
autofs5 segfaults in Jaunty x86_64
https://bugs.launchpad.net/bugs/386268
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
LDAP server is Sun One Directory Server.
--
autofs5 segfaults in Jaunty x86_64
https://bugs.launchpad.net/bugs/386268
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Release: Jaunty
autofs does not seems to exit cleanly on Jaunty.
After users log on the system, /proc/mounts is not being cleared, and a
segfault is shown in the system logs:
[ 5839.284941] automount[19289]: segfault at 7fbf078cdd90 ip
7fbf078cdd90 sp 7fbf037e1118
Customer has provided the following auto_master entries from LDAP
(attached).
Novell provided a new autofs with the following changelog that has fixed
the issue:
Distribution: home:cseader:autofs5 / SLE_10\
\
Changelog:\
\
* Tue Apr 14 2009 - csea...@novell.com\
- PTF for bug #410450\
74 matches
Mail list logo
