[UNSOLVED] GCloud : Failed to report error: Error connecting to Redis on localhost:6379

Looking to connect a Discourse app to a Google Cloud instance of a Rails app running redis and postgres ala How to deploy a Ruby Discourse app on Google Cloud. Have an instance of redis running on localhost and Google cloud configured through How to set up Redis on Compute Engine. Both seem to be connected. Went through entire process including pinging the server from the cloud instance and returning PONG.

Config file has also been altered as mentioned in the docs. When pushing the command

VERSION=$(date +%Y%m%dt%H%M%S); gcloud app deploy --version=$VERSION --promote && bundle exec rake appengine:exec -- bundle exec rake db:migrate && gcloud app services set-traffic default $VERSION=1

returning the following error and not sure where to go from here:

(Errno::ECONNREFUSED) 2 Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED) subscribe failed, reconnecting in 1 second. Call stack ["/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:344:in `rescue in establish_connection'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:328:in `establish_connection'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:99:in `block in connect'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:291:in `with_reconnect'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:98:in `connect'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:274:in `with_socket_timeout'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:131:in `call_loop'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/subscribe.rb:43:in `subscription'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/subscribe.rb:12:in `subscribe'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis.rb:2824:in `_subscription'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis.rb:2192:in `block in subscribe'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis.rb:45:in `block in synchronize'", "/opt/rbenv/versions/2.4.4/lib/ruby/2.4.0/monitor.rb:214:in `mon_synchronize'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis.rb:45:in `synchronize'", "/app/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis.rb:2191:in `subscribe'", "/app/vendor/bundle/ruby/2.4.0/gems/message_bus-2.1.6/lib/message_bus/backends/redis.rb:337:in `global_subscribe'", "/app/vendor/bundle/ruby/2.4.0/gems/message_bus-2.1.6/lib/message_bus.rb:533:in `global_subscribe_thread'", "/app/vendor/bundle/ruby/2.4.0/gems/message_bus-2.1.6/lib/message_bus.rb:481:in `block in new_subscriber_thread'"] 

Step #1: No connection to db, unable to retrieve site settings! (normal when running db:create)

Step #1: fatal: Not a git repository (or any of the parent directories): .git

Step #1: rake aborted!

What does this have to do with Discourse? :thinking:

2 Likes

Updated the question to be more specific regarding Discourse stack. Thought maybe someone in the Discourse team (or reading this) may have seen it before or know how to troubleshoot.