March 3, 20251 yr Hi, have looked at a few similar threads but don't seem to be able to track it back to any of those specific cases - similar symptoms though in that after some period (say 2 - 12 hours) my server becomes unresponsive, first to GUI, then SSH becomes extremely laggy (60 seconds + responses) or fails to connect at all, requiring a hard reset. Things I have tried: - Downgrading to 6.x.x (previous version from 7.0.0) - still happened - Running in safe mode - seemed to help, but given intermittency, hard to say for sure - Removing a bunch of plugins that I wasn't really using - Running extended SMART on all drives now as I saw a few errors in the logs, but given the weird degradation, doesn't seem to be as "binary" as I'd assume a disk failure would be? My next step would probably be to run in safe mode and spin up plugins and docker containers one by one, but given that I'd need to leave it for say 24 hours to be sure, that's at least 15 days' effort, so be good to know if there's anything obvious to try first. Diagnostics file attached, any advice on where to start probing (after SMART tests all finish) would be much appreciated servesup-diagnostics-20250303-1525.zip
March 3, 20251 yr Community Expert Mar 3 15:09:40 servesup php-fpm[5719]: [WARNING] [pool www] child 952448 exited on signal 9 (SIGKILL) after 11.866721 seconds from start Mar 3 15:10:34 servesup php-fpm[5719]: [WARNING] [pool www] child 952508 exited on signal 9 (SIGKILL) after 53.102297 seconds from start Mar 3 15:10:35 servesup php-fpm[5719]: [WARNING] [pool www] child 952562 exited on signal 9 (SIGKILL) after 42.619271 seconds from start Mar 3 15:10:38 servesup php-fpm[5719]: [WARNING] [pool www] child 952684 exited on signal 9 (SIGKILL) after 27.408115 seconds from start Mar 3 15:10:47 servesup php-fpm[5719]: [WARNING] [pool www] child 952777 exited on signal 9 (SIGKILL) after 13.073427 seconds from start In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM, could also be docker containers hogging the server, see if happens with docker disabled, or try pinning only some cores to them.
March 4, 20251 yr Author Thanks for that - I've been a bit suspicious of my docker image for a little while - was ballooning in size for reasons I couldn't figure out (all the paths seemed sound). I've done a rebuild of that, will keep an eye on memory and see if there's a difference.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.