-
Bug
-
Resolution: Obsolete
-
Minor
-
None
-
None
-
None
-
None
-
One could set MemManagerFile to an allowed location on a particular system.
If you try to run httpd on windows64-x86_64 with Mod_cluster modules from 1.0.10.GA_CP02 natives, you will encounter a failure:
[emerg] create_mem_node C:/tmp/work/httpd/logs/manager.node failed Configuration Failed
On the other hand, if you comment out Mod_cluster modules (and configuration) from httpd.conf, httpd starts OK.
It is noteworthy that the aforementioned file, manager.node is really not present in the logs/ directory, however these files are:
C:\tmp\work\httpd\logs>ls access_log manager.node.nodes ssl_access_log ssl_request_log error_log manager.node.nodes.lock ssl_error_log
I would advocate that there is no Read/Write permission problem regarding the logs/ directory.
manager.node.nodes and manager.node.nodes.lock files were created by Mod_cluster.
- is cloned by
-
JBPAPP-7336 Apache with mod_cluster refuses to start (create_mem_node)
- Closed
- is duplicated by
-
JBPAPP-7336 Apache with mod_cluster refuses to start (create_mem_node)
- Closed
- is related to
-
MODCLUSTER-211 SE Linux in RHEL 6 does not support mod_cluster in the context of HTTPD
- Closed
-
MODCLUSTER-120 Apache with mod_cluster refuses to start at first, after 7 retries it starts up
- Closed