[Bug 1153626] Re: Multiple Interfaces and IPs not detected in AWS VPC
Re-uploading attachment as solution ** Attachment added: "Re-uploading attachment as solution" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1153626/+attachment/3925065/+files/bug_1153626.tar.gz -- 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/1153626 Title: Multiple Interfaces and IPs not detected in AWS VPC To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1153626/+subscriptions -- 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 1153626] Re: Multiple Interfaces and IPs not detected in AWS VPC
Hi, I have actually adapted the files from the Amazon AMI which are working just fine. There is also an ansible file which tells where the files should be dropped. You might need to adjust a few things but it should all be working There is only a problem with this bug (https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1235169) which has actually been solved and I am waiting for the updated package to be available. Otherwise the solution for this is to add the interfaces-eth1 configuration into the main /etc/network/interfaces file. I am not good at packaging stuff so if you think this is useful it would be great if someone could wrap it up in a nice package. Myself I am ok with using ansible for now :) Hope this helps Regards Alessandro ** Attachment added: "Modified files from Amazon AMI ec2net package" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1153626/+attachment/3925064/+files/bug_1153626.tar.gz -- 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/1153626 Title: Multiple Interfaces and IPs not detected in AWS VPC To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1153626/+subscriptions -- 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 1058301] Re: [bzr] error when encountering large file
As a temporary work around just manually add X11/core to the end of /etc/.bzrignore Yes? (On my system, nothing else in /etc comes anywhere near the size of /etc/X11/core. So, that's likely to be the only file tripping this error for a while.) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1058301 Title: [bzr] error when encountering large file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1058301/+subscriptions -- 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 1235231] Re: plymouth loses output to /dev/console (such as ci-info: messages)
** Attachment added: "bootlogs.tar.gz" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1235231/+attachment/3924816/+files/bootlogs.tar.gz -- 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/1235231 Title: plymouth loses output to /dev/console (such as ci-info: messages) To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1235231/+subscriptions -- 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 1235231] Re: plymouth loses output to /dev/console (such as ci-info: messages)
On a regular trusty laptop with an SSD i did 6 boots (3 reboots and 3 cold boots), and compared the boot.logs. My expectation is to have no less than 6 instances of each unique boot messages, that is not the case: 1 * Starting Bridge socket events into upstart 1 * Starting modem connection manager 1 * Starting Restore Sound Card State 1 * Starting System V initialisation compatibility 2 * Starting bluetooth daemon 2 * Starting configure network device 2 * Starting system logging daemon 3 * Starting save kernel messages 3 * Stopping save kernel messages 4 * Starting Bridge file events into upstart 4 * Starting save udev log and update rules 4 * Starting SystemD login management service 4 * Stopping save udev log and update rules 5 * Starting ACPI daemon 5 * Starting enable remaining boot-time encrypted block devices 5 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated 5 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated 5 * Stopping cold plug devices 5 * Stopping log initial device creation bootlogs attached. I'm not sure if this is the same or different problem. -- 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/1235231 Title: plymouth loses output to /dev/console (such as ci-info: messages) To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1235231/+subscriptions -- 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 586898] Re: php5 cli segmentation fault when executing script
Program received signal SIGSEGV, Segmentation fault. 0x006b57d9 in gc_zval_possible_root (zv=0x351f4c8) at /build/buildd/php5-5.3.2/Zend/zend_gc.c:143 143 GC_ZOBJ_CHECK_POSSIBLE_ROOT(zv); (gdb) bt #0 0x006b57d9 in gc_zval_possible_root (zv=0x351f4c8) at /build/buildd/php5-5.3.2/Zend/zend_gc.c:143 #1 0x006a3eb8 in zend_hash_destroy (ht=0x32e6ed0) at /build/buildd/php5-5.3.2/Zend/zend_hash.c:726 #2 0x0054efed in sxe_object_free_storage (object=0x32e3510) at /build/buildd/php5-5.3.2/ext/simplexml/simplexml.c:2016 #3 0x006bcadc in zend_objects_store_del_ref_by_handle_ex (handle=32767, handlers=0x32ecbb0) at /build/buildd/php5-5.3.2/Zend/zend_objects_API.c:220 #4 0x006bcb03 in zend_objects_store_del_ref (zobject=0x3535208) at /build/buildd/php5-5.3.2/Zend/zend_objects_API.c:172 #5 0x00719d38 in ZEND_ASSIGN_SPEC_CV_VAR_HANDLER (execute_data=0x77ea8438) at /build/buildd/php5-5.3.2/Zend/zend_execute.c:698 #6 0x006bf770 in execute (op_array=0x17cded8) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #7 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #8 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77ea6640) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #9 0x006bf770 in execute (op_array=0x17cded8) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #10 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #11 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77ea58d0) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #12 0x006bf770 in execute (op_array=0x17c7520) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #13 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #14 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77ea4a10) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #15 0x006bf770 in execute (op_array=0x1808e90) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #16 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #17 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77ea40a8) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #18 0x006bf770 in execute (op_array=0x1798168) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #19 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #20 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77ea37e0) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #21 0x006bf770 in execute (op_array=0x16fdbc0) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #22 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so ---Type to continue, or q to quit--- #23 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77ea34a0) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #24 0x006bf770 in execute (op_array=0x17348e8) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #25 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #26 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77e91440) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #27 0x006bf770 in execute (op_array=0x1945ae8) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #28 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #29 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77e90e80) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #30 0x006bf770 in execute (op_array=0x7fffea64e4c0) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #31 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #32 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77e90068) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #33 0x006bf770 in execute (op_array=0x1229120) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #34 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #35 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77e8e730) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #36 0x006bf770 in execute (op_array=0x11d7ba8) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #37 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #38 0x006e8176 in zend_do_fcall_common_helper_SPEC (execute_data=0x77e8e068) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:337 #39 0x006bf770 in execute (op_array=0x1175208) at /build/buildd/php5-5.3.2/Zend/zend_vm_execute.h:104 #40 0x7fffeb293836 in ?? () from /usr/lib/php5/20090626/suhosin.so #41 0x006971bd in zend_execute_scripts (type=538976288, retval=0x7fffbf70, file_count=3) at /build/buildd/php5-5.3.2/Zend/zend.c:1266 #42 0x0
[Bug 1258735] Re: package dbconfig-common 1.8.47+nmu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that you were running at least two install operations at the same time. I am unsure which package this bug belongs, as I would say that should not be possible, but it is not a failure of dconfig-common. Maybe somebody reading this has an idea? >From the DpkgTerminalLog.txt file: Log started: 2013-12-06 17:55:28 Paramétrage de man-db (2.6.5-2) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Ressource temporairement non disponible dpkg: erreur de traitement de man-db (--configure) : -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1258735 Title: package dbconfig-common 1.8.47+nmu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1258735/+subscriptions -- 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 1153626] Re: Multiple Interfaces and IPs not detected in AWS VPC
Hi Forest, looking at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using- eni.html#ec2-net-utils "DHCP script Whenever the network interface receives a new DHCP lease, this script queries the instance metadata for Elastic IP addresses. For each Elastic IP address, it adds a rule to the routing policy database to ensure that outbound traffic from that address uses the correct network interface. It also adds each private IP address to the network interface as a secondary address." I think all they do is run a hook script on DHCP lease that configures the interface. And yes they add multiple ip addresses to the same interface. I am looking at some sort of solution because I want to use some instances as LXC hosts and would love to give each container its own ip. So I think I will have to go down the route of using subinterfaces. Will keep tracking this bug Thank you Alessandro -- 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/1153626 Title: Multiple Interfaces and IPs not detected in AWS VPC To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1153626/+subscriptions -- 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 1251939] Re: Chroot fails with "Cannot chroot when not started as root" error
** 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 apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with "Cannot chroot when not started as root" error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+subscriptions -- 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
