Opened 2 years ago

Last modified 11 months ago

#2861 reopened task

Setup woodie-client image and container on osgeo9

Reported by: robe Owned by: sac@…
Priority: normal Milestone: Sysadmin Contract 2024-I
Component: SysAdmin Keywords: woodie
Cc:

Description

So I have woodie-server running on osgeo8 and also installed woodpecker client in that server.

Need another client. I'll create a repo for thaton gitea to track the details for setting up future clients.

I'll start with using the ubuntu-220docker image I created (which is used for woodie-server).

Change History (6)

comment:1 by robe, 16 months ago

Milestone: UnplannedSysadmin Contract 2023-I
Resolution: fixed
Status: newclosed

Done. I started setting one up on osgeo8 and reduced the one that is part of woodie-server to just one run. The others are set to 4.

Config details here: https://git.osgeo.org/gitea/sac/osgeo8/wiki/woodie-client

and the agent configuration is here - https://git.osgeo.org/gitea/sac/woodpecker-agent-config

The tricky part was proxying gRPC traffic thru nginx and setting true for GRPC.

This should also keep the size of woodie-server low since the bulk of the growth is caused by runs that failed or were canceled and left dead containers behind.

comment:2 by robe, 16 months ago

Also created a woodie-client on osgeo4

comment:3 by robe, 16 months ago

Resolution: fixed
Status: closedreopened

Reopening because the grpc requests seem to be hit or miss:

When I check the docker logs on one of the clients using:

 docker logs osgeo-woodie-agent -f

I'm seeing a lot of

{"level":"error","error":"rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); transport: received unexpected content-type \"text/html\"","time":"2023-07-31T01:23:08Z","message":"grpc error: log(): code: Unavailable: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); transport: received unexpected content-type \"text/html\""}

But yet the osgeo8 and osgeo9 and osgeo4 woodie-clients are working as I can see a trisquel3 live container running even when these errors are showing. So might be something like i need to allocate more worker threads for agent.woodie.osgeo.org site (which I have set to use grpc on the https port)

comment:4 by strk, 16 months ago

Keywords: woodie added

The osgeo4 client is failing with the same error (html received instead of expected grpc)

comment:5 by strk, 16 months ago

I'd suggest to raise the osgeo8 number of agent processes back up to 4 until this problem is fixed

comment:6 by robe, 11 months ago

Milestone: Sysadmin Contract 2023-ISysadmin Contract 2024-I

Moving my prior still open items to the next proposed Milestone

Note: See TracTickets for help on using tickets.