-
Notifications
You must be signed in to change notification settings - Fork 859
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
Unable to run Apache with fcgid - cannot create shared memory #693
Comments
Thanks for reporting the issue, can you please share out a strace of the failing process so we can see what is failing? |
Is this what you need? Sorry, I'm not familiar with strace |
Thanks for collecting the trace. It looks like that only has the information for the parent process and it's likely a child process reporting the error above. Can you try the following command line to collect the child processes as well, |
Try this one. Thanks for looking in to this BTW. |
Glad to help, thanks for collecting the traces. Going through the strace it looks like the failure is coming from some socket options that aren't supported. I'll make sure we are tracking these socket options so we can prioritize appropriately. strace snip |
FWIW those first two errors appear without fcgid enabled and Apache still On 29 Jul 2016 11:52 PM, "stehufntdev" [email protected] wrote:
|
Just a thought but isn't shared memory (shm) support currently missing from WSL? |
Posix shared memory through /dev/shm should be working, but the system v shared memory system calls are not currently supported. In the strace I didn't see any hits for the system v syscalls. |
@stehufntdev, I am seeing the same problem on WSL (Windows 10 Home, version 1607). I successfully installed a simple apache2 configuration that seemed to work. I then tried to install the virtualmin webserver management platform - apache2 would not start due to the following errors:
I disabled slotmem_shm_module, socache_shmcb_module and auth_digest_module - now I get the same fcgid error as mstrelan. Another post suggested checking ipcs values - here is the response.
I will try switching to mod_php to see if that lets me continue configuring virtualmin. I realize I am asking a lot but it will be a good test of the WSL features. |
Do we have any updates with this? This issue hasn't been resolved yet with Build 16299. There are other things that require shared memory other than Apache and would help alleviate some error messages. |
Try using the Ubuntu release on the Windows Store. It can actually run along side the legacy release. |
@shinji257 I don't use the legacy release. I switched as soon as it was available on FCU. My specific notice of this issue actually is similar to this issue but it wasn't a permission error I was seeing. Strace will be posted as soon as I have time for it. |
I am not able to reproduce this issue on build 17074. Has anyone tried it recently? |
Gonna guess it was fixed with #1016 release 15002. |
I tried to reproduce this with the commands provided in the OP but Apache starts just fine. I can't believe I've been running WSL for 18 months already... seems this is fixed. |
It is, ref #1953. |
I'm trying to configure Apache to run with fcgid, but Apache won't start. I have tested this in a VM and it worked fine, but does not work in lxss.
After 20 seconds Apache fails to start and the following error appears in /var/log/apache2/error.log
I'm on build 14393.5.
I'm not too sure, but this might be related to #135.
The text was updated successfully, but these errors were encountered: