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...
<Darklight[m]> alpha autoupdated
<Darklight[m]> Beta autoupdating...
<Darklight[m]> Now I need to figure out where alpha and master differ
<Darklight[m]> Ok after a bit of digging the point of divergence is 27d5, so there is actually a handful of commits
<Darklight[m]> Can one of the gitty people cherry-pick or create a commit needed to pull this stuff in if you need to?
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]
DasSkelett[m] has joined #spacedock
VITAS[m] has joined #spacedock
<VITAS[m]> can you read this?
<VITAS[m]> bla
<VITAS[m]> and the link does to?
<VITAS[m]> seems like the problem is the relative path
<VITAS[m]> test
<DasSkelett[m]> Now, yes
<DasSkelett[m]> Looks like the bridge died
<DasSkelett[m]> One-way bridge
<DasSkelett[m]> Yes 😄
<DasSkelett[m]> It's pubkey authentication, and the one HebaruSan has on beta is probably not in allowed_keys of alpha
<DasSkelett[m]> So alpha is pulled and restarted <span class="d-mention d-user">VITAS</span> ?
<DasSkelett[m]> First want to test on alpha 🙂
<DasSkelett[m]> <span class="d-mention d-user">Darklight</span> can you check if alpha is updated?
<DasSkelett[m]> It should, but we don't know if it worked 😛
<DasSkelett[m]> Yep
<DasSkelett[m]> Getting `This is not a valid zip file.` when trying to upload now, looks like something else is needed.
<DasSkelett[m]> Yep, tuples should work
<DasSkelett[m]> Next PR is up 😛 I think I got all occurrences of `_save_mod_zipball`
<DasSkelett[m]> Nono, I actually do PRs, I want to give you the chance to have at least a very quick look 😄
<DasSkelett[m]> Okay, merging now 🤞
<DasSkelett[m]> Merged.
<DasSkelett[m]> Hmmm, not sure why we get this one, isn't this path correct? ?`The requested URL /content/DasSkelett_5/Test_download_path/Test_download_path-1.1.zip was not found on this server.`
<DasSkelett[m]> `GET https://spacedock.info/content/VITAS_150/SpaceLink/SpaceLink-1.0.zip` this is one from prod that works
<DasSkelett[m]> It's the same, isn't it?
<DasSkelett[m]> Oh, maybe the zip is saved in the wrong path now...
<DasSkelett[m]> Got it!
<DasSkelett[m]> It's redirecting from `alpha.spacedock.info` to `spacedock.info`
<DasSkelett[m]> This shouldn't affect us on production
<DasSkelett[m]> I fixed a few of these misdirections already I think. Seems there are still some hidden
<DasSkelett[m]> I'd say got for it, we're in the advertised downtime, the right link is returned (except the subdomain, irrelevant for prod) and works.
<DasSkelett[m]> Yes! It's quite nice!
<DasSkelett[m]> Testing right now
<DasSkelett[m]> IT WORKS!!!!
<DasSkelett[m]> Now <span class="d-mention d-user">Darklight</span> should re-check the DB real quick if any other mod sneaked in in the meantime
<DasSkelett[m]> Ah, good
<DasSkelett[m]> Yes, `www-data` needs a NOPASSWD
<DasSkelett[m]> Submitted a issue on GH to track the subdomain redirection problem. Will look into that when I got some time. If someone else wants t, you're welcome 😉
<DasSkelett[m]> Submitted a issue on GH to track the subdomain redirection problem. Will look into that when I got some time. If someone else wants to, you're welcome 😉
<DasSkelett[m]> Hmm, problem still exists. Either not restarted, or fix not fixing. Hoping and guessing first one.
HebaruSan[m] has joined #spacedock
<HebaruSan[m]> ```
<HebaruSan[m]> HebaruSan@sd2:~$ ssh sd6.srv.52k.de
<HebaruSan[m]> ssh: connect to host sd6.srv.52k.de port 22: Connection refused
<HebaruSan[m]> ```
<HebaruSan[m]> ```
<HebaruSan[m]> HebaruSan@sd2:~$ ssh sd6.52k
<HebaruSan[m]> ssh: connect to host sd6.52k port 22: Connection refused
<HebaruSan[m]> ```
<HebaruSan[m]> <span class="d-mention d-user">DasSkelett</span> it doesn't get to the auth stage:
<HebaruSan[m]> ```
<HebaruSan[m]> HebaruSan@sd2:~$ ssh -v -v -v sd6.52k
<HebaruSan[m]> OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017
<HebaruSan[m]> debug1: Reading configuration data /etc/ssh/ssh_config
<HebaruSan[m]> debug1: /etc/ssh/ssh_config line 19: Applying options for *
<HebaruSan[m]> debug2: resolving "sd6.52k" port 22
<HebaruSan[m]> debug2: ssh_connect_direct: needpriv 0
<HebaruSan[m]> debug1: Connecting to sd6.52k [10.150.1.52] port 22.
<HebaruSan[m]> debug1: connect to address 10.150.1.52 port 22: Connection refused
<HebaruSan[m]> ssh: connect to host sd6.52k port 22: Connection refused
<HebaruSan[m]> ```
<HebaruSan[m]> Ahh right the weird port number thing
<HebaruSan[m]> ```
<HebaruSan[m]> HebaruSan@sd2:~$ ssh sd6.srv.52k.de.:21352
<HebaruSan[m]> ssh: Could not resolve hostname sd6.srv.52k.de.:21352: Name or service not known
<HebaruSan[m]> HebaruSan@sd2:~$ ssh sd6.srv.52k.de:21352
<HebaruSan[m]> ssh: Could not resolve hostname sd6.srv.52k.de:21352: Name or service not known
<HebaruSan[m]> HebaruSan@sd2:~$ ssh sd6.52k:21352
<HebaruSan[m]> ssh: Could not resolve hostname sd6.52k:21352: Name or service not known
<HebaruSan[m]> ```
<HebaruSan[m]> OK, now it connects, but it wants my password. Off to see if I wrote it down somewhere...
<HebaruSan[m]> The previous commit might be dozens of commits fyi
<HebaruSan[m]> Well done team, sorry I couldn't pitch in. And thanks for keeping the latest changes, they're a big help for CKAN!
<HebaruSan[m]> I believe I can ssh to beta only
DasSkelett[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]> does prod behave normaly now?
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has joined #spacedock
<Darklight[m]> I believe so
<VITAS[m]> could you check?
<Darklight[m]> Having a rest, it tested fine then was moved to prod, I think it was skellet who has a testing mod on live spacedock
<Darklight[m]> I'll go through those commits when we are both around if they are important
<VITAS[m]> k
<VITAS[m]> thanks again for helping
<Darklight[m]> All good, alpha and beta now correctly autoupdate too
<Darklight[m]> Somewhere along the line ubuntu added /usr/bin/systemctl which takes preferece over /bin/systemctl
<Darklight[m]> Which broke sudo
<VITAS[m]> ah ok
<Darklight[m]> I just duplicated the sudo line, and beta had a broken secret
<Darklight[m]> Other than that it all is good
<VITAS[m]> grand
<Darklight[m]> I still would prefer master to represent production, but that means figuring out if those commits mean something ^
<Darklight[m]> And if they made their way back into alpha
<VITAS[m]> hmm i think there was a broken theme rebuild i did ways back?
<VITAS[m]> all i know is that prod diverged from actual master and we sort of backported prod into git
<VITAS[m]> you could deploy master on alpha to test thingst
<Darklight[m]> I took that screenshot, the highlighted one is the most common recent ancestor
<Darklight[m]> Well funding will just be "copy the file and commit it" I think, but the others may be actual patches that take integration if stuff changed
<Darklight[m]> If you are lucky you can just cherry pick it though
<Darklight[m]> Anyway, I'll be back later
<VITAS[m]> k
<VITAS[m]> have fun
<Darklight[m]> Also git --no-ff is the devil and github is terrible for it :P
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]