On Tue, 2021-03-02 16:27:27 +0100, meskio <mes...@sindominio.net> wrote: > Quoting Jan-Benedict Glaw (2021-03-02 14:44:33) > > I do not think that SysV init has something to do with the SIGPIPE. > > It's probably being a close()d / shutdown()ed FD (at the browser side) > > while it tries to chunk-send data. > > > > However, with systemd you'd probably get a restart of laminard. You > > may observe a failed / missing run, but because daemon(1) won't do > > a restart, laminard dies for me without getting a recovery by restart. > > At least on my case this is not the problem. I see the laminard hasn't being > restarted in my server for the last 20 days, and I do run several jobs per > day > and some of them I do watch them while they play. But there might be > something > different on my setup. > > > > If you are able to test your laminar with systemd tell me if your problem > > > persist there. > > > > I'll try to pin down in which circumstances this actually happens. > > Good luck with it. If you don't find anything we can open an issue upstream, > Oliver is pretty responsive and helpful.
I had quite a few runs in parallel, and over the day it was like 700 or something in that order. The database was quite busy following stdout/stderr from all the builds and even watching the logs (or downloading them as a whole) took noticeable time. I guess it was in such a situation that GETs were aborted (tabs closed / reloaded). MfG, JBG --
signature.asc
Description: PGP signature
