Opened 5 years ago

Closed 4 years ago

#13491 closed enhancement (fixed)

Make a separate VM for check.tp.o

Reported by: arma Owned by: arlolra
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Right now Arlo's shiny new go version of check still runs on sergii, which is hard to upgrade because of tordnsel.

If I understand it correctly, check just needs to get a text file from tordnsel every hour.

If so, it sounds like we should separate the two services, so check can run on a normal VM with normal up-to-date versions of things.

Arlo, does this all sound right? If so, what level of resources would you want this new VM to have? I think all it would run is an apache front-end and your check backend.

Child Tickets

Change History (5)

comment:1 Changed 5 years ago by weasel

Do we know what kind of resources we need?

comment:2 in reply to:  description Changed 5 years ago by arlolra

Right now Arlo's shiny new go version of check still runs on sergii, which is hard to upgrade because of tordnsel.

Hard only because noone merged those patches way back when but let's ignore that for now. #9419

I started working on a replacement but haven't quite found the time to finish that up,
https://github.com/arlolra/exitaddr

If I understand it correctly, check just needs to get a text file from tordnsel every hour.

That's all it needs from TorDNSEL. It also needs the consensus and descriptors from tor.

If so, it sounds like we should separate the two services, so check can run on a normal VM with normal up-to-date versions of things.

The dependencies for the new VM should be listed on,
https://trac.torproject.org/projects/tor/wiki/org/operations/Guidelines
https://gitweb.torproject.org/check.git/blob/HEAD:/Readme.md#l50

Arlo, does this all sound right? If so, what level of resources would you want this new VM to have? I think all it would run is an apache front-end and your check backend.

Sounds good. I assume whatever resources are allocated to sergii currently are sufficient. It hasn't gone down yet and now that it isn't the homepage in Tor Browser, probably sees much less use.

It tried to get a better idea of the resources it's consuming but am getting,

λ ssh sergii
fork failed: Resource temporarily unavailable
ssh_exchange_identification: Connection closed by remote host
ssh_exchange_identification: Connection closed by remote host

and some of this,

λ ssh sergii
Permission denied (publickey).
ssh_exchange_identification: Connection closed by remote host

comment:3 Changed 5 years ago by arlolra

Ignore those ssh errors ... that was me not passing my username to the proxycommand.

comment:4 Changed 4 years ago by weasel

There is now a chiwui.torproject.org.

Please contact me if you need help setting up check there.

comment:5 Changed 4 years ago by weasel

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.