[SAC] [OSGeo] #2861: Setup woodie-client image and container on osgeo9

[OSGeo]

#2861: Setup woodie-client image and container on osgeo9
---------------------------+---------------------------------------
 Reporter:  robe           |       Owner:  sac@…
     Type:  task           |      Status:  reopened
 Priority:  normal         |   Milestone:  Sysadmin Contract 2023-I
Component:  Systems Admin  |  Resolution:
 Keywords:                 |
---------------------------+---------------------------------------
Changes (by robe):

 * status:  closed => reopened
 * resolution:  fixed =>

Comment:

 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)
-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2861#comment:3>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.