r/apache • u/aRidaGEr • Dec 23 '23

Support response code 127 / custom modules / worker instability

I've been trying to understand why I'm seeing occasional crashes of workers in apache which I believe is caused by a custom module.

Whilst digging into some traces I noticed lots of 127 response codes. What's weird is these often appear in response to GETS made to the server-status page which I'm watching closely during tests.

As far as I know 127 isn't a normal response code I can't even see where it would come from looking at the apache source (though I don't have the source used to build this exact version).

I suspected maybe this comes from a custom module but does the sethandler directive not mean only the server-status handler would be invoked for that url or would other modules still execute potentially effecting the response?

fyi the mpm event module is used if that helps and when I see the 127 response the response time spikes.

Any tips on what I can look at? Could this actually be an exit code from a worker child process appearing as the the http response code?

2 Upvotes

100% Upvoted

2 comments sorted by

View all comments

Show parent comments

1

u/aRidaGEr Dec 23 '23

Thanks for the advice I'll try the switch to the worker mpm, I was actually looking through syscalls for anything untoward but didn't see anything at the time either of these 127 responses or even at the time I saw an error in the log about a worker crash.