No AI replies. GitHub or StackOver flow profile required. Please - Rhd, Centos to Alma 9 .. migrate on DO solve FUTEX CPU spiral CraKER Unix ONly Sys
Budget: €18 – €36 EUR
No AI replies. GitHub or StackOver flow profile required. Please - Rhd, Centos to Alma 9 .. migrate on DO solve FUTEX CPU spiral CraKER Unix ONly Sys
I’m moving a production droplet on DigitalOcean from an ageing RHEL/CentOS build to AlmaLinux 9 and, at the same time, must eliminate a stubborn FUTEX spin that periodically drives CPU usage to the ceiling and starves the database server.
Here’s what I need done:
• Build or convert the droplet to Alma 9 with the same package set and security hardening already in place.
• Trace and resolve the FUTEX spiral so the database process returns to normal, stable utilisation.
• Hand back a fully patched system, clean boot logs and updated configs (systemd units, SELinux, firewalld) that survive a reboot without manual intervention.
Acceptance checks
– top / perf / strace show no runaway FUTEX waits after 24 h under load.
– Database queries complete within their usual SLA.
– All existing services start cleanly on Alma 9.
Please include a link to your public GitHub or Stack Overflow profile when you reply. I’m only interested in hands-on Unix/Linux engineers who can demonstrate real-world kernel or glibc debugging experience. Automated or AI-generated pitches will be ignored.
I’m moving a production droplet on DigitalOcean from an ageing RHEL/CentOS build to AlmaLinux 9 and, at the same time, must eliminate a stubborn FUTEX spin that periodically drives CPU usage to the ceiling and starves the database server.
Here’s what I need done:
• Build or convert the droplet to Alma 9 with the same package set and security hardening already in place.
• Trace and resolve the FUTEX spiral so the database process returns to normal, stable utilisation.
• Hand back a fully patched system, clean boot logs and updated configs (systemd units, SELinux, firewalld) that survive a reboot without manual intervention.
Acceptance checks
– top / perf / strace show no runaway FUTEX waits after 24 h under load.
– Database queries complete within their usual SLA.
– All existing services start cleanly on Alma 9.
Please include a link to your public GitHub or Stack Overflow profile when you reply. I’m only interested in hands-on Unix/Linux engineers who can demonstrate real-world kernel or glibc debugging experience. Automated or AI-generated pitches will be ignored.