Hi
Em qui., 7 de mar. de 2024 08:14, Mathias Radtke mailto:m.radtke@uib.de > escreveu:
Hi, me again.
So what I saw in the rep_server.log was
2024-03-07 10:14:13: [19782] maxchild limit reached
2024-03-07 10:14:13: maxchild limit reached
and on a worker itself
rpc failed: socket write: Connection timed out
sleeping one minute just in case...
send_statehttp://obs.uib.gmbh:5252 http://obs.uib.gmbh:5252 : rpc timeout
Any suggestion what I might do ?
Can you do a "curl -v http://obs.uib.gmbh:5252" from the worker? Maybe you're getting blocked traffic on either the worker or your main OBS?
So got this on server and worker before restarting the obsrepserver.service
obsworker2:~ # curl -vhttp://obs.uib.gmbh:5252
* Trying 192.168.109.101:5252...
* Connected to obs.uib.gmbh (192.168.109.101) port 5252 (#0)
> GET / HTTP/1.1
> Host: obs.uib.gmbh:5252
> User-Agent: curl/8.0.1
> Accept: */*
>
After restarting the obsrepserver.service I got this
obsworker2:~ # curl -vhttp://obs.uib.gmbh:5252
* Trying 192.168.109.101:5252...
* Connected to obs.uib.gmbh (192.168.109.101) port 5252 (#0)
> GET / HTTP/1.1
> Host: obs.uib.gmbh:5252
> User-Agent: curl/8.0.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/xml
< Cache-Control: no-cache
< Connection: close
< Content-Length: 43
<
<hello name="Package Repository Server" />
* Closing connection 0
This will now work for some time, worker finished packages will still end up in the rpc timeout.
Regards
Mathias