Could you check the Apache error log to see what errors you get? Also if you set
define( 'WP_DEBUG', true );
in wp-config.php, you may get more info about what’s going on.
On the MySQL machine, check that mysqld is listening on port 3306. netstat -tan would show this.
On the second webserver machine make sure that DB_HOST in wp-config.php is set to the internal IP address of the MySQL machine or to the ec2-N-N-N-N… DNS name of the MySQL machine (which AWS knows to resolve to internal IP in such cases). If you use external IP (or your http://www.example.com DNS name) then you’d need to open port 3306 in the firewall which you’d want to avoid for security reasons (also you’ll get charged for traffic between the servers as it’s going through the external IPs).
Yeah, I checked the httpd logs under /var/log/httpd and there were no errors reported only the GET calls in access.log. I also made sure I could connect to the mysql instance running on the first instance from the second instance. Whats the best way to create the second instance? Should I create it from the “Launch Instance” in the installation instructions or should I make the second instance from the Amazon Console using the “Launch More Like This” option?
Either way works. In production, you’d probably want to create an AMI for the webtier, that is already configured and ready to launch.
I re-created the second EC2 instance by making a copy of the the first and here is the error I get after I enabled WP_DEBUG:
[Wed Feb 19 15:05:57 2014] [error] [client x.x.x.x] PHP Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /var/www/wordpress/wp-includes/functions.php on line 2919
That’s just a warning that wouldn’t make your site whitescreen. Do you still have the problem on the second webtier? If so, send email to support at oblaksoft dot com and someone will take a look at your config.
Thanks! Yes, I am still getting a whitescreen on the second webtier. I will submit the issue to oblaksoft support.
