502 bad gateway error


(Graham Chiu) #1

While I was overseas with no access to my Google compute instance (Great Firewall) I was advised of this error.

Maybe I had too many backups that were accumulating while I was away. But I followed the advice on previous reports but now although the 502 error has gone, I’m now getting no response.

So, I did a rebuild, cleanup and autoremove.

What information do I need to provide to help fix this?


(Bhanu Sharma) #2

I’m not quite sure what are you trying to fix here?

Too many backups? Considered using a storage provider to store backups? E.g. AWS S3/DO Spaces/Minio ??


(Graham Chiu) #3

I don’t get any errors on starting the docker instance using ./launcher start app but the webserver is no longer responding other than redirecting to https

$ wget http://127.0.0.1--2018-08-28 19:27:11-- [http://127.0.0.1/] (https://ssh.cloud.google.com/devshell/proxy?authuser=0&devshellProxyPath=%2F&port=null)Connecting to 127.0.0.1:80... connected.HTTP request sent, awaiting response... 301 Moved PermanentlyLocation: https://forum.rebol.info/ [following]--2018-08-28 19:27:11-- https://forum.rebol.info/Resolving forum.rebol.info (forum.rebol.info)... 35.196.220.213Connecting to forum.rebol.info (forum.rebol.info)|35.196.220.213|:443....

PS: If I use quoted text for the above, meta.discourse.org responds with a server error


(Graham Chiu) #4

This post says that there should be a redis log at /var/discourse/shared/standalone/log/var-log/redis but I’m not seeing the redis directory. The unicorn.stderr.log seems to be saying that it can’t connect to redis.

I, [2018-08-28T07:06:13.329585 #310]  INFO -- : master done reopening logs
I, [2018-08-28T07:06:13.371811 #482]  INFO -- : worker=0 done reopening logs
I, [2018-08-28T07:06:13.372877 #498]  INFO -- : worker=1 done reopening logs
I, [2018-08-28T07:06:14.315375 #310]  INFO -- : master reopening logs...
I, [2018-08-28T07:06:14.338814 #310]  INFO -- : master done reopening logs
I, [2018-08-28T07:06:14.339087 #482]  INFO -- : worker=0 reopening logs...
I, [2018-08-28T07:06:14.342471 #498]  INFO -- : worker=1 reopening logs...
I, [2018-08-28T07:06:14.376770 #498]  INFO -- : worker=1 done reopening logs
I, [2018-08-28T07:06:14.379761 #482]  INFO -- : worker=0 done reopening logs
Failed to report error: Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED) 2 Error connecting to Redi
s on localhost:6379 (Errno::ECONNREFUSED) subscribe failed, reconnecting in 1 second. Call stack ["/var/www/discours
e/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:344:in `rescue in establish_connection'", "/var/www/
discourse/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:329:in `establish_connection'", "/var/www/di
scourse/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:99:in `block in connect'", "/var/www/discourse
/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:291:in `with_reconnect'", "/var/www/discourse/vendor/
bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:98:in `connect'", "/var/www/discourse/vendor/bundle/ruby/2.4.
0/gems/redis-4.0.1/lib/redis/client.rb:363:in `ensure_connected'", "/var/www/discourse/vendor/bundle/ruby/2.4.0/gems
/redis-4.0.1/lib/redis/client.rb:219:in `block in process'", "/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/redis
-4.0.1/lib/redis/client.rb:304:in `logging'", "/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/redis-4.0.1/lib/redi

(Graham Chiu) #5

I installed redis-cli, but even on redis-cli ping I get a connection refused

$ redis-cli ping
Could not connect to Redis at 127.0.0.1:6379: Connection refused

Where can I find the redis log? it’s not where it’s supposed to be viz: /var/discourse/shared/standalone/log/var-log/redis