I just had the oddest experience doing a simple reboot of my Amazon Lightsail instance. Did the reboot… waited for restart. Got “502 Gateway Error - Nginx” error message screen on some (I assume uncached) pages). Waited a bit… Did a discourse rebuild via shell. Got an error message that rebuild fa…

It’s hard to tell from your description. What errors are you getting when you rebuild?

I try another update soon and update this. I didn’t save the log file and running updates spikes my burst zone pretty badly (especially after running it 3 times), so I needed to wait a day or so to get my burst levels back up.

This seems to be the culprit. Seeding default *** Bundling assets. This will take a while *** $ RUBY_GC_MALLOC_LIMIT_MAX=20971520 RUBY_GC_OLDMALLOC_LIMIT_MAX=20971520 RUBY_GC_HEAP_GROWTH_MAX_SLOTS=50000 RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=0.9 bundle exec rake themes:update assets:precompile Updat…

And now my forum is completely down and 500 erroring. :frowning: Why would that happen? I would have thought the update only replaces the current working forum once the process is finalized and doesn’t run into issues?

But isn’t dark a system theme component? How could a system theme component be causing that kind of issue? But thanks I will probably be able to fix the issue now that I know what’s going on.

The theme component is deprecated and Discourse refuses to use it. BUt if you do a ./launcher rebuild app then it takes down the container to build the new one (because it’s using the same database files). If the build fails, then you need to restart the container to get it running again.

Yeah I noted the update actually was complete on all the other elements once I deleted the Dark and Alternate Logos components everything was updated in the update screen.

Picchi CPU per aggiornamenti/ricompilazioni

Supporto Installazione

pfaffman (Jay Pfaffman) 7 Luglio 2021, 4:29pm 6

Non so quale fosse il tuo problema originale, ma questo è il problema attuale: Failed to Bootstrap, due to discourse-alt-logo theme component

Dovresti poter

 ./launcher start app

e poi eliminare il componente del tema difettoso.

Argomento		Risposte	Visualizzazioni
Precompiling assets takes 20 minutes Self-hosting server-resources	18	1331	Gennaio 31, 2024
Unable to start discourse due to rubygems rate limiting Support	45	3522	Dicembre 21, 2020
Update from 2.9.0 beta 3 to beta 4 failed - Site is down Self-hosting	9	563	Giugno 12, 2022
Updated latest beta (got warning about critical update), now Discourse won't start Self-hosting	6	139	Agosto 27, 2024
Update failing due to rate limiting by RubyGems Support	40	5798	Dicembre 18, 2020

Picchi CPU per aggiornamenti/ricompilazioni

Argomenti correlati