Hi munix9, On Thu, 2026-05-21 at 18:42 +0200, munix9 wrote: > FYI: It looks like "x86_64" and "i586" are stuck. > > Packages are "stuck" in the "waiting queue" (and consequently, > a few more in the "blocked queue"). > > https://pmbs.links2linux.de/monitor/old > > thx.
This was not the case. For some time now I have a systemd timer, which checks the schedulers for their "fitness". If one of the scheduler processes is not there anymore, all architectures are restarted. Yesterday there was a common-mode problem with the workers, which occurred also in the past: To optimize the effective use of the available resources of CPU cores and RAM I modified the automatic calculation of the parameter OBS_INSTANCE_MEMORY in obsstoragesetup. In stock obs-server only about half the available RAM is used for the worker processes, which is rather a waste. Currently buildwk1 has 25GB and buildwk3 is configured with 32GB. My modification looks for the available amount of RAM, leaves 2GB for the VM, and divides the remaining RAM equally to the configured worker processes, a.k.a. number of CPUs in the VM. Additionally I respect the minimum maximal amount of RAM between NUMA nodes, if in effect. The effective amount of RAM differs slightly between kernel updates, so I could just calculate a value for OBS_INSTANCE_MEMORY sufficiently low and be done with it. Apart from PBMS I run two other build service installations, with completely different workers, which are created dynamically, with varying hardware specs. To optimize the use of resources I rely on the dynamic configuration of the workers. End of April support for openSUSE Leap 15.6 came to an end, and during March there was no installable stable release of obs for openSUSE Leap 16.0. At that time I resorted to installing the proposed alpha release 2.11 of obs, which gets updated several times a day occasionally. My modifications is a simple patch for /usr/sbin/obsstoragesetup, which I have to implement manually, as building a patched version of the obs- common package is not possible for me, as even the spec file is pulled from upstream git, so local patching is not possible. Thankfully since Apr 28th there is (or at least there was - I did not check right now) a installable stable 2.10 of obs for openSUSE Leap 16.0, so I could update PMBS to a supported OS - no, I do not consider Tumbleweed and Slowroll for local compliance reasons. I will try to downgrade the workers to the 2.10 stable, in the hope, that automatic updates do not occur to often, and I do not miss manually patching the obsstoragesetup script, leading to workers not building. Greetings, Stefan _______________________________________________ Packman mailing list [email protected] https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
