[Bug 584048] Re: kvm images losing connectivity w/bridged network
This morning I had an freeze also. The virtualized Hardy was freezed. (Host is Lucid-AMD64 on Xenons) The virtualized Lucid was running fine. (on same Host) The virtualized Dapper was running fine also (same Host). The Hardy is on-production Server Ouch! Ouch! Ouch! "I hate mondays" -- kvm images losing connectivity w/bridged network https://bugs.launchpad.net/bugs/584048 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 573436] Re: PHP Deprecated: Comments starting with '#' are deprecated in /etc/php5/cli/conf.d/ldap.ini on line 1 in Unknown on line 0
The following worked for me: cd /etc/php5/cli/conf.d sudo perl -pi.bk -e 's/(\s*)#/\1;/' *ini sudo mkdir bk sudo mv *.bk bk Which only catches comments at the start of a line; also, backups of the original files are in the /etc/php5/cli/conf.d/bk directory. -- PHP Deprecated: Comments starting with '#' are deprecated in /etc/php5/cli/conf.d/ldap.ini on line 1 in Unknown on line 0 https://bugs.launchpad.net/bugs/573436 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 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 607039] Re: NFS automount failover doesn't work
** Attachment added: "/etc/autofs.d/auto.vcs that the auto.master file refers to" http://launchpadlibrarian.net/52140619/auto.vcs -- NFS automount failover doesn't work https://bugs.launchpad.net/bugs/607039 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 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 607039] Re: NFS automount failover doesn't work
** Attachment added: "auto.master file" http://launchpadlibrarian.net/52140589/auto.master -- NFS automount failover doesn't work https://bugs.launchpad.net/bugs/607039 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 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 607039] Re: NFS automount failover doesn't work
** Attachment added: "strace output" http://launchpadlibrarian.net/52140531/strace-autofs-and-kids.txt -- NFS automount failover doesn't work https://bugs.launchpad.net/bugs/607039 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 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 607039] [NEW] NFS automount failover doesn't work
Public bug reported: Binary package hint: autofs5 In lucid, using autofs5 version 5.0.4-3.1ubuntu5, we are having trouble using failover with NFS. Autofs allows you to specify multiple hosts with weighting in its configuration files and will fall back to a secondary host if the first host is not available at mount time. However, currently on our systems, the mount fails completely. This functionality does work with our RHEL 5 hosts (which use autofs 5.0.1). Automounting from a single host does work, but when we supply multiple hosts, an strace shows that it's trying to connect to the IP address '0.0.0.0', port 0, rather than any of the hosts we specify. I have attached the full strace output, our /etc/auto.master file, and the relevant file from /etc/autofs.d including the multiple hosts. ** Affects: autofs5 (Ubuntu) Importance: Undecided Status: New -- NFS automount failover doesn't work https://bugs.launchpad.net/bugs/607039 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 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 573919] Re: autofs doesn't work with lucid
If you look in /etc/init/portmap.conf you will see that its prerequisite for starting is statd which is done in /etc/init/portmap.conf. However, there are numerous errors in my /var/log/boot.log file. I upgraded two machines and both have the same issue as mentioned above. A new install I did does not have this issue, so it obviously is some config issues that is going badly when upgrading. I was originally fixing this issue by stopping then starting portmap again. (A restart didn't work.) I have found this in my /var/log/boot.log file: init: statd main process (730) terminated with status 1 init: statd main process ended, respawning init: statd main process (736) terminated with status 1 init: statd main process ended, respawning init: statd main process (747) terminated with status 1 init: statd main process ended, respawning init: statd main process (754) terminated with status 1 init: statd main process ended, respawning init: rpc_pipefs pre-start process (703) terminated with status 32 init: statd main process (764) terminated with status 1 init: statd main process ended, respawning init: statd main process (770) terminated with status 1 init: statd main process ended, respawning init: statd main process (776) terminated with status 1 init: statd main process ended, respawning init: statd main process (782) terminated with status 1 init: statd main process ended, respawning init: statd main process (788) terminated with status 1 init: statd main process ended, respawning init: statd main process (794) terminated with status 1 init: statd main process ended, respawning init: statd main process (800) terminated with status 1 init: statd respawning too fast, stopped -- autofs doesn't work with lucid https://bugs.launchpad.net/bugs/573919 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs 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 604802] Re: Merge commons-io 1.4-3 (main) from Debian unstable (main)
Please note in the bug when you've forwarded a patch to Debian. It makes sponsors start the review happy :) Err, I'm not a main sponsor, but I think this can be synced, given that Debian has changed their java policy here and reject the ubuntu dependancy changes.. -- Merge commons-io 1.4-3 (main) from Debian unstable (main) https://bugs.launchpad.net/bugs/604802 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to commons-io 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 606953] [NEW] debian /etc/init.d/eucalyptus-cloud needs help
Public bug reported: JAVA_HOME was set to "/usr", just because $ ls -l /usr/bin/java lrwxrwxrwx 1 root root 22 May 26 17:01 /usr/bin/java -> /etc/alternatives/java and not directly to anything in # ls -l /usr/lib/jvm total 12 lrwxrwxrwx 1 root root 14 May 17 14:55 default-java -> java-6-openjdk lrwxrwxrwx 1 root root 18 May 17 14:55 java-1.5.0-gcj -> java-1.5.0-gcj-4.4 drwxr-xr-x 6 root root 4096 Jul 8 22:23 java-1.5.0-gcj-4.4 lrwxrwxrwx 1 root root 14 May 17 14:55 java-1.6.0-openjdk -> java-6-openjdk drwxr-xr-x 7 root root 4096 May 26 15:55 java-6-openjdk lrwxrwxrwx 1 root root 19 May 26 17:00 java-6-sun -> java-6-sun-1.6.0.20 drwxr-xr-x 8 root root 4096 May 26 17:00 java-6-sun-1.6.0.20 lrwxrwxrwx 1 root root 12 May 17 14:55 java-gcj -> java-gcj-4.4 lrwxrwxrwx 1 root root 18 May 17 14:55 java-gcj-4.4 -> java-1.5.0-gcj-4.4 But independent from that observation, it should be noted that the structure of the code is erroneous. The lower half of the following patch improves the situation. For the upper half, a readlink to /usr/lib/jvm/default-java, if existing, to seed JAVA_HOME would however possibly be preferable. This was spotted in the debian 1.6.2 packages but might also apply to Ubuntu's. Steffen --- eucalyptus-cloud.orig 2010-07-16 16:18:48.0 +0200 +++ eucalyptus-cloud2010-07-16 16:43:55.0 +0200 @@ -189,17 +189,36 @@ # to be sure we are using the right java/JAVA_HOME JAVA="$JAVA_HOME/jre/bin/java" - - # let's see if we can find a decent java - if [ -x "$JAVA" ]; then - java_version=`$JAVA -version 2>&1 | grep "java version" | sed -e 's/.*java version "\(.*\)".*/\1/'` - if [ `expr $java_version "<" $java_min_version` -eq 0 ]; then - export JAVA_HOME - return + for relpath in "jre/bin" bin; do + JAVA="$JAVA_HOME/$relpath/java" + if [ -x "$JAVA" ]; then + break; fi + done + + if [ "x$JAVA" == "x" ]; then + echo "Could not find Java executable underneath JAVA_HOME determined as $JAVA_HOME" + exit 1 + fi + + # version check + + java_version=`$JAVA -version 2>&1 | grep "java version" | cut -f2 -d\"` + if [ -z "$java_version" ]; then + echo "Failed to determine Java version in init script." + exit 1 + else + echo "Java version is '$java_version'" + fi + if [ `expr $java_version "<" $java_min_version` -eq 0 ]; then + export JAVA_HOME + return + else + echo "Eucalyptus needs java version >= $java_min_version, found version \"$java_version\" of \"$JAVA\"" + exit 1 fi - echo "Eucalyptus needs java version >= $java_min_version" + echo "Error in init.d/eucaluptus-cloud, this statement should not be reached." exit 1 } ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- debian /etc/init.d/eucalyptus-cloud needs help https://bugs.launchpad.net/bugs/606953 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 603363] Re: sshd never stops, prevents umount of /usr partition
Will the fix also be released for Lucid or only for future versions of Ubuntu? -- sshd never stops, prevents umount of /usr partition https://bugs.launchpad.net/bugs/603363 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 606908] [NEW] euca-describe-availability-zones verbose returns EC2ResponseError: 403 Forbidden in Ubuntu 10.04
Public bug reported: i've done this on Ubuntu 10.04: $ . ̃/.euca/eucarc $ euca−describe−availability−zones verbose but result was: Warning: failed to parse error message from AWS: :1:0: syntax error EC2ResponseError: 403 Forbidden Failure: 403 Forbidden my cloud controller has 2 network interfaces: eth0: 192.168.1.30/24; dg: 192.168.1.254; dns:192.168.1.254 eth1: 192.168.20.1/24 and my cluster controller is set with: eth0: 192.168.20.2/24 /// i can't ping 192.168.20.1 or 192.168.20.2 from client, is it the reason of this issue? (cause i'm fallowing a guide on this) and there's no "DEADLOCK" or "Resetting" on my "cloud-output.log" file. i did an upgrade but problem still exist. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- euca-describe-availability-zones verbose returns EC2ResponseError: 403 Forbidden in Ubuntu 10.04 https://bugs.launchpad.net/bugs/606908 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 606898] Re: package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
** Attachment added: "AptOrdering.txt" http://launchpadlibrarian.net/52118868/AptOrdering.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52118869/Dependencies.txt ** Attachment added: "Df.txt" http://launchpadlibrarian.net/52118870/Df.txt ** Attachment added: "Dmesg.txt" http://launchpadlibrarian.net/52118871/Dmesg.txt ** Attachment added: "DpkgTerminalLog.txt" http://launchpadlibrarian.net/52118872/DpkgTerminalLog.txt -- package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 https://bugs.launchpad.net/bugs/606898 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 606898] [NEW] package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
Public bug reported: Binary package hint: postfix ivtv drivers would not install. ivtv-utils although the software center now reports it is installed. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: postfix 2.7.0-1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Jul 18 09:54:12 2010 ErrorMessage: subprocess installed post-installation script returned error exit status 75 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) SourcePackage: postfix Title: package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- package postfix 2.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 https://bugs.launchpad.net/bugs/606898 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 606630] Re: package vsftpd 2.2.2-3ubuntu6 failed to install/upgrade:
*** This bug is a duplicate of bug 530832 *** https://bugs.launchpad.net/bugs/530832 for the record, this is the error: Installing new version of config file /etc/vsftpd.conf ... Installing new version of config file /etc/logrotate.d/vsftpd ... Installing new version of config file /etc/pam.d/vsftpd ... vsftpd user (ftp) already exists, doing nothing. chown: invalid group: `root:ftp' dpkg: error processing vsftpd (--configure): subprocess installed post-installation script returned error exit status 1 So it is, indeed, the same as bug 530832. -- package vsftpd 2.2.2-3ubuntu6 failed to install/upgrade: https://bugs.launchpad.net/bugs/606630 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd 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
