[Bug 437058] Re: Walrus, SC and CC registrations hardcode 'localhost'
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu -- Walrus, SC and CC registrations hardcode 'localhost' https://bugs.launchpad.net/bugs/437058 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 438602] Re: Autoregistration of eucalyptus-cc sometimes fails
I've made some progress, and autoregistration is now succeeding for me. I had to ditch the localhost registrations, and use a real IP address. I pulled that functionality into a single place, that can be sourced by each upstart file. As of 1am, this is working for me. I'm uploading now, and will poke admins about accepting the package and pushing another ISO build. :-Dustin ** Changed in: eucalyptus (Ubuntu Karmic) Status: In Progress = Fix Committed ** Changed in: upstart (Ubuntu Karmic) Status: New = Incomplete -- Autoregistration of eucalyptus-cc sometimes fails https://bugs.launchpad.net/bugs/438602 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439161] Re: console.log not working
This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu13 --- eucalyptus (1.6~bzr854-0ubuntu13) karmic; urgency=low * eucalyptus-common.eucalyptus.upstart: the -L option was in the wrong place, breaking the console.log logging, LP: #439161 * eucalyptus-cc.eucalyptus-cc-registration.upstart, eucalyptus-cc.upstart, eucalyptus-cloud.upstart, eucalyptus-ipaddr.conf, eucalyptus-common.install, eucalyptus-sc.eucalyptus-sc-registration.upstart, eucalyptus-sc.upstart, eucalyptus-walrus.upstart: using localhost is breaking registration; instead, use the real, external ip address; consolidate the (nasty) logic for determining this into a single, sourcable, overridable location, LP: #437058, #438602 * 80-eucalyptus-url: use the new $CLOUD_IP_ADDR value and logic -- Dustin Kirkland kirkl...@ubuntu.com Wed, 30 Sep 2009 01:16:12 -0500 ** Changed in: eucalyptus (Ubuntu) Status: Fix Committed = Fix Released -- console.log not working https://bugs.launchpad.net/bugs/439161 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 437058] Re: Walrus, SC and CC registrations hardcode 'localhost'
This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu13 --- eucalyptus (1.6~bzr854-0ubuntu13) karmic; urgency=low * eucalyptus-common.eucalyptus.upstart: the -L option was in the wrong place, breaking the console.log logging, LP: #439161 * eucalyptus-cc.eucalyptus-cc-registration.upstart, eucalyptus-cc.upstart, eucalyptus-cloud.upstart, eucalyptus-ipaddr.conf, eucalyptus-common.install, eucalyptus-sc.eucalyptus-sc-registration.upstart, eucalyptus-sc.upstart, eucalyptus-walrus.upstart: using localhost is breaking registration; instead, use the real, external ip address; consolidate the (nasty) logic for determining this into a single, sourcable, overridable location, LP: #437058, #438602 * 80-eucalyptus-url: use the new $CLOUD_IP_ADDR value and logic -- Dustin Kirkland kirkl...@ubuntu.com Wed, 30 Sep 2009 01:16:12 -0500 ** Changed in: eucalyptus (Ubuntu) Status: Fix Committed = Fix Released -- Walrus, SC and CC registrations hardcode 'localhost' https://bugs.launchpad.net/bugs/437058 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 438602] Re: Autoregistration of eucalyptus-cc sometimes fails
This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu13 --- eucalyptus (1.6~bzr854-0ubuntu13) karmic; urgency=low * eucalyptus-common.eucalyptus.upstart: the -L option was in the wrong place, breaking the console.log logging, LP: #439161 * eucalyptus-cc.eucalyptus-cc-registration.upstart, eucalyptus-cc.upstart, eucalyptus-cloud.upstart, eucalyptus-ipaddr.conf, eucalyptus-common.install, eucalyptus-sc.eucalyptus-sc-registration.upstart, eucalyptus-sc.upstart, eucalyptus-walrus.upstart: using localhost is breaking registration; instead, use the real, external ip address; consolidate the (nasty) logic for determining this into a single, sourcable, overridable location, LP: #437058, #438602 * 80-eucalyptus-url: use the new $CLOUD_IP_ADDR value and logic -- Dustin Kirkland kirkl...@ubuntu.com Wed, 30 Sep 2009 01:16:12 -0500 ** Changed in: eucalyptus (Ubuntu Karmic) Status: Fix Committed = Fix Released -- Autoregistration of eucalyptus-cc sometimes fails https://bugs.launchpad.net/bugs/438602 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439251] [NEW] Eucalyptus restart is needed after autoregistration of components
Public bug reported: Eucalyptus as of 1.6~bzr854-0ubuntu13 autoregisters components. However those registered components are not put in use by the cloud webservice until it is restarted. So after installation you need to run: $ sudo stop eucalyptus $ sudo start eucalyptus before making use of the cloud. ** Affects: eucalyptus (Ubuntu) Importance: High Status: Triaged ** Changed in: eucalyptus (Ubuntu) Importance: Undecided = High ** Changed in: eucalyptus (Ubuntu) Status: New = Triaged -- Eucalyptus restart is needed after autoregistration of components https://bugs.launchpad.net/bugs/439251 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439288] [NEW] 1.6~bzr854-0ubuntu13 fails to run instances
Public bug reported: When starting up an instance on 1.6~bzr854-0ubuntu13, it fails to run on the NC. nc.log shows: [EUCAINFO ] retrieving images for instance i-5BA00998 (disk limit=20480MB)... [EUCAINFO ] walrus_request(): downloading /var/lib/eucalyptus/instances/admin/i-5BA00998/kernel-digest [EUCAINFO ] from http://127.0.0.1:8773/services/Walrus/ueckernel/vmlinuz-2.6.31-11-generic.manifest.xml [EUCADEBUG ] walrus_request(): writing GET output to /var/lib/eucalyptus/instances/admin/i-5BA00998/kernel-digest [EUCADEBUG ] walrus_request(): wrote 0 bytes in 0 writes [EUCAERROR ] walrus_request(): couldn't connect to host (7) For some reasons it believes it should connect to 127.0.0.1 to retrieve things. Cluster is apparently correctly registered with external IP addresses... I couldn't find an easy workaround. I'm considering reverting beta candidate to 20090930. ** Affects: eucalyptus (Ubuntu) Importance: High Status: New ** Affects: eucalyptus (Ubuntu Karmic) Importance: High Status: New ** Changed in: eucalyptus (Ubuntu) Importance: Undecided = High ** Changed in: eucalyptus (Ubuntu) Milestone: None = ubuntu-9.10-beta ** Also affects: eucalyptus (Ubuntu Karmic) Importance: High Status: New -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439315] [NEW] package postfix 2.5.5-1.1 failed to install/upgrade: subprocess post-installation script returned error exit status 75
Public bug reported: Binary package hint: postfix n/a ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 9.04 ErrorMessage: subprocess post-installation script returned error exit status 75 Package: postfix 2.5.5-1.1 SourcePackage: postfix Title: package postfix 2.5.5-1.1 failed to install/upgrade: subprocess post-installation script returned error exit status 75 Uname: Linux 2.6.28-15-generic i686 ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package postfix 2.5.5-1.1 failed to install/upgrade: subprocess post-installation script returned error exit status 75 https://bugs.launchpad.net/bugs/439315 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in ubuntu. -- 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 439315] Re: package postfix 2.5.5-1.1 failed to install/upgrade: subprocess post-installation script returned error exit status 75
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/32745024/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/32745025/DpkgTerminalLog.txt -- package postfix 2.5.5-1.1 failed to install/upgrade: subprocess post-installation script returned error exit status 75 https://bugs.launchpad.net/bugs/439315 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in ubuntu. -- 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 278864] Re: samba4 should 'Conflicts:' with samba-tools
** Changed in: samba4 (Ubuntu) Status: Triaged = Fix Released ** Changed in: samba4 (Ubuntu) Assignee: (unassigned) = Jelmer Vernooij (jelmer) -- samba4 should 'Conflicts:' with samba-tools https://bugs.launchpad.net/bugs/278864 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba4 in ubuntu. -- 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 438395] Re: virsh crashed with SIGSEGV in virDomainCreate()
** Visibility changed to: Public -- virsh crashed with SIGSEGV in virDomainCreate() https://bugs.launchpad.net/bugs/438395 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 439364] [NEW] Internal error registering local walrus
Public bug reported: Registering a walrus on localhost fails with an internal error message: $ sudo euca_conf --register-walrus localhost Adding WALRUS host localhost Internal Error. ERROR: failed to register Walrus, please log in to the admin interface and check cloud status. This was done with a freshly installed Eucalyptus. I'm attaching the logs. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Internal error registering local walrus https://bugs.launchpad.net/bugs/439364 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439364] Re: Internal error registering local walrus
** Attachment added: eucalyptus-logs.tar.bz2 http://launchpadlibrarian.net/32747582/eucalyptus-logs.tar.bz2 -- Internal error registering local walrus https://bugs.launchpad.net/bugs/439364 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
Needs to be reverted to code from ubuntu12 and uploaded as ubuntu14. ** Changed in: eucalyptus (Ubuntu Karmic) Status: New = Triaged ** Changed in: eucalyptus (Ubuntu Karmic) Milestone: ubuntu-9.10-beta = None -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 343898] Re: dhclient-script apparmor issues
Jamie, I continue to have this problem. Here is an example what I get logged to /var/log/kern.log type=1503 audit(1254319799.833:61): operation=inode_permission requested_mask=r:: denied_mask=r:: fsuid=0 name=/bin/bash pid=9551 profile=/sbin/dhclient-script Could you please elaborate on how to put apparmor in the initramfs? Also, how would I make sure that ifupdown loads the profile before dhclient3 starts? Thanks -- dhclient-script apparmor issues https://bugs.launchpad.net/bugs/343898 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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 439410] [NEW] Instances from fresh EMIs sometimes fail to start
Public bug reported: Running 1.6~bzr854-0ubuntu12 Starting an instance of a freshly baked EMI, I get on the NC: nc.log [EUCADEBUG ] walrus_request(): wrote 36 bytes in 1 writes [EUCAERROR ] walrus_request(): server responded with HTTP code 500 [EUCAINFO ] walrus_request(): due to error, removing /var/lib/eucalyptus/instances/admin/i-35F90747/disk [EUCAERROR ] error: failed to download file from Walrus into /var/lib/eucalyptus/instances/admin/i-35F90747/disk [EUCAFATAL ] Failed to prepare images for instance i-35F90747 (error=1) Running a new instance of the same EMI just after that usually succeeds. Couldn't find anything useful in the CC logs. ** Affects: eucalyptus (Ubuntu) Importance: Medium Status: New ** Changed in: eucalyptus (Ubuntu) Importance: Undecided = Medium -- Instances from fresh EMIs sometimes fail to start https://bugs.launchpad.net/bugs/439410 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439415] [NEW] Bundling UEC image with provided ramdisk results in an EMI that fails to boot
Public bug reported: Using UEC 20090929 beta candidate on UEC cloud. Bundling the amd64 image with local kernel and ramdisk works. Bundling it with uec-images-published kernel and ramdisk fails (see get-console-output log). Bundling it with uec-images-published kernel and local ramdisk works. ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New ** Tags: uec-images -- Bundling UEC image with provided ramdisk results in an EMI that fails to boot https://bugs.launchpad.net/bugs/439415 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 410379] Re: Tomcat security configuration error prevents proper logging when used with Sun's JVM
You may also put this in a file like /etc/tomcat6/policy.d/99custom-
fixes.policy :
grant codeBase file:${catalina.home}/bin/tomcat-juli.jar {
permission java.lang.RuntimePermission setContextClassLoader;
};
... does the job without too widely opening security.
--
Tomcat security configuration error prevents proper logging when used with
Sun's JVM
https://bugs.launchpad.net/bugs/410379
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.
--
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 439415] Re: Bundling UEC image with provided ramdisk results in an EMI that fails to boot
** Attachment added: euca-get-console-output for failed EMI http://launchpadlibrarian.net/32749737/boot.log -- Bundling UEC image with provided ramdisk results in an EMI that fails to boot https://bugs.launchpad.net/bugs/439415 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
** Changed in: eucalyptus (Ubuntu Karmic) Assignee: (unassigned) = Dustin Kirkland (kirkland) -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
Some more information. I did a 20090930.1 CD-based install. Cluster : no issue. Looking at the registration logs, I remember seeing some errors, but the final lines all show success with the external IP used, so I figured everything was ok and fixed. Node: no issue. Stopped/started eucalyptus on cluster to take care of bug 439251 Ran nodes discovery and added the node. On the node, nc.log shows its getting polled. Bundled EMI, ran instance: nc.log shows 127.0.0.1 walrus download errors (see above) Going back to the cluster, I tried: - restarting everything - manually registering - manually registering and restart - manually deregister, register and restart Every time the external IP address is shown and the tools answer success. But every time I run the instance I got the error on the NC. -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 343898] Re: dhclient-script apparmor issues
severin, You don't have to do anything on 9.10. 9.04 had logic for handling ifupdown (which is why you are seeing the problem). Can you please perform: $ sudo apport-collect -p apparmor 343898 ** Changed in: dhcp3 (Ubuntu) Status: Fix Released = Incomplete -- dhclient-script apparmor issues https://bugs.launchpad.net/bugs/343898 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
Is it possible that, at some point, a walrus registration was attempted with 'localhost'? If so, you'll need to deregister walrus: euca_conf --deregister-walrus and try registering again with a valid public IP. This error is implying that the system believes that a registered walrus lives on 127.0.0.1 -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
This is an install from scratch, using CD install. First test was done with the autoregistration stuff from Dustin. The logs showed the external IP to be used. See above, I tried deregister/manual register. It also showed external IP being used, and also failed. I think there ios something on the NC side that makes it believe walrus is 127.0.0.1, whatever you do on the Cluster side doesn't seem to help. btw, I also tried deregistering the node and reregistering it, fwiw :) -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 344400] Re: libvirtError: internal error unable to start guest
Is this bug only relevant to disk files? I am booting guests fine with raw disks, albeit LVM-based. Details: On a Jaunty KVM host I'm using LVM. When creating a guest I allocated 2 logical volumes (4 GB and 80 GB) to it to be used as raw disks. With virt-manager I used the first one (/dev/vda) for installation (with LVM again; so LVM over LVM) and afterwards added the second one (/dev/vdb). I also set up LVM on the second disk and created a 40 GB logical volume. The VM starts fine. -- libvirtError: internal error unable to start guest https://bugs.launchpad.net/bugs/344400 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 343898] Re: dhclient-script apparmor issues
Jamie, I am running jaunty (ie. 9.4) not karmic. BTW. it's an eeePc with custom kernel. I ran $ sudo apport-collect -p apparmor 343898 (twice actually) and this is what I got in response Logging into Launchpad... Downloading bug... Bug title: dhclient-script apparmor issues Collecting apport information for source package apparmor... Uploading additional information to Launchpad bug... short text data... Error connecting to Launchpad: HTTP Error 401: Unauthorized -- dhclient-script apparmor issues https://bugs.launchpad.net/bugs/343898 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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 343898] Re: dhclient-script apparmor issues
Actually, you gave enough information to know what the problem is. The apparmor profile in 9.04 is specific to the 2.6.28 kernel as included in Ubuntu. There was a bug in the kernel that is worked around in the apparmor profile. This is bug #400349. For people who are using a non- Ubuntu kernel on Ubuntu 9.04 and are seeing this bug, I recommend either using the apparmor profile from dhcp3-client 3.1.2-1ubuntu5 (in Ubuntu 9.10) or disabling the dhclient3 profile (sudo ln -s /etc/apparmor.d/sbin.dhclient3 /etc/apparmor.d/disable) until you can upgrade to Ubuntu 9.10. ** Changed in: dhcp3 (Ubuntu) Status: Incomplete = Fix Released -- dhclient-script apparmor issues https://bugs.launchpad.net/bugs/343898 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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 437944] Re: Samba session request failure when using IP address
** This bug has been marked a duplicate of bug 435061 smbd loses connection on DHCP lease ** This bug is no longer a duplicate of bug 435061 smbd loses connection on DHCP lease -- Samba session request failure when using IP address https://bugs.launchpad.net/bugs/437944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 420960] Re: Karmic Alpha 4 playback stops when playing media stored on samba share
** Package changed: dhcp3 (Ubuntu) = samba (Ubuntu) ** Changed in: samba (Ubuntu) Assignee: (unassigned) = Chuck Short (zulcss) -- Karmic Alpha 4 playback stops when playing media stored on samba share https://bugs.launchpad.net/bugs/420960 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 435061] Re: smbd loses connection on DHCP lease
*** This bug is a duplicate of bug 420960 *** https://bugs.launchpad.net/bugs/420960 ** This bug has been marked a duplicate of bug 420960 Karmic Alpha 4 playback stops when playing media stored on samba share -- smbd loses connection on DHCP lease https://bugs.launchpad.net/bugs/435061 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 42947] Re: postfix: fatal: /etc/postfix/postfix-script: No such file or directory
Ran aswell in with Jaunty Much simplier solution, even with no connection at all touch /etc/postfix/main.cf -- postfix: fatal: /etc/postfix/postfix-script: No such file or directory https://bugs.launchpad.net/bugs/42947 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in ubuntu. -- 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 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
Thierry, I *definitely* am not reproducing the 127.0.0.1 error. In my nc.log, I'm seeing: [Wed Sep 30 17:37:49 2009][008286][EUCAINFO ] from http://192.168.0.136:8773/services/Walrus/ueckernel/vmlinuz-2.6.31-11-generic.manifest.xml [Wed Sep 30 17:37:49 2009][008286][EUCAINFO ] from http://192.168.0.136:8773/services/Walrus/uecramdisk/initrd.img-2.6.31-11-generic.manifest.xml [Wed Sep 30 17:37:49 2009][008286][EUCAINFO ] from http://192.168.0.136:8773/services/Walrus/uecimage/ubuntu-uec-jaunty-amd64.img.manifest.xml [Wed Sep 30 17:37:49 2009][008286][EUCAINFO ] from http://192.168.0.136:8773/services/Walrus/uecimage/ubuntu-uec-jaunty-amd64.img.manifest.xml Where 192.168.0.136 is my CC, and 192.168.0.121 is my NC. I am also seeing my network traffic flooded for ~15 minutes as it downloads 10GB+, and I see r...@node:/var/lib/eucalyptus/instances# find /var/lib/eucalyptus/instances/ -type f /var/lib/eucalyptus/instances/admin/i-3BEB06F3/kernel /var/lib/eucalyptus/instances/admin/i-3BEB06F3/ramdisk /var/lib/eucalyptus/instances/admin/i-3BEB06F3/disk-digest /var/lib/eucalyptus/instances/admin/i-3BEB06F3/disk /var/lib/eucalyptus/instances/eucalyptus/cache/eki-8F0A139D/kernel /var/lib/eucalyptus/instances/eucalyptus/cache/eki-8F0A139D/kernel-digest /var/lib/eucalyptus/instances/eucalyptus/cache/eri-E64F14E8/ramdisk /var/lib/eucalyptus/instances/eucalyptus/cache/eri-E64F14E8/ramdisk-digest /var/lib/eucalyptus/instances/eucalyptus/cache/emi-D5871527/disk-staging However, I never see my instance move from pending to running, so there is a bug here, but perhaps different from whatever you're seeing on your end. RESERVATION r-31500705 admin default INSTANCEi-3BEB06F3 emi-D5871527192.168.0.250 172.19.1.2 pending mykey 0 m1.xlarge 2009-09-30T22:37:49.042Zcanyonedge eki-8F0A139Deri-E64F14E8 :-Dustin -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
Actually, the last part of the previous comment about never moving pending-running might be premature, actually. Its still working on creating the instance, I think. In the NC, I can see: root 17311 17278 3 17:53 ?00:00:16 /bin/dd if=/var/lib/eucalyptus/instances/admin/i-3BEB06F3/disk of=/dev/loop1 bs=512k So I'll give it a bit longer. (Note that I'm doing this on an external USB hardrive, so my throughput is very slow, like 10MB/s). :-Dustin -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
Okay, yeah, so my instance runs after a long time: RESERVATION r-31500705 admin default INSTANCEi-3BEB06F3 emi-D5871527192.168.0.250 172.19.1.2 running mykey 0 m1.xlarge 2009-09-30T22:37:49.042Z canyonedge eki-8F0A139Deri-E64F14E8 The console output is attached. Networking isn't quite working correctly. :-Dustin ** Attachment added: out http://launchpadlibrarian.net/32763199/out -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
The lack of networking appears to be a problem in the particular image I tried (daily UEC build). When I run bundle and run an image from Eucalyptus, such as: * http://eucalyptussoftware.com/downloads/eucalyptus-images/euca-ubuntu-9.04-x86_64.tar.gz networking comes up just fine! I'm now running my *first* network connected Eucalyptus instance! :-Dustin -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439288] Re: 1.6~bzr854-0ubuntu13 fails to run instances
I was able to do this with these instructions: wget http://eucalyptussoftware.com/downloads/eucalyptus-images/euca-ubuntu-9.04-x86_64.tar.gz gunzip euca-ubuntu-9.04-x86_64.tar.gz tar xvf euca-ubuntu-9.04-x86_64.tar euca-bundle-image -i euca-ubuntu-9.04-x86_64/kvm-kernel/vmlinuz-2.6.28-11-generic --kernel true euca-upload-bundle -b ueckernel -m /tmp/vmlinuz-2.6.28-11-generic.manifest.xml euca-register ueckernel/vmlinuz-2.6.28-11-generic.manifest.xml euca-bundle-image -i euca-ubuntu-9.04-x86_64/kvm-kernel/initrd.img-2.6.28-11-generic --ramdisk true euca-upload-bundle -b uecramdisk -m /tmp/initrd.img-2.6.28-11-generic.manifest.xml euca-register uecramdisk/initrd.img-2.6.28-11-generic.manifest.xml euca-bundle-image -i euca-ubuntu-9.04-x86_64/ubuntu.9-04.x86-64.img --kernel eki- --ramdisk eri- euca-upload-bundle -b uecimage -m /tmp/ubuntu.9-04.x86-64.img.manifest.xml euca-register uecimage/ubuntu.9-04.x86-64.img.manifest.xml euca-run-instances -k mykey emi- watch -n 5 euca-describe-instances euca-get-console-output i- touch mykey.priv chmod 600 mykey.priv euca-add-keypair mykey mykey.priv ssh -i mykey.priv ubu...@192.168.0.250 -- 1.6~bzr854-0ubuntu13 fails to run instances https://bugs.launchpad.net/bugs/439288 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 439788] [NEW] ec2-bundle-image and ec2-unbundle-image use single, static named fifo in /tmp
Public bug reported: Binary package hint: ec2-ami-tools the ec2-bundle-image and ec2-unbundle-image tools make fifos in /tmp with names of ec2-bundle-image-digest and ec2-unbundle-image-digest respectively. This is potentially a security issue, and definitely it means that 2 processes can't be doing this at the same time. The proposed patch attached uses random filename in /tmp for feeding to mkfifo. It also turns down the permissions on the fifo that is created using '--mode' flag to mkfifo. ** Affects: ec2-ami-tools (Ubuntu) Importance: Medium Assignee: Scott Moser (smoser) Status: Confirmed -- ec2-bundle-image and ec2-unbundle-image use single, static named fifo in /tmp https://bugs.launchpad.net/bugs/439788 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-ami-tools in ubuntu. -- 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 439788] Re: ec2-bundle-image and ec2-unbundle-image use single, static named fifo in /tmp
** Attachment added: proposed patch http://launchpadlibrarian.net/32767375/ec2-ami-tools-use-random-mkfifo-name.diff -- ec2-bundle-image and ec2-unbundle-image use single, static named fifo in /tmp https://bugs.launchpad.net/bugs/439788 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-ami-tools in ubuntu. -- 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
