Hi, Maxim Cournoyer <[email protected]> skribis:
> Looking at multiple of recent 'cannot build missing derivation' build > failures on Cuirass, I see for example: > > substitute: > substitute: [Kupdating substitutes from 'http://141.80.167.131'... 0.0% > substitute: [Kcould not fetch > http://141.80.167.131/rhgrs3ac6h64siz0krqh2ia8kkn3h6ym.narinfo 504 > substitute: updating substitutes from 'http://141.80.167.131'... 100.0% > cannot build missing derivation > ?/gnu/store/rhgrs3ac6h64siz0krqh2ia8kkn3h6ym-python-asdf-standard-1.0.3.drv? > > > So it seems the error originated from guix-publish being too heavily > under load to produce a timely reply, and the nginx proxy issued a 504 > (timeout) error response. > > Looking into /var/log/guix-publish.log for a corresponding entry, I > found: > > 2023-08-21 23:59:35 GET /rhgrs3ac6h64siz0krqh2ia8kkn3h6ym.narinfo > 2023-08-21 23:59:35 In web/server/http.scm: > 2023-08-21 23:59:35 159:7 2 (http-write #<<http-server> socket: > #<input-output: fi…> …) > 2023-08-21 23:59:35 In unknown file: > 2023-08-21 23:59:35 1 (put-bytevector #<input-output: socket 42> > #vu8(83 # …) …) > 2023-08-21 23:59:35 In ice-9/boot-9.scm: > 2023-08-21 23:59:35 1685:16 0 (raise-exception _ #:continuable? _) > 2023-08-21 23:59:35 In procedure fport_write: Broken pipe > > > So the connection was apparently severed (?), resulting in the "broken > pipe" error. I think it’s just that, when ‘guix publish’ eventually replied, the client had left, hence EPIPE. The initial problem does look like ‘guix publish’ being too slow. Do the corresponding nginx logs confirm the “backend too slow => 504” hypothesis? Thanks for investigating! Ludo’.
