VITAS changed the topic of #spacedock to: Problems?: https://github.com/KSP-SpaceDock/SpaceDock/issues | Matrix/Riot Chat: https://im.52k.de +spacedock:52k.de Feel free to ask for help, we only bite a little bit! | If you want to help, please check https://github.com/KSP-SpaceDock/SpaceDock-Backend/issues/5 :) | <VITAS> inet users have the attentionspan of a squirrel...
DasSkelett[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]> cool
<VITAS[m]> you could post on the forums and invite people to test it
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
DasSkelett[m] has joined #spacedock
<DasSkelett[m]> It's still running the production code, the alpha->beta PR hasn't been merged yet.
VITAS[m] has joined #spacedock
<VITAS[m]> i thought beta was all fixes we want to deploy from alpha
<VITAS[m]> if not can you see to that?
<DasSkelett[m]> Beta is still "untouched" yet. I only redid the config. Pinging <span class="d-mention d-user">HebaruSan</span> because we wrote about this the day before yesterday. He wasn't quite sure whether he may already merge the PR or not.
<VITAS[m]> cool thx for getting this going
DasSkelett[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
oeuf has joined #spacedock
egg has quit [Ping timeout: 198 seconds]
HebaruSan[m] has joined #spacedock
<HebaruSan[m]> OK, PR 242 merged, the beta branch now has the changes from alpha. Just need to pull them to the server and restart it.
<HebaruSan[m]> I've attempted the pull, but some stuff in alembic was chown'd wrong so it failed and requires cleanup, in progress...
<HebaruSan[m]> OK, pull done. Does anyone remember how to restart this thing?
<HebaruSan[m]> OK, I ran systemd-restart.sh, which did something, but now the load average is 60+ again
<HebaruSan[m]> Because we have a billion gunicorns
<HebaruSan[m]> Ugh
DasSkelett[m] has joined #spacedock
<DasSkelett[m]> Yep, encountered the same back then
<DasSkelett[m]> > I've set --workers 1 in spacedock@.service for the time being, someone knowing what he's doing can look into that later.
<DasSkelett[m]> So I solved it by editing the `./systemd/sapcedock@.service` and changing `--workers 6` to `--workers 1` in the `ExecStart` command.
<HebaruSan[m]> That worked!
<HebaruSan[m]> What features from alpha are easiest to confirm on the web site?
<HebaruSan[m]> I guess the footer hyperlink to Discord?
oeuf is now known as egg
<HebaruSan[m]> <span class="d-mention d-user">DasSkelett</span> can you see in the db whether I have a user account on beta?
<DasSkelett[m]> Yes, that footer is the new one (I used that one too everytime I had to check :P)
<DasSkelett[m]> Yep can check that, wait a minute
<HebaruSan[m]> Either that or upload your own test mod file so we can browse it
<DasSkelett[m]> No you don't have currently. Only me and VITAS (twice). You can create one and I can unlock it then to bypass the email verification which probably doesn't work still.
<HebaruSan[m]> Hmm, 500 error on trying to register
<HebaruSan[m]> [Thu Jan 23 23:40:13.446490 2020] [proxy_http:error] [pid 25612:tid 140385535833856] [client 10.150.1.9:35182] AH01114: HTTP: failed to make connection to backend: 127.0.0.1, referer: https://beta.spacedock.info/
<DasSkelett[m]> Same when trying to upload a mid...
<DasSkelett[m]> Same when trying to upload a mod...