-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apache with mod_neko hangs up on service reload #199
Comments
Are you using mpm prefork mode? It's the only mode that Neko supports. |
Server status page says I do. From the dockerfile I think that means you use mod_tora explicitly to handle requests:
I tested it out and, indeed, mod_tora works correctly with reload. But if I add this first line LoadModule neko..., it breaks. |
I can confirm this. I have an old project built on
|
As a quick fix in my case since it was behind nginx anyways, I've just started tora server in fcgi mode (the git version iirc) and configured nginx to use it to handle index.n and removed Apache altogether, hope that helps. |
Thanks, I'll probably do that as well. Normally I use nginx anyway nowadays. I installed apache just because of mod_neko. Does tora run reliably in fcgi mode? |
I find it very reliable, yes. Just make sure you have HaxeFoundation/tora#15 if you care about |
OK, I'll give it a try. Is it possible to use PUT as well with tora? |
Sorry about missing this comment @mockey. From the top of my mind, it should. But I confess to not knowing if there's isn't anyplace that's hardcoded to ignore PUTs. But if there are, they should be easy to fix. One thing that does come to mind though is that the only streaming API on the Haxe side is |
Will try this, thanks. |
I ran into this bug again after upgrading an old server. I suppose it won't get fixed, right? |
Clean Ubuntu 18.04 install with Apache 2.4.29 with mod_neko enabled. Using service reload hangs apache so I have to kill -9 it manually:
Removing mod_neko config files allows the Apache to reload correctly.
The text was updated successfully, but these errors were encountered: