Help! Upgrade constantly fails We recently upgraded servers on Google Cloud Console. Not sure this is related, but since then we’ve hit lots of 502 errors. It seems that infrequently updates such as for official theme components and themes can be pulled, and at times they return 502 after around 30-sec. Using safe mode it also works most of the time, but not always. We updated the docker, then got a message we must re-build via SSH. Then we constantly get a failure and have to revert to an image backup → ….. oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 129:C 22 Mar 2023 13:00:10.162 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=129, just started 129:C 22 Mar 2023 13:00:10.162 # Configuration loaded 129:M 22 Mar 2023 13:00:10.162 * monotonic clock: POSIX clock_gettime 129:M 22 Mar 2023 13:00:10.163 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use 129:M 22 Mar 2023 13:00:10.163 # Failed listening on port 6379 (TCP), aborting. Updating files: 100% (32972/32972), done. I, [2023-03-22T13:00:11.909015 #1] INFO -- : HEAD is now at 59e548540 Build(deps): Bump sass from 1.58.3 to 1.59.2 in /app/assets/javascripts (#20656) I, [2023-03-22T13:00:11.909217 #1] INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git clean -f I, [2023-03-22T13:00:12.001100 #1] INFO -- : I, [2023-03-22T13:00:12.001244 #1] INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse bash -c ' if [ $(git rev-parse --is-shallow-repository) == "true" ]; then git remote set-branches --add origin main git remote set-branches origin tests-passed git fetch --depth 1 origin tests-passed else git fetch --prune --prune-tags origin tests-passed fi [[[[[…. Timeout here -> and exit with an error ]]]]] fatal: unable to access 'https://github.com/discourse/discourse.git/': gnutls_handshake() failed: Error in the pull function. I, [2023-03-20T10:54:29.239940 #1] INFO -- : I, [2023-03-20T10:54:29.240283 #1] INFO -- : Terminating async processes I, [2023-03-20T10:54:29.240310 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 41 I, [2023-03-20T10:54:29.240342 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 102 2023-03-20 10:54:29.240 UTC [41] LOG: received fast shutdown request 2023-03-20 10:54:29.242 UTC [41] LOG: aborting any active transactions 2023-03-20 10:54:29.244 UTC [41] LOG: background worker "logical replication launcher" (PID 50) exited with exit code 1 2023-03-20 10:54:29.245 UTC [45] LOG: shutting down 2023-03-20 10:54:29.268 UTC [41] LOG: database system is shut down

If anyone has even a slight idea I’d really appreciate it!

[image] sok: fatal: unable to access 'https://github.com/discourse/discourse.git/': gnutls_handshake() failed: Error in the pull function. There appears to be a problem with git in the Docker container being able to access github.com.

That’s exactly what I thought, but I have no idea why it would fail? At times it work, and so I was able to update the docker to the latest version. But then re-build fails all the time, and sometimes even installing an official theme fails.

If I were you I’d get a shell in the Docker container and try to debug accessing https://github.com/ from there.

I just checked again and it does download the update from git but fails at the end… pretty lost here! Any advice would be extremely appreciated.

Continuing the discussion here as it’s the same issue and there is advice :slight_smile: [image] Issue when installing new Discourse instance Self-hosting Hello Everyone, When trying to install a new instance of discourse, I’m getting this error (here is my install log): Configuration file at containers/app.yml updated successfully! Updates successful. Rebuilding in 5 seconds. Building app x86_64 arch detected. Ensuring launcher is up to date Fetching origin Launcher is up-to-date 2.0.20230313-1023: Pulling from discourse/base Digest: sha256:f7467469ab9e39c3548d4478e3f416c05b34a0ee58eb6e40b963e562005669cc Status: Image is up to date for discour…

Help! Upgrade constantly fails

Product Support Self-hosting

chrisc (Chris Croome) March 23, 2023, 1:10pm 3

There appears to be a problem with git in the Docker container being able to access github.com.

Topic		Replies	Views
Cant upgrade on /admin/upgrade/ due to failed internet connectivity Product Support	3	577	October 29, 2019
502: Bad Gateway after web update Product Support	17	5957	December 16, 2019
Cannot upgrade due to old version of docker Self-hosting	4	1726	June 19, 2018
The forum is down after clicking on update! Product Support	7	1836	November 4, 2020
Site down: 502 Bad Gateway - after update Self-hosting	2	1245	September 24, 2018

Help! Upgrade constantly fails

Related topics