** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Tags added: eucalyptus
--
Instance fail to run
https://bugs.launchpad.net/bugs/429754
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Tags added: eucalyptus
--
Eucalyptus 403 Forbidden when trying to run instance after package upgrade
https://bugs.launchpad.net/bugs/430093
You received this bug notification because you are a member of Ubuntu
Server Team,
** Changed in: qemu-kvm (Ubuntu)
Status: Won't Fix = Confirmed
--
`kvm -name TITLE` option does not set gnome-panel name correctly
https://bugs.launchpad.net/bugs/423076
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
Re-opening this bug as it took me a minute of googling to find what code
change were needed in qemu-kvm. Will attach a patch shortly.
--
`kvm -name TITLE` option does not set gnome-panel name correctly
https://bugs.launchpad.net/bugs/423076
You received this bug notification because you are a
Etienne, could you check the the node controller is running as the
eucalyptus user and that the eucalyptus user is a member of the libvirtd
group? Also, does /var/run/eucalyptus exist on the node controller?
** Changed in: eucalyptus (Ubuntu)
Status: New = Incomplete
--
Instance fail to
Same error on my machine.
it looks like postfix cannot handle a hostname that consists of only numbers
sudo dpkg --configure postfix
Instellen van postfix (2.5.5-1.1) ...
Postfix configuration was not changed. If you need to make changes, edit
/etc/postfix/main.cf (and others) as needed. To
Public bug reported:
Binary package hint: qemu-kvm
= Abstract
The /etc/qemu-ifup script used by `-net tap` seems to have regressed in
0.11.0~rc2-0ubuntu4 and no longer functions correctly on a machine where
it previously worked.
= Description
/etc/qemu-ifup used to hardcode the bridge
I get the blank/black screen after the bios, booting XP vm's i setup on the
same pc a while ago.
Could it be the kernel version ?
--
kvm can not run Windows XP
https://bugs.launchpad.net/bugs/105195
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Does it fail gracefully in the absence of the proxy service?
--
Eucalyptus 'Store' tab requires appliance store proxy package
https://bugs.launchpad.net/bugs/425926
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
** Summary changed:
- snmpd: error getting netmask for interface
+ [SRU] snmpd: error getting netmask for interface
--
[SRU] snmpd: error getting netmask for interface
https://bugs.launchpad.net/bugs/270713
You received this bug notification because you are a member of Ubuntu
Server Team, which
Statement of Impact: The net-snmp version that we are running hardcodes
the /etc/sensors.conf in the source code. However on ubuntu this file is
/etc/sensors3.conf. Users wanting to use lmsensors and net-snmp have to
create a symlink for /etc/sensors.conf.
How this bug has been addresses: This
** Attachment added: 103-fix-ubuntu-lmsensors.patch
http://launchpadlibrarian.net/31898496/103-fix-ubuntu-lmsensors.patch
--
[SRU] Net-SNMP tries to read the obsolete /etc/sensors.conf
https://bugs.launchpad.net/bugs/192745
You received this bug notification because you are a member of
** Summary changed:
- libsnmp-python segmentation fault
+ [SRU] libsnmp-python segmentation fault
** Changed in: net-snmp (Ubuntu Hardy)
Assignee: (unassigned) = Chuck Short (zulcss)
--
[SRU] libsnmp-python segmentation fault
https://bugs.launchpad.net/bugs/347361
You received this bug
** Attachment added: 101-fix-ipalias.patch
http://launchpadlibrarian.net/31899024/101-fix-ipalias.patch
** Changed in: net-snmp (Ubuntu Hardy)
Assignee: (unassigned) = Chuck Short (zulcss)
** Changed in: net-snmp (Ubuntu Intrepid)
Assignee: (unassigned) = Chuck Short (zulcss)
**
Just to get this on record:
Why is layer two tunneling needed? Does EC2 allow direct ethernet
communication between instances? Is that why we're doing it? Or is this
related to AoE?
--
Eucalyptus CC package depends on 'vtund' process in multi-cluster mode
https://bugs.launchpad.net/bugs/425928
statement explaining the impact
Net-snmp in all versions of Ubuntu up until Karmic have this problem.
This is caused by a bug in net-snmp and ip aliasing. When a user tries
to use an interface with the physical interface is unconfigured and an
ip alias is configured for the same interface the
Approved by asac, as per
https://wiki.ubuntu.com/EucalyptusInMainSpec/Packages
** Changed in: jmock (Ubuntu)
Status: Confirmed = Fix Released
--
Main Inclusion Report (Eucalyptus dependencies set 1)
https://bugs.launchpad.net/bugs/405715
You received this bug notification because you are
Approved by doko, as per
https://wiki.ubuntu.com/EucalyptusInMainSpec/Packages
** Changed in: qdox (Ubuntu)
Status: Confirmed = Fix Released
--
Main Inclusion Report (Eucalyptus dependencies set 1)
https://bugs.launchpad.net/bugs/405715
You received this bug notification because you are
Fixed by passing the 'QEMU (NAME)' as the icon_title value to
SDL_WM_SetCaption.
debdiff attached, standalone patch for debian/patches to follow
** Summary changed:
- `kvm -name TITLE` option does not set gnome-panel name correctly
+ [patch] `kvm -name TITLE` option does not set gnome-panel
debian/patches/06_improve-qemu-sdl-title.patch
** Attachment added: 06_improve-qemu-sdl-title.patch
http://launchpadlibrarian.net/31899293/06_improve-qemu-sdl-title.patch
--
[patch] `kvm -name TITLE` option does not set gnome-panel name correctly
https://bugs.launchpad.net/bugs/423076
You
built and installed the pkg locally and found to be working as desired
have also uploaded to my ppa
--
[patch] `kvm -name TITLE` option does not set gnome-panel name correctly
https://bugs.launchpad.net/bugs/423076
You received this bug notification because you are a member of Ubuntu
Server
Statement of Impact
The python bindings for net-snmp shipped with a bug that can cause a
segmentation fault when a user tries to run a python script.
How this bug has been fixed
net-snmp has a patch in their SVN tree which addresses this issue (http
It does. It should just display a message saying that the proxy is not
available.
That said, considering it has so few dependencies by itself, it'd be
good to have the Eucalyptus package depending on the Image Store Proxy
package, so that people will benefit from the service without having to
Statement of Impact:
Users trying to use NetSNMP::agent are unable to do so because Counter64
is broken.
How the bug has been addressed:
This bug has been addressed in the SVN tree for net-snmp (http://net-
snmp.svn.sourceforge.net/viewvc/net-snmp/branches/V5-4-patches/net-
Public bug reported:
Binary package hint: freeradius
freeradius refuses to start without the freeradius-mysql package being
installed:
From the output of freeradius -X:
{snip}
including configuration file /etc/freeradius/modules/acct_unique
including configuration file
Public bug reported:
Binary package hint: freeradius
The radclient tool in freeradius doesn't work:
# radtest testuser testpass localhost 10 testing123
radclient: socket: cannot initialize udpfromto: Function not implemented
** Affects: freeradius (Ubuntu)
Importance: Undecided
This is an issue in intrepid, jaunty and karmic.
--
freeradius config needs freeradius-mysql
https://bugs.launchpad.net/bugs/430730
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in ubuntu.
--
Ubuntu-server-bugs mailing list
This affects jaunty and karmic.
Intrepid is ok.
--
radclient doesn't work
https://bugs.launchpad.net/bugs/430732
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in ubuntu.
--
Ubuntu-server-bugs mailing list
This is still broken in Intrepid.
--
freeradius init script not consistent with radiusd.conf
https://bugs.launchpad.net/bugs/367769
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in ubuntu.
--
Ubuntu-server-bugs mailing list
Ok, after playing around with this, I'm getting there. I want to
document this here, so at least others and even myself can benefit from
this in the future. I added this line: options lockd nlm_udpport=4045
nlm_tcpport=4045to /etc/modprobe.d/options.conf the port number
can really be
Ok, after playing around with this, I'm getting there. I want to
document this here, so at least others and even myself can benefit from
this in the future. I added this line: options lockd nlm_udpport=4045
nlm_tcpport=4045to /etc/modprobe.d/options.conf the port number
can really be
Public bug reported:
Using the Cloud Installer option on the server CD, cluster mode, after reboot
the system hangs at:
Enabling IP forwarding * Restarting OpenBSD Secure Shell server sshd
Logging in via ssh, it appears /etc/init.d/eucalyptus-cc is stuck in a loop.
Which is not that
Confirming, I'm seeing the same thing from a fresh install on real
hardware.
:-Dustin
** Changed in: eucalyptus (Ubuntu)
Status: New = Confirmed
--
Cloud installer / Cluster install hangs at reboot after install
https://bugs.launchpad.net/bugs/430758
You received this bug notification
My testing on EC2 suggests that direct ethernet communication across
availability zone boundaries is not possible. For the record, I added an
extra IP address (192.168.10.1 and .2) to eth0 on each host, and added
an arp entry for the other host on each of them, and tried to ping. No
luck.
--
** Changed in: qemu-kvm (Ubuntu)
Status: New = Triaged
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Low
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
/etc/qemu-ifdown is being installed without execute permissions
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Triaged
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
[patch] `kvm -name TITLE` option does not set gnome-panel name correctly
https://bugs.launchpad.net/bugs/423076
You received this bug
Proposed patch
** Attachment added: patch
http://launchpadlibrarian.net/31904061/patch
--
Cloud installer / Cluster install hangs at reboot after install
https://bugs.launchpad.net/bugs/430758
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Changing 8773 to 8774 in all initscripts fixes this.
This is only a first-boot issue, since CLOUD_PORT gets defined afterwards.
Adding VERBOSE=yes at the top of the initscripts restores the missing
start/stop messages at boot.
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed =
My proposal [1] is to have eucalyptus-cloud recommend python-image-
proxy-store.
[1]: https://code.launchpad.net/~mathiaz/eucalyptus/image-store-proxy-
recommends
** Branch linked: lp:~mathiaz/eucalyptus/image-store-proxy-recommends
--
Eucalyptus 'Store' tab requires appliance store proxy
You have been subscribed to a public bug:
The first thing I did was trying to install lamp server like below:
sudo tasksel install lamp-server. Then I entered the root password for mysql,
after few mins the installation stopped at 72%(for very long time), It didn't
recover at all. So I just
Looks like mysql-server package failed to installed. Assigning it to
mysq-dfsg-5.0 pacakge.
** Summary changed:
- Unable to get exclusive lock
+ mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade
** Package changed: ubuntu = mysql-dfsg-5.0 (Ubuntu)
--
mysql-server-5.0
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I can see two errors:
Setting up mysql-server-5.0 (5.1.30really5.0.75-0ubuntu10.2) ...
* Stopping MySQL database server mysqld
...done.
* Reloading AppArmor profiles ...
...done.
*
Public bug reported:
Binary package hint: bind9
i had this problem when i was upgrding from ubuntu 9.04 to ubuntu 9.10
ProblemType: Package
Architecture: amd64
Date: Tue Sep 15 12:41:42 2009
DistroRelease: Ubuntu 9.10
ErrorMessage:
ErrorMessage: sub-processo installed post-installation script
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/31905270/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/31905271/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
** Attachment added: questions.dat
http://launchpadlibrarian.net/31905201/questions.dat
** Changed in: eucalyptus (Ubuntu)
Status: New = Triaged
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Importance: Medium = High
--
Public bug reported:
Fresh install of eucalyptus-node, /etc/network interfaces looks like
this:
===
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network
I found this while searching the mountd man pages:
-P portnum or --port portnum
Makes mountd listen on port portnum instead of some random port.
By default, mountd will listen on the mount/udp port specified
in /etc/services, or, if that is
Public bug reported:
The eucalyptus-cloud, -walrus, and -sc services all run as web services
under the same process if installed on the same machine. The init
scripts, upon 'start', check if the web service file exists, and the
process is running; if both are true, the init script does nothing
Public bug reported:
The eucalyptus init scripts check for the number of loop devices, which
is set to 8 in Ubuntu.
Eucalyptus requests 32 loop devices for for mounting the root filesystem
to inject credentials. the storage controller uses it for volumes. you
run out pretty quick with the
Marking won't fix against the kernel since this can and should be
configured in user space.
:-Dustin
--
eucalyptus politely requests 32 loop devices
https://bugs.launchpad.net/bugs/430846
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
ok got it. I put up a small how-to here:
http://ubuntuforums.org/showpost.php?p=7959294postcount=17
Hope this helps.
Shane
--
need way to specify the lockd port
https://bugs.launchpad.net/bugs/28706
You received this bug notification because you are a member of Ubuntu
Server Team, which is a
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
--
eucalyptus politely requests 32 loop devices
https://bugs.launchpad.net/bugs/430846
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
Excellent post! Thanks for making the how-to, Shane. You may want to
consider posting this to the Ubuntu wiki, with a title something like,
Making NFS work with Ubuntu-CE-Firewall. That would make it a little
easier to find.
--
need way to specify the lockd port
You will also want to make eth0 manual (iface eth0 inet manual),
otherwise both the bridge and eth0 will get an IP, making the routing
table funny.
--
eucalyptus node install results in broken /etc/network/interfaces
https://bugs.launchpad.net/bugs/430820
You received this bug notification
Public bug reported:
Every other (sometimes third) time, euca/ec2 describe volumes/snapshots
will hang.
** Affects: eucalyptus
Importance: Undecided
Status: New
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:eucalyptus/1.6
**
revno: 764
committer: Neil
branch nick: 1.6
timestamp: Wed 2009-09-16 10:47:56 -0700
message:
fixes #430888
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Ideally, I think netcfg should make sure that netcfg/choose_interface is
always set even if there's only one interface. Still, we can work around
this in eucalyptus-udeb.
** Also affects: netcfg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcfg (Ubuntu)
Importance:
Etienne, can you file a separate bug about setting eth0 to manual, with
more details? Dustin says he didn't have to do that and is routing table
looks OK, so maybe this is a more isolated problem.
--
eucalyptus node install results in broken /etc/network/interfaces
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
--
eucalyptus node install results in broken /etc/network/interfaces
https://bugs.launchpad.net/bugs/430820
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
eucalyptus node install results in broken /etc/network/interfaces
https://bugs.launchpad.net/bugs/430820
You received this bug
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = Fix Committed
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: Gustavo Niemeyer (niemeyer) = Mathias Gug (mathiaz)
--
Eucalyptus 'Store' tab requires appliance store proxy package
https://bugs.launchpad.net/bugs/425926
This bug was fixed in the package eucalyptus - 1.6~bzr746-0ubuntu3
---
eucalyptus (1.6~bzr746-0ubuntu3) karmic; urgency=low
[ Dustin Kirkland ]
* tools/eucalyptus-nc.in: Create the suggested 32 loop devices using
mknod in the init script, perm'd 660, owned by root:disk, LP:
This bug was fixed in the package eucalyptus - 1.6~bzr746-0ubuntu3
---
eucalyptus (1.6~bzr746-0ubuntu3) karmic; urgency=low
[ Dustin Kirkland ]
* tools/eucalyptus-nc.in: Create the suggested 32 loop devices using
mknod in the init script, perm'd 660, owned by root:disk, LP:
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Status: New = Triaged
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = New
** Changed in: eucalyptus (Ubuntu)
Milestone: None = ubuntu-9.10-beta
--
after package
I think having 'start' restart the process if it isn't already providing
the necessary service would be reasonable enough.
I filed a separate bug about how the init scripts work recently, but
even then, presumably you'd still have to restart the frontend to get it
to run an additional service.
** Description changed:
Binary package hint: php5
Code that worked great on another server causes segfaults on a freshly
installed Gutsy 64-bit server
ProblemType: Crash
Architecture: amd64
Date: Tue Dec 18 18:08:58 2007
DistroRelease: Ubuntu 7.10
ExecutablePath:
Colin, for me on jaunty, the following /etc/network/interfaces result in
a system with broken network (ie, cannot ping or connect to anything):
---
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
** Description changed:
Binary package hint: totem
Occurred when system rebooted after installing Hardy Heron Beta.
ProblemType: Crash
Architecture: amd64
Date: Mon Mar 24 09:28:36 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/totem-xine-video-indexer
** Description changed:
Binary package hint: bacula-console-qt
I use BAT to connect to my bacula director via SSH Port forward.
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Apr 3 15:58:16 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/bat
Unfortunately, I had to revert back to 1.5 for a specific project, and I
do not have the hardware to run two clusters in parallel (a stable one
on jaunty/1.5, and one for testing on karmic/1.6). I will not be able
to test any earlier than late next week. Sorry! :(
--
Instance fail to run
Public bug reported:
the eucalyptus init scripts create the:
/var/run/eucalyptus/*
directory(ies) on start, but do not correctly change the ownership of
the created directory(ies). The init scripts (for example eucalyptus-
cc) call /usr/sbin/euca_conf -check cc on startup:
if [ ! -d
I believe that there are two problems here; first, the latest
apparmor/libvirt is preventing the NC from being able to start VMs:
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/431090
second, the 'nc-stat' error is caused by /var/run/eucalyptus directories
are not getting the right
** Description changed:
Binary package hint: samba
executing smbmount
ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /sbin/mount.cifs
MediaBuild: Ubuntu 9.04 Jaunty Jackalope - Release amd64 (20090420.1)
Package: smbfs 2:3.3.2-1ubuntu3
I believe that Etienne is correct.
Upon installation of the Node Controller, my networking was broken until
I configured eth0 to manual, while leaving br0 to dhcp. I did, in
fact, draw a dhcp address.
I'm fixing this with the following in debian/eucalyptus-udeb.finish-
install:
+ sed -i
74 matches
Mail list logo
