[Bug 661453] Re: dovecot.conf always shows as having been locally modified on update
** Changed in: dovecot (Ubuntu) Importance: Low = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/661453 Title: dovecot.conf always shows as having been locally modified on update -- 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 654549] Re: [SRU] Tomcat6 fails to upgrade if JAVA_OPTS contains /
** Description changed: IMPACT: This bug will impact tomcat6 installs upgrading to Maverick and updates in Maverick itself; its fixed in Natty. - Using the '/' character in JAVA_OPTS is quite common - its normally uses + Using the '/' character in JAVA_OPTS is quite common - its normally used to specify the filesystem location for additional application files such as those for Hudson: - -Dhudson.home=/home/hudson + -Dhudson.home=/home/hudson Updates/upgrades using this type of option will fail. FIX: tomcat6.postinst uses sed to parse various debconf answers into a template which is used to generate /etc/default/tomcat6; this currently uses '/' as the pattern delimiter - the fix switches this to '%' which is unlikely to be used in JAVA_OPTS. PATCH: See linked branch TEST CASE 1: sudo apt-get install tomcat6 sudo dpkg-reconfigure tomcat6 - Accept all default for user and group - Add an additional parameter to JAVA_OPTS - -Dtest.dir=/var/log/nonsense + Accept all default for user and group + Add an additional parameter to JAVA_OPTS - -Dtest.dir=/var/log/nonsense Reconfiguration will fail with sed: -e expression #1, char 44: unknown option to `s' TEST CASE 2: sudo apt-get install tomcat6 sudo vi /etc/default/tomcat6 - Add an additional parameter to JAVA_OPTS - -Dtest.dir=/var/log/nonsense + Add an additional parameter to JAVA_OPTS - -Dtest.dir=/var/log/nonsense sudo dpkg-reconfigure tomcat6 - Accept all default values + Accept all default values - Reconfiguration will fail with sed: -e expression #1, char 44: unknown option to `s' - + Reconfiguration will fail with sed: -e expression #1, char 44: unknown + option to `s' + IMPACT: Minor change to maintainer script; already in development release so limited regression potential. Original bug report Binary package hint: tomcat6 tomcat upgrade fails with the following error: sed: -e expression #1, char 44: unknown option to `s' ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: tomcat6 6.0.28-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.33-server 2.6.35.4 Uname: Linux 2.6.35-22-server x86_64 Architecture: amd64 Date: Mon Oct 4 15:51:21 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.2) PackageArchitecture: all ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: tomcat6 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat6 in Ubuntu. https://bugs.launchpad.net/bugs/654549 Title: [SRU] Tomcat6 fails to upgrade if JAVA_OPTS contains / -- 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
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
so what if you issue again an upsc powercom? does it still broke the pipe? is your issue 100 % reproducible? my guess, is ATM, that the faulty end-of-line marker in battery.type is causing parseconf to close prematurely the connexion, while upsd is still sending data. which explains why unit requests works, while getting the whole tree fails... the only way to ensure this is the root cause is to fix the function that retrieve strings from the device's indexed table, to trim EOL, and check if it solves your issue. would you be ready to test a fix using subversion? cheers, Arno -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- 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 740815] Re: [FFe] Updates to enable us to drop xulrunner from main
This bug was fixed in the package libreoffice - 1:3.3.2-1ubuntu3 --- libreoffice (1:3.3.2-1ubuntu3) natty; urgency=low * make build dep on xulrunner-dev alternatively depend on firefox-dep (LP: #740815) * cherry-pick from debian: - enable is (icelandic) l10n (LP: #751746) * add unity quicklist support (LP: #720716) * workaround for unity icon issue (LP: #732412) * regenerated control file and refresh patch queue -- Bjoern Michaelsen bjoern.michael...@canonical.com Fri, 15 Apr 2011 10:01:19 +0200 ** Changed in: libreoffice (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gwt in Ubuntu. https://bugs.launchpad.net/bugs/740815 Title: [FFe] Updates to enable us to drop xulrunner from main -- 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 726769] Re: package eucalyptus-common 2.0.1 bzr1255-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags added: server-nrs -- 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/726769 Title: package eucalyptus-common 2.0.1 bzr1255-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- 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 745946] Re: cloud-final job did not run in ec2-automated-tests
** Tags added: server-nrs -- 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/745946 Title: cloud-final job did not run in ec2-automated-tests -- 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 764391] Re: cobbler fails to manage bind9
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/764391 Title: cobbler fails to manage bind9 -- 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 764391] [NEW] cobbler fails to manage bind9
Public bug reported: Binary package hint: cobbler I've been testing the dns management module in cobbler; it does not currently manage bind9 correctly as the file paths and daemon name are not aligned to Ubuntu's bind9 packaging. Does not look that difficult to fix (have it hacked locally to work); I'll work out a patch. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cobbler 2.1.0-0ubuntu6 ProcVersionSignature: Ubuntu 2.6.38-8.42-server 2.6.38.2 Uname: Linux 2.6.38-8-server x86_64 Architecture: amd64 Date: Mon Apr 18 10:11:54 2011 InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Beta amd64 (20110413) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: cobbler UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cobbler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/764391 Title: cobbler fails to manage bind9 -- 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 747090] Re: wrong return address sometimes pushed for INT in kvm (not qemu)
Confirmed with apw that this is fixed in ubuntu git tree, and will be Fixed in first SRU upload. Updating milestone to natty-updates to reflect this. ** Changed in: linux (Ubuntu Natty) Milestone: ubuntu-11.04 = natty-updates -- 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/747090 Title: wrong return address sometimes pushed for INT in kvm (not qemu) -- 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 764391] Re: cobbler fails to manage bind9
Templates could integrate with a standard bind9 install a bit better as well - will include in the patch ** Changed in: cobbler (Ubuntu) Importance: Undecided = Medium ** Changed in: cobbler (Ubuntu) Assignee: (unassigned) = James Page (james-page) ** Changed in: cobbler (Ubuntu) Milestone: None = ubuntu-11.10 ** Tags added: server-nrs -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/764391 Title: cobbler fails to manage bind9 -- 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 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
yes, it 100 % reproducible. i am ready to test svn version. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- 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 764391] Re: cobbler fails to manage bind9
** Branch linked: lp:~james-page/ubuntu/natty/cobbler/fix-764391 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/764391 Title: cobbler fails to manage bind9 -- 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 747090] Re: wrong return address sometimes pushed for INT in kvm (not qemu)
** Tags added: server-nro ** Tags removed: server-nrs -- 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/747090 Title: wrong return address sometimes pushed for INT in kvm (not qemu) -- 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 580319] Re: dhcp3-server launches before upstart brings all interface, thus failing to start
dhcp3 is no longer in Natty archive, it's been replaced by a transitional package to isc-dhcp (v4), marking Natty task invalid for dhcp3. ** Changed in: dhcp3 (Ubuntu Natty) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/580319 Title: dhcp3-server launches before upstart brings all interface, thus failing to start -- 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 764391] Re: cobbler fails to manage bind9
** Changed in: cobbler (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/764391 Title: cobbler fails to manage bind9 -- 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 726769] Re: package eucalyptus-common 2.0.1 bzr1255-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: eucalyptus (Ubuntu Natty) Assignee: (unassigned) = Dave Walker (davewalker) -- 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/726769 Title: package eucalyptus-common 2.0.1 bzr1255-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- 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
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/18 Virus 753...@bugs.launchpad.net yes, it 100 % reproducible. I also managed to reproduce it using dummy-ups (the simulation driver) and injecting the error on the same variable: adding a newline (ie \n) results in a broken pipe on upsc side. i am ready to test svn version. ok, here we go: 1) checkout an svn copy using: $ svn co svn://svn.debian.org/nut/trunk 2) configure it using (Debian arguments, limited for the current test scope ; should be sufficient): --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \ --mandir=/usr/share/man \ --libdir=/lib \ --includedir=/usr/include \ --without-all \ --with-usb \ --enable-static \ --with-statepath=/var/run/nut \ --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut \ --with-pidpath=/var/run/nut \ --datadir=/usr/share/nut \ --with-pkgconfig-dir=/usr/lib/pkgconfig \ --with-user=nut --with-group=nut 3) apply the attached patch $ patch -p0 /path/to/virus.patch 4) make as usual, ie $ make 5) stop all previous NUT instances, then launch the new driver and upsd $ sudo drivers/usbhid-ups -a powercom $ sudo server/upsd -DDD 6) now issue your upsc of death $ upsc powercom everything should behave fine. Remember that it's a blind patch: I've not validated the above configure line, nor the patch itself! cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ** Attachment added: virus.patch https://bugs.launchpad.net/bugs/753661/+attachment/2059655/+files/virus.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- 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 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
It`s working great! Many thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- 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 759943] Re: mod_wsgi.so-3.2 gives errors
** Changed in: mod-wsgi (Ubuntu) Assignee: (unassigned) = James Page (james-page) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mod-wsgi in Ubuntu. https://bugs.launchpad.net/bugs/759943 Title: mod_wsgi.so-3.2 gives errors -- 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
Re: [Bug 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
2011/4/18 Virus 753...@bugs.launchpad.net It`s working great! Many thanks! excellent, thanks for the feedback. I've just committed it upstream (r2972) the changeset will be available on the NUT Trac mirror (just give it some minutes to sync): http://trac.networkupstools.org/projects/nut/changeset/2972 I'll leave up to our Ubuntu friends to generate an updated package. I have to note that importance is low since this should not affect the protection (ie upsmon is still working fine). @Virus: can you please confirm this point? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- 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 753661] Re: upsd write() failed for 127.0.0.1: Broken pipe
Yeah, upsmon working fine. I was checked it now by unplug power cable. upsmon was generate alerts UPS powercom@localhost on battery and UPS powercom@localhost on line power after plug cable back. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/753661 Title: upsd write() failed for 127.0.0.1: Broken pipe -- 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 759943] Re: mod_wsgi.so-3.2 gives errors
** Branch linked: lp:~james-page/ubuntu/natty/mod-wsgi/fix-759943 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mod-wsgi in Ubuntu. https://bugs.launchpad.net/bugs/759943 Title: mod_wsgi.so-3.2 gives errors -- 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 614731] Re: shutdown hangs with wlan autofs/nfs mounted homedirs
Same for me. We have autofs home dirs. eth0 is in /etc/network/interfaces so users have no control over it. For some reason unclear to me, shutdown fails unless I first unlog and then stop autofs and gdm by hand before asking to shut down. This is very painful, especially because it is difficult to debug: there is no clear documented way to understand the order in which the upstart jobs are shutting down and where is the deadlock (which job is waiting for which, etc.), unless (following the upstart doc) I put additional debugging commands all over the place in the upstart scripts. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/614731 Title: shutdown hangs with wlan autofs/nfs mounted homedirs -- 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 387189] Re: logrotate incorrectly rotates /dev/null to /dev/null.1
Confirmed fix in logrotate 4.7.8-4ubuntu2.1 (Lucid proposed). Marking verification-done. ** Tags added: verification-done ** Tags removed: verification-needed -- 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/387189 Title: logrotate incorrectly rotates /dev/null to /dev/null.1 -- 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 764391] Re: cobbler fails to manage bind9
** Changed in: cobbler (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/764391 Title: cobbler fails to manage bind9 -- 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 745930] Re: cloud-init timeout waiting for metadata service on EC2
** Changed in: cloud-init (Ubuntu) Milestone: ubuntu-11.04 = None -- 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/745930 Title: cloud-init timeout waiting for metadata service on EC2 -- 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 764391] Re: cobbler fails to manage bind9
** Changed in: cobbler (Ubuntu) Milestone: ubuntu-11.10 = ubuntu-11.04 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/764391 Title: cobbler fails to manage bind9 -- 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 745008] Re: Files left behind on upgrade from Maverick
There's some validity in having /var/lib/dhcp3 files still exist: we don't remove the old leases unless the user specifically removes the transitional dhcp3-client packages. That seems to be a decision that was made in Debian, and I think it makes some sense -- later, upgrades from 11.04 should probably remove these files. I'm removing the assignment for now and setting this back to Triaged because it needs to be brought up to the Debian maintainers of isc-dhcp. Much of the same goes for samba: seems like the enter/exit scripts were created in /etc/dhcp/dhclient-*-scripts.d as symlinks to the same scripts in /etc/dhcp3; and changing this would need to be done in Debian. ** Changed in: isc-dhcp (Ubuntu) Status: In Progress = Triaged ** Changed in: isc-dhcp (Ubuntu) Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned) ** Also affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/745008 Title: Files left behind on upgrade from Maverick -- 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 745008] Re: Files left behind on upgrade from Maverick
Seems the symlinks in Samba were done on purpose for upgrade compatibility, since samba doesn't depend on the installed DHCP client and can't know which is the correct directory to put the hooks in. At a later point in Debian samba should drop that symlink. ** Changed in: samba (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/745008 Title: Files left behind on upgrade from Maverick -- 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 764391] Re: cobbler fails to manage bind9
This bug was fixed in the package cobbler - 2.1.0-0ubuntu7 --- cobbler (2.1.0-0ubuntu7) natty; urgency=low * Fixed management of bind9 (LP: #764391): - debian/patches/40_ubuntu_bind9_management.patch: - Manage bind9 instead of named daemon. - Generate configuration in /etc/bind. - Use default bind9 configuration as much as possible. - debian/control: Added Suggests: bind9 to cobbler. -- James Page james.p...@canonical.com Mon, 18 Apr 2011 11:15:59 +0100 ** Changed in: cobbler (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/764391 Title: cobbler fails to manage bind9 -- 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
Re: [Bug 343870] Re: php-cli segmentation fault with mysql extension
Excerpts from Nonox's message of Sun Apr 17 17:02:41 UTC 2011: Hi Clint Byrum, sorry for the delay, here is the result of dpkg -l 'libmysqlclient*': Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-===-== un libmysqlclient-dev none (no description available) ii libmysqlclient165.1.49-1ubuntu8.1 MySQL database client library This looks like an up to date Maverick, which should not display this behavior. Hopefully it wasn't accidentally regressed. Can you install gdb, mysql-dbg, and php5-dbg, and run with gdb /usr/bin/php then at the prompt do run -whatever --options you_use.php Then when it segfaults do 'bt' and paste the backtrace? Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/343870 Title: php-cli segmentation fault with mysql extension -- 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
Re: [Bug 576501] Re: vmbuilder doesn't recognize --ec2 flag
Thanks for testing, Henrik. But is there any way you could test on a natty system? Your failure looks to be due to a different bug, and my test just now in a maverick container also failed, differently from yours. But on two different natty systems it has succeeded (using your exact commandline, and also using --ec2-bundle). I'd like to get the fix upstream first, and then figure out what needs to be done to backport it. In fact, a simple vmbuilder kvm ubuntu --suite=lucid \ --mirror=http://10.42.43.65:3142/us.archive.ubuntu.com/ubuntu/ --debug failed for me. So that is unrelated to --ec2 -serge -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/576501 Title: vmbuilder doesn't recognize --ec2 flag -- 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 633725] Re: mysql thread_stack parameter too low, causing usage problems.
You can close this. I have given up on this bug. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/633725 Title: mysql thread_stack parameter too low, causing usage problems. -- 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
Re: [Bug 576501] Re: vmbuilder doesn't recognize --ec2 flag
Hi Serge! I acknowledge your point of view and more thorough insight into vmbuilder than me. What can I do to help you? -Henrik On Mon, Apr 18, 2011 at 7:19 PM, Serge Hallyn 576...@bugs.launchpad.net wrote: Thanks for testing, Henrik. But is there any way you could test on a natty system? Your failure looks to be due to a different bug, and my test just now in a maverick container also failed, differently from yours. But on two different natty systems it has succeeded (using your exact commandline, and also using --ec2-bundle). I'd like to get the fix upstream first, and then figure out what needs to be done to backport it. In fact, a simple vmbuilder kvm ubuntu --suite=lucid \ --mirror=http://10.42.43.65:3142/us.archive.ubuntu.com/ubuntu/ --debug failed for me. So that is unrelated to --ec2 -serge -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/576501 Title: vmbuilder doesn't recognize --ec2 flag Status in Virtual Machine Builder: New Status in “vm-builder” package in Ubuntu: In Progress Bug description: Description: Ubuntu 10.04 LTS Release: 10.04 python-vm-builder-ec2: Installed: 0.12.3-0ubuntu1 Candidate: 0.12.3-0ubuntu1 Version table: *** 0.12.3-0ubuntu1 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status Hi, I can't generate EC2 images with vmbuilder. I'm using a command like this: sudo vmbuilder xen ubuntu --suite=lucid --ec2 \ --ec2-cert=.ec2/cert-.pem \ --ec2-key=.ec2/pk-.pem \ --ec2-access-key=WHATEVER \ --ec2-secret-key=WHATEVER \ --ec2-user=424242424242 --ec2-bucket=anyrandombucket --ec2-prefix=test \ --ec2-version='first' \ --firstboot=/usr/share/doc/python-vm-builder-ec2/examples/ec2-firstboot.sh \ --part=/usr/share/doc/python-vm-builder-ec2/examples/ec2-i386-part-file.txt \ --debug Actually, I was following this howto: https://wiki.ubuntu.com/EC2Vmbuilder When I run vmbuilder with those flags, I just get this message: Usage: vmbuilder hypervisor distro [options] vmbuilder: error: no such option: --ec2 So, I can not build images for Amazon EC2. I inspected /usr/share/pyshared/VMBuilder/plugins/ec2/__init__.py and I found at the last line of that file this: #register_plugin(EC2) I uncommented that line and it didn't work. Also I tried using register_hypervisor_plugin(EC2), but it didn't work -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/576501 Title: vmbuilder doesn't recognize --ec2 flag -- 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 760157] Re: euca-bundle-image can fail on small images
I have merged this into the new development branch for euca2ools upstream. We will need to decide if we are going to merge into the 1.3.1 branch upstream. ** Changed in: euca2ools Assignee: (unassigned) = Mitch Garnaat (mitch-garnaat) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/760157 Title: euca-bundle-image can fail on small images -- 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 628145] Re: Eucalyptus does not understand IPv6
** Tags added: ipv6 -- 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/628145 Title: Eucalyptus does not understand IPv6 -- 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
Re: [Bug 576501] Re: vmbuilder doesn't recognize --ec2 flag
Quoting Henrik Bach (576...@bugs.launchpad.net): 2011-04-16 04:36:12,380 INFO: Creating config file /etc/default/grub with new version 2011-04-16 04:36:12,970 INFO: /proc/devices: fopen failed: No such file or directory 2011-04-16 04:36:12,971 INFO: Is device-mapper driver missing from kernel? Hm. Actually all the problems I've had I've traced to environments (bad network setup for one, device permissions for another). I finally got a maverick xen host in a working environment - and vmbuilder -ec2 worked there. What does /proc/devices on your host show? What sort of storage setup do you have? The 'Is device-mapper driver missing from kernel?' is odd, and presumably comes from grub in the chroot. It almost sounds like your host is multipathed. What does 'df -h' and 'mount' on the host show? Does a regular 'vmbuilder xen ubuntu' work for you? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/576501 Title: vmbuilder doesn't recognize --ec2 flag -- 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
Re: [Bug 614731] Re: shutdown hangs with wlan autofs/nfs mountedhomedirs
I'm pretty sure that the problem is because the network stops before filesystem unmounts, and so the nfs unmount hangs because the file server is unreachable. The fix would be to unmount network file systems before stopping the network. But that would require stopping processes that use network file systems even sooner than that. But some processes are used to manage the network card (particularly wireless network) so they can't be killed before un-mounting the network file systems. The current workaround is to use windows with roaming profile or something like that, I believe that works quite well. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/614731 Title: shutdown hangs with wlan autofs/nfs mounted homedirs -- 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 765224] [NEW] import from mini.iso fails
Public bug reported: Binary package hint: cobbler Importing the natty mini iso fails as the import detection looks for the dists directory and also cannot determine which ubuntu version it is importing. Tested using: http://archive.ubuntu.com/ubuntu/dists/natty/main /installer-amd64/current/images/netboot/mini.iso root@install:~# mount -o loop mini.iso /mnt root@install:~# cobbler import --name=natty-mini --path=/mnt --breed=ubuntu task started: 2011-04-18_222035_import task started (id=Media import, time=Mon Apr 18 22:20:35 2011) Warning: No distro signature for kernel at /mnt, using value from command line running: rsync -a '/mnt/' /var/www/cobbler/ks_mirror/natty-mini/ --exclude-from=/etc/cobbler/rsync.exclude --quiet received on stdout: received on stderr: adding distros associating repos associating kickstarts *** TASK COMPLETE *** After this has imported, it correctly copied created the ks_mirror tree in /var/www/cobbler/ks_mirror/natty-mini but does not create any distro or profile in cobbler. After adding these manually, I can install systems without issues: cobbler distro add --name=natty-mini --kernel=/var/www/cobbler/ks_mirror/natty-mini/linux --initrd=/var/www/cobbler/ks_mirror/natty-mini/initrd.gz --arch=x86_64 --breed=ubuntu --os-version=natty cobbler profile add --name=natty-mini-install --distro=natty-mini --kickstart=/var/lib/cobbler/kickstarts/ubuntu-client.seed cobbler sync ** Affects: cobbler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/765224 Title: import from mini.iso fails -- 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 765249] [NEW] tarmode exclude no longer working
Public bug reported: Binary package hint: samba 1) 11.04 2)samba: Installed: 2:3.5.8~dfsg-1ubuntu2 Candidate: 2:3.5.8~dfsg-1ubuntu2 Version table: *** 2:3.5.8~dfsg-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages 100 /var/lib/dpkg/status 3) Backuppc was backing up fine but no longer works (did not work with 10.10 or with 11.04 4) smbclient no longer excludes directories or files when tarmode is enabled. This is breaking backuppc as backuppc relies on smb for one of its transfer methods. To reproduce try: /usr/bin/smbclient user\\D -U user -E -d 1 -c tarmode\ full -TcrX - \\dirToExclude /dev/null There is no formatting of the directory (\\dirToExclude) which will allow its exclusion. A similar problem was discussed years ago: https://bugzilla.samba.org/show_bug.cgi?id=4734 ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/765249 Title: tarmode exclude no longer working -- 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 765224] Re: import from mini.iso fails
** Changed in: cobbler (Ubuntu) Status: New = Confirmed ** Changed in: cobbler (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/765224 Title: import from mini.iso fails -- 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 765224] Re: import from mini.iso fails
Related to bug https://bugs.launchpad.net/ubuntu-cdimage/+bug/765254 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/765224 Title: import from mini.iso fails -- 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 765224] Re: import from mini.iso fails
The server/desktop cdimage is different from the mini.iso. The mini.iso support will have to be added later. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/765224 Title: import from mini.iso fails -- 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 765275] Re: metadata server cannot be contacted when deploying new instances on EUC
-- 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 server cannot be contacted when deploying new instances on EUC -- 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 765275] [NEW] metadata server cannot be contacted when deploying new instances on EUC
Public bug reported: ## Issue New instances deployed on EUC cannot contact the metadata server, failing with Connection refused. ## Environment Distributor ID: Ubuntu Description:Ubuntu Natty (development branch) Release:11.04 Codename: natty ii eucalyptus-admin-tools 2.0.1+bzr1256-0ubuntu4 Elastic Utility Computing Architecture - Admin tools ii eucalyptus-cc2.0.1+bzr1256-0ubuntu4 Elastic Utility Computing Architecture - Cluster controller ii eucalyptus-cloud 2.0.1+bzr1256-0ubuntu4 Elastic Utility Computing Architecture - Cloud controller ii eucalyptus-common2.0.1+bzr1256-0ubuntu4 Elastic Utility Computing Architecture - Common files ii eucalyptus-gl2.0.1+bzr1256-0ubuntu4 Elastic Utility Computing Architecture - Logging service ii eucalyptus-java-common 2.0.1+bzr1256-0ubuntu4 Elastic Utility Computing Architecture - Common Java package ii eucalyptus-sc2.0.1+bzr1256-0ubuntu4 Elastic Utility Computing Architecture - Storage controller ii eucalyptus-walrus2.0.1+bzr1256-0ubuntu4 Elastic Utility Computing Architecture - Walrus (S3) ii libeucalyptus-commons-ext-java 0.5.0-0ubuntu2 Eucalyptus commons external Java library ## Resolution - reinstalling usually fixes the issue, but this is suboptimal ## Diagnostic Steps euca-get-console-output shows the following: lxcmount stop/pre-start, process 47 init: udev-fallback-graphics main process (256) terminated with status 1 init: plymouth main process (49) killed by SEGV signal init: plymouth-splash main process (259) terminated with status 2 cloud-init start-local running: Mon, 18 Apr 2011 22:05:50 +. up 7.14 seconds no instance data found in start-local init: cloud-init-local main process (255) terminated with status 1 cloud-init start running: Mon, 18 Apr 2011 22:05:50 +. up 7.70 seconds 2011-04-18 22:05:50,859 - DataSourceEc2.py[WARNING]: waiting for metadata service at http://169.254.169.254/2009-04-04/meta-data/instance-id 2011-04-18 22:05:50,861 - DataSourceEc2.py[WARNING]: 22:05:50 [ 1/30]: url error [[Errno 111] Connection refused] 2011-04-18 22:05:51,864 - DataSourceEc2.py[WARNING]: 22:05:51 [ 2/30]: url error [[Errno 111] Connection refused] 2011-04-18 22:05:52,868 - DataSourceEc2.py[WARNING]: 22:05:52 [ 3/30]: url error [[Errno 111] Connection refused] ... 2011-04-18 19:55:09,908 - DataSourceEc2.py[WARNING]: 19:55:09 [26/30]: url error [[Errno 111] Connection refused] 2011-04-18 19:55:15,917 - DataSourceEc2.py[WARNING]: 19:55:15 [27/30]: url error [[Errno 111] Connection refused] found data source: DataSourceEc2 mountall: Event failed Opening http://169.254.169.254/2009-04-04/meta-data/instance-id from the cluster controller gives a 404 error, and not a 111 / Connection refused. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: eucalyptus-cloud 2.0.1+bzr1256-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-8.42-server 2.6.38.2 Uname: Linux 2.6.38-8-server x86_64 .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME=disaster-cluster1 Architecture: amd64 Date: Mon Apr 18 18:24:52 2011 ProcEnviron: LANGUAGE=en_US: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eucalyptus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- 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 server cannot be contacted when deploying new instances on EUC -- 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 719833] Re: ssh upstart job fails to actually bring up ssh
This sounds a lot like what happened to me when the fix for this defect was released: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/687535 I had to roll back to 5.3p1-3ubuntu4 to be able to restart Xen based Lucid instances and have sshd restart reliably. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/719833 Title: ssh upstart job fails to actually bring up ssh -- 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 765367] [NEW] xinetd fails to parse config files with comments when HUPped
Public bug reported: Binary package hint: xinetd xinetd handles comments in service configuration files fine when it is started/restarted. However, when it reloads configuration files (on HUP signal), it fails to parse the same files. For example, given the following (partial) configuration file: disable = no only_from = 0.0.0.0/0 # recommended to put the IPs that need # to connect exclusively (security purposes) } on reload the following errors would be seen in syslog, and the service in question would be taken offline: Apr 19 11:47:22 adbmaster xinetd[19231]: Reading included configuration file: /etc/xinetd.d/yourservice [file=/etc/xinetd.d/yourservice] [line=26] Apr 19 11:47:22 adbmaster xinetd[19231]: failed to parse # [file=/etc/xinetd.d/yourservice] [line=13] Apr 19 11:47:23 adbmaster xinetd[19231]: failed to parse recommended [file=/etc/xinetd.d/yourservice] [line=13] Apr 19 11:47:23 adbmaster xinetd[19231]: failed to parse put [file=/etc/xinetd.d/yourservice] [line=13] Apr 19 11:47:23 adbmaster xinetd[19231]: failed to parse the [file=/etc/xinetd.d/yourservice] [line=13] Apr 19 11:47:23 adbmaster xinetd[19231]: failed to parse IPs [file=/etc/xinetd.d/yourservice] [line=13] Apr 19 11:47:23 adbmaster xinetd[19231]: failed to parse that [file=/etc/xinetd.d/yourservice] [line=13] Apr 19 11:47:23 adbmaster xinetd[19231]: failed to parse need [file=/etc/xinetd.d/yourservice] [line=13] xinetd should parse configuration files the same way on reload that it does on regular start. We hit this surprising behavior when we upgraded an unrelated package (postfix) which ran the update-inetd script, causing an xinetd reload. ** Affects: xinetd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in Ubuntu. https://bugs.launchpad.net/bugs/765367 Title: xinetd fails to parse config files with comments when HUPped -- 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
Re: [Bug 735239] Re: package postfix 2.7.0-1 failed to install/upgrade: 子程序 installed post-installation script 傳回了錯誤退出狀態 75
Thank you, James~ It is no error message again~ I hope it is done [?] I share my step about some solutions of this bug. 1. check the /etc/postfix/main.cf 2. search the /etc/hosts and /etc/hostname, comparing those infomation with /etc/postfix/main.cf [myhostname = ?] parameter. 3. I change the myhostname parameter to be the same with /etc/hostname. 4. apt-get upgrade --force-yes (little danger :P) or sudo dpkg-reconfigure postfix ** Attachment added: 360.gif https://bugs.launchpad.net/bugs/735239/+attachment/2064536/+files/360.gif -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/735239 Title: package postfix 2.7.0-1 failed to install/upgrade: 子程序 installed post- installation script 傳回了錯誤退出狀態 75 -- 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 759943] Re: mod_wsgi.so-3.2 gives errors
Patch from mod_wsgi 4.0 has been back port to mod_wsgi 3.X and can be obtained from: http://code.google.com/p/modwsgi/source/detail?r=8633d5afeea845a12c028cfae31dc828c5ce8908 Patch has also been sent to Bernd and Piotr. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mod-wsgi in Ubuntu. https://bugs.launchpad.net/bugs/759943 Title: mod_wsgi.so-3.2 gives errors -- 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 735239] Re: package postfix 2.7.0-1 failed to install/upgrade: 子程序 installed post-installation script 傳回了錯誤退出狀態 75
** Changed in: postfix (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/735239 Title: package postfix 2.7.0-1 failed to install/upgrade: 子程序 installed post- installation script 傳回了錯誤退出狀態 75 -- 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 759943] Re: mod_wsgi.so-3.2 gives errors
Okay, you can view the differences, but seems GoogleCode site doesn't make it easy to download a patch file for differences. So, have attached patch here as well. The patch is against mod_wsgi 3.3, but should still apply properly to mod_wsgi 3.2. Recommended that this only be applied when building for Python 3.2 as not sure if changes will in Python 2.X prevent mod_python from being used at same time as mod_python's use of threading APIs broken and have worked around that in the past. Now that mod_wsgi does things by the book, there may be issues. ** Patch added: Patch to mod_wsgi 3.3 from mod_wsgi site. https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/759943/+attachment/2064600/+files/patch-3.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mod-wsgi in Ubuntu. https://bugs.launchpad.net/bugs/759943 Title: mod_wsgi.so-3.2 gives errors -- 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 715152] Re: [SRU] ntp wont run on IPv6 only host unless lo has 127.0.0.1 address
In reviewing this diff for lucid-proposed: http://launchpadlibrarian.net/69484036/ntp_1%3A4.2.4p8%2Bdfsg- 1ubuntu2_1%3A4.2.4p8%2Bdfsg-1ubuntu2.1.diff.gz and the other similar diff for maverick-proposed; It took me a while to see why it was Forwarded: not-needed. The Origin header of the patch would usually tell me, but that just shows me where this file was added to Natty in a merge. Its fairly difficult to tell that this patch is just the differences for this file between 4.2.4 and 4.2.6, which the linked upstream bug report tells me is the revision in which the bug has been fixed. I don't see where our time will be used well by tracking that down much further, but I wanted to make it clear that this is not very straight forward. Given that, we need to see wide spread testing of this before it leaves -proposed. APPROVED: the package version 1:4.2.4p8+dfsg-1ubuntu2.1 uploaded to lucid-proposed should be accepted. APPROVED: the package version 1:4.2.4p8+dfsg-1ubuntu6.1 uploaded to maverick-proposed should be accepted. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/715152 Title: [SRU] ntp wont run on IPv6 only host unless lo has 127.0.0.1 address -- 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 765275] Re: metadata server cannot be contacted when deploying new instances on EUC
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 server cannot be contacted when deploying new instances on EUC -- 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
