Public bug reported: Please see initial issue reported here:
http://open.eucalyptus.com/forum/walrus-configuration-failed-contact- server When running Walrus/S3 services of a different machine than the Cloud controller (CLC), we are missing some jar files. We seems to assume that the Walrus/S3 services are running out of the CLC by default. >From the earlier referenced page: "There is an issue, however, with starting standalone Eucalyptus components due to a missing file in the Ubuntu Karmic packages (we, the upstream, do not produce those packages). Try purging all eucalyptus packages, go through the steps again, then manually copy /usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar from the CLC host to /usr/share/eucalyptus on the Walrus host, run "stop eucalyptus" and then "start eucalyptus" on the Walrus host." Copying the /usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar to the walrus host fixes the problem. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- Missing jar file when Walrus/S3 runs on different host than CLC https://bugs.launchpad.net/bugs/516083 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
