Unable to deploy guestbook on KVM test

5 views
Skip to first unread message

GNUton

unread,
Nov 2, 2009, 11:31:49 AM11/2/09
to AppScale Community
Hi,
I have to test (for job) a minimal testbed made by 4 Ubuntu 9.04 KVM
virtual machines and appscale. I have followed the wiki howto, doing
step-by-step the appscale_scratch_install_1.2.sh script.
Now I have builded everything and I can see my infrastructure status
browsing the frontend web-frontend. When I try to deploy guestbook app
using appscale-tools (running over the first appscale machine
(172.25.0.73) this is the only output:

$ appscale-run-instances --ips ips.yaml --file appscale-tools/
sample_apps/guestbook.tar.gz --table voldemort
Head node successfully created at 172.25.0.73. It is now starting up
voldemort via the command line arguments given.
Generating certificate and private key
Killing and starting server at 172.25.0.73
Please wait for the controller to finish pre-processing tasks.

This AppScale instance is linked to an e-mail address giving it
administrator privileges.
Enter your desired administrator e-mail address: f...@bar.org
Please repeat your e-mail address to verify: f...@bar.org

The new administrator password must be at least six characters long
and can include non-alphanumeric characters.
Enter your new password:
Enter again to verify:
Please wait for AppScale to prepare your machines for use.
Done starting up AppScale, now in heartbeat mode

On the other machines I can see GOD running, but the app stay there
until timeout error begins.

Now I am trying to patch ruby with http://appscale.googlecode.com/files/patch-ruby-1.8.7-p72
but I cannot find an indication to apply this patch.

My versions are:
$ ruby -v
ruby 1.8.7 (2008-08-11 patchlevel 72) [x86_64-linux]
$ python -V
Python 2.6.2

Any suggestions?

Simone

PS: Sorry for my worst english :-)

Chris Bunch

unread,
Nov 2, 2009, 11:38:58 AM11/2/09
to AppScale Community
Hi Simone,
What happens if you do a run-instances in the exact fashion you did
earlier but adding on the -v flag? It should spit out more useful
output and produce a file /tmp/172.25.0.73.log on your head node (here
it appears to be 172.25.0.73). If you could e-mail me that log file
instead of posting it directly to the mailing list, I should be able
to fish out any specific error messages and post them back here for us
all to look at (and in case anyone in the future has a similar problem
this should be the most helpful for them).

Thanks,
> Now I am trying to patch ruby withhttp://appscale.googlecode.com/files/patch-ruby-1.8.7-p72
Reply all
Reply to author
Forward
0 new messages