In EC2 platformdeployment is binding redis and PG on 127.0.0.0 after restarting the app server. about yelb HOT 8 CLOSED

Which of the two CFN templates are you using (standalone or distributed)? And what is the command you are launching to restart the app server?

from yelb.

Which of the two CFN templates are you using (standalone or distributed)? And what is the command you are launching to restart the app server?

I am using distributes cfn templates.
"ruby yelb-appserver.rb -o 0.0.0.0 & " this command I have used to restart the server.

from yelb.

You need to export the redis and postgres endpoints before you restart the yelb-appserver. This is how the launch of the appserver works in the CFN template.

You don't need to launch the startup script necessarily because that only tries to set the SEARCH_DOMAIN variable (that is used for other type of deployments) BUT you need to set the YELB_DB_SERVER_ENDPOINT and REDIS_SERVER_ENDPOINT variables.

from yelb.

I have run the two export commands from the command line,

export REDIS_SERVER_ENDPOINT=ip-172-x-x-x.ec2.internal
export YELB_DB_SERVER_ENDPOINT=ip-172-x-x-x.ec2.internal

and then executed the ruby script

ruby yelb-appserver.rb -o 0.0.0.0 &

But the app server still tries to connect to the Redis cache over 127.0.0.1:6379. It specifically fails for the api/getstats, api/pageviews, api/getvotes, etc.

Is there any specific configuration file to be updated? And, also where is the ruby log file located on the linux system?

Thanks in advance!

from yelb.

Ouch. My bad. The CFN template does NOT call the setup.sh script in the yelb-appserver folder. It calls another script (yelb-appserver.sh) in the Linux deployment folder. This script actually setup the app server on Linux.

You do NOT need to re-run the entire script because the code is already installed but you are probably only missing the setting of the RACK_ENV variable that is set to custom in that script (here).

This tells ruby to start the code and look for the variables you are exporting (here). Long story short, if you run these commands it should work:

export REDIS_SERVER_ENDPOINT=ip-172-x-x-x.ec2.internal
export YELB_DB_SERVER_ENDPOINT=ip-172-x-x-x.ec2.internal
export RACK_ENV="custom"
ruby /yelb-setup/yelb/yelb-appserver/yelb-appserver.rb -o 0.0.0.0 &

Can you try?

from yelb.

Hey, Thanks for inputs, we fixed that error.
But, We are still having an issue in connecting to Redis. It throws an Internal Server Error. Please find the screen capture of the issue that we have encountered.

from yelb.

Actually it worked now, we executed the commands in order and the app server is able to connect to Redis.

Thanks a lot for your assistance. It was of great help.

from yelb.

Excellent. Thanks for your patience!

from yelb.