~lilmike

Recent activity

Re: build runner, dispatchers, and such 15 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

Ah ok, so just like I did it. I misunderstood and thought there was special ssh magic that would allow you to still have builds.sr.ht and git.sr.ht only installed on the web servers :-).
Thanks!
-Michael.





On Sun, Sep 29, 2019 at 12:55:15PM -0400, Drew DeVault wrote:
>Follow the git.sr.ht setup instructions for SSH - it should be fairly
>apparent from the config file. You'll want to add an entry for
>builds:builds=buildsrht-keys or something like that.

Re: build runner, dispatchers, and such 15 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

Ah, understandable. Mind giving a quick overview of how it's done so I can tinker with it?
-Michael.



On Sun, Sep 29, 2019 at 12:40:02PM -0400, Drew DeVault wrote:
>No, this is correct. We rely on gitsrht-dispatch to coordinate all SSH
>access to sr.ht. The SSH access to builds is still pretty new and I
>haven't gotten around to documenting its setup.

build runner, dispatchers, and such 15 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

So I was looking when setting up my build runner, and I couldn't help that notice that, to have ssh login to the runners working, you need to install not only builds.sr.ht-worker (for the building),
builds.sr.ht-images (for the images), but also builds.sr.ht itself (for buildsrht-shell and buildsrht-keys), and *also* git.sr.ht (for the dispatcher). I could easily be wrong, so please tell me if I
am, but shouldn't builds.sr.ht-worker be the one including the shell and keys, and shouldn't builds.sr.ht-worker include a dispatcher since the recommended way to run it is on a separate server from
your web servers?
Do I perhaps have some error in my configuration? Could there be a trick I'm missing?
Thanks!
-Michael.

docker setup 23 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

Hiya,
I'm getting closer to getting my build worker working. I think the current problem (hopefully the last) is that I can't get internet to the build environment. To this end, can someone explain the docker config necessary? I.E. do I need to change the docker ip from 172.x.y.z to 10.0.2.x or something else? Or am I just going about it wrong.
Thanks!
-Michael.

Re: redis for build.sr.ht and worker 24 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

Hiya,
I actually hadn't built the image of the docker image, but I did that now. I built an archlinux image and the qemu docker image, but it still won't run any queued tasks. I've tried debugging commands like celery -A buildsrht.runner status, and lots of others, and basically every one of them respondes "Error: No nodes replied within time constraint." I'm not quite sure what this means, maybe that the worker isn't actually looking for events, or maybe the build.sr.ht master server isn't  queuing them. But something's certainly off.
-Michael.





On Thu, Sep 19, 2019 at 06:26:44PM -0400, Drew DeVault wrote:
>Yes, that should be sufficient. Make sure you've built at least one
>image and you've set up the docker qemu container as well.

Re: redis for build.sr.ht and worker 25 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

Looks like libnss_dns is now at 2.29, so that's the error.
-Michael.




On Thu, Sep 19, 2019 at 06:26:44PM -0400, Drew DeVault wrote:
>Yes, that should be sufficient. Make sure you've built at least one
>image and you've set up the docker qemu container as well.

Re: redis for build.sr.ht and worker 25 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

Actually, that's probably the problem
Now, however, when I run the docker build command, I get:

Step 18/21 : COPY --from=0 /lib/x86_64-linux-gnu/libnss_dns-2.28.so /lib/x86_64-linux-gnu/
COPY failed: stat /var/lib/docker/overlay2/20fdde95899bc437fdd6e1b4927974328fcc4e05e6aca66f5ae4d07e78d82503/merged/lib/x86_64-linux-gnu/libnss_dns-2.28.so: no such file or directory




On Thu, Sep 19, 2019 at 06:26:44PM -0400, Drew DeVault wrote:
>Yes, that should be sufficient. Make sure you've built at least one
>image and you've set up the docker qemu container as well.

Re: redis for build.sr.ht and worker 25 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

One other thought: I might be missing something required to run along side the worker. Right now my master server has all the main services, and my worker machine has just the builds.sr.ht worker on it. They're both running arch, so master server has all of the sr.ht packages on it except worker, and the worker machine simply has worker and images. Is this right?
They also both have redis, and the worker has docker.
-Michael.




On Thu, Sep 19, 2019 at 05:37:54PM -0400, Drew DeVault wrote:
>On Thu Sep 19, 2019 at 2:37 PM Michael Taboada wrote:
>> They're definitely using the same database number and redis instance,
>> minus the fact that they have to connect to different ips (localhost
>> versus another).  Is there some command I can run, python, redis-cli,
>> something to see the list of queue tasks?
>

Re: redis for build.sr.ht and worker 25 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

They're definitely using the same database number and redis instance, minus the fact that they have to connect to different ips (localhost versus another).
Is there some command I can run, python, redis-cli, something to see the list of queue tasks?
-Michael.




On Thu, Sep 19, 2019 at 04:54:42PM -0400, Drew DeVault wrote:
>Make sure that the worker is reading the jobs from the same redis server
>& db that they're being submitted to (e.g. /0 vs /1).

Re: redis for build.sr.ht and worker 25 days ago

From Michael Taboada to ~sircmpwn/sr.ht-discuss

Hi,
On builds.2mb.codes it claims it queued two jobs from a git push, but the worker is not picking them up. All I'm getting in the systemd journal is "starting..." and "waiting for tasks..."
It can connect to the redis on the master server, and I see the connections (4 of them), but it isn't getting anything started. Any troubleshooting I can do here?
-Michael.




On Thu, Sep 19, 2019 at 04:21:31PM -0400, Drew DeVault wrote:
>The truth is that sr.ht uses Redis in a disorganized and shitty manner
>which is begging to be refactored. Basically, it's used for these
>things:
>
>1. Volatile data store for the web services, shared among all instances