deploying grails app to the cloud foundry gives mysql errors

[ekkelenkamp]

Hi,

I tried to deploy a grails application using cloud foundry.
Uploading and Deployment seem to go just fine (all green button). But I don't seem to be able to access the web application.
There seems to be an issue with the mysql database. Any idea what might be wrong? I added the log file.

Thanx in advance,

Rudie.



---------------- START --------------
Executing command: Thu Aug 20 15:17:17 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: dos2unix|bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

5 46684 5 2557 0 0 10541 0 0:00:04 --:--:-- 0:00:04 10541
100 46684 100 46684 0 0 99810 0 --:--:-- --:--:-- --:--:-- 191k
copying aws to /usr/bin/
Stopping MySQL: [FAILED]
Shutting down postfix: [FAILED]
error reading information on service xvfb: No such file or directory
xvfb: unrecognized service
Stopping tomcat5:
Executing command: Thu Aug 20 15:17:19 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: dos2unix|bash
Executing command: Thu Aug 20 15:17:19 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: dos2unix|bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

5 46684 5 2557 0 0 20487 0 0:00:02 --:--:-- 0:00:02 20487
100 46684 100 46684 0 0 138k 0 --:--:-- --:--:-- --:--:-- 211k
copying aws to /usr/bin/
Stopping MySQL: [FAILED]
Shutting down postfix: [FAILED]
error reading information on service xvfb: No such file or directory
xvfb: unrecognized service
Stopping tomcat5:
Executing command: Thu Aug 20 15:17:20 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: dos2unix|bash
Executing command: Thu Aug 20 15:17:21 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: dos2unix|bash
Executing command: Thu Aug 20 15:17:21 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: dos2unix|bash
installing ...
Thank you for using SpringSource tc Server!
Executing command: Thu Aug 20 15:17:23 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: dos2unix|bash
Executing command: Thu Aug 20 15:17:24 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: /sbin/service mysqld stop
Stopping MySQL: [FAILED]
Executing command: Thu Aug 20 15:17:24 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: cat > /etc/my.cnf
Executing command: Thu Aug 20 15:17:24 EDT 2009 : ssh on ec2-67-202-55-241.compute-1.amazonaws.com: /sbin/service mysqld start
Initializing MySQL database: Installing MySQL system tables...
OK
Filling help tables...
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h domU-12-31-39-03-21-F3 password 'new-password'
See the manual for more instructions.
You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &

You can test the MySQL daemon with mysql-test-run.pl
cd mysql-test ; perl mysql-test-run.pl

[marceloverdijk]

I have exactly the same problem; at least the same symptom that I cannot access the application.

I couldn't understand why I wasn't able to access my Grails application.
After checking the log file Ifound out I had the same mysql error.

But I wonder if it's really related to mysql I would expect a different error.
Now I got just connection timeouts...

[marceloverdijk]

As I expected it was not related to mysql.

I needed to add HTTP port 80 (and HTTPS port 443) to my security group in the Amazon AWS Management Console.
Then it works like a charm.


Cheers,
Marcel
http://twitter.com/marceloverdijk

[ekkelenkamp]

Thanks. Opening port 80 did the trick!

[lallfr]

Hi guys,

I succeeded to retrieve my database connection parameters but I failed to create tables. I get this: Access denied for user 'username'@'%' to database 'aaaa'.

Does anyone can help ???

Regards.

[ceracm]

It looks like your log has been truncated when you posted it to the forum.
In any case, what is shown looks fine.
If you get all the way to a HEALTHY (Green) deployment then MySQL/tcServer/Apache are fine.
If you can't access the application then the most likely explanation is that you haven't opened port 80 in your default security group.

Chris