Custom Apache instance suddenly getting No space left on device

digitalmoksha

In the last couple of days I've stared getting the dreaded 502 Bad Gateway for my site. It is running a private Apache instance (setup from the instructions here), and has been chugging long fine for over a year.

The errors I'm getting from my privateApache_error.log are

[Mon Jul 11 14:58:21.053254 2022] [core:notice] [pid 50474:tid 140387429144704] SELinux policy enabled; httpd running as context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
[Mon Jul 11 14:58:21.075609 2022] [core:emerg] [pid 50481:tid 140387429144704] (28)No space left on device: AH00023: Couldn't create the proxy mutex
[Mon Jul 11 14:58:21.075665 2022] [proxy:crit] [pid 50481:tid 140387429144704] (28)No space left on device: AH02478: failed to create proxy mutex
[Mon Jul 11 14:58:21.075673 2022] [:emerg] [pid 50481:tid 140387429144704] AH00020: Configuration Failed, exiting

Doing a bin/restart produces the error consistently.

My plan has 200GB of space, and based on my account stats I've only used _168GB.

bin/start shows it's using /usr/sbin/httpd, and httpd.conf is loading modules from /usr/lib64/httpd/modules

Running on opal6. Any ideas, or should I open a private support ticket?

sean

digitalmoksha "no space left on device" can refer to other things like a lack of available inodes or IPC semaphores.

I don't see either of those happening on opal6 right now so if you're still seeing this issue then please do email support for assistance.

digitalmoksha

Just to wrap this thread up, it seems that there was a "problem with available IPC semaphores earlier today". It's cleared up and my site is jammin again. Thanks Sean!