Red Hat Bugzilla – Bug 901170
Apache with mod_cluster refuses to start (manager.node)
Last modified: 2015-03-11 01:18:31 EDT
Workaround Description: Disable UAC project_key: JBPAPP6 I think we have a similar problem like with: * [JBPAPP-7336] Apache with mod_cluster refuses to start (create_mem_node) With *UAC Enabled*, I am getting this error: {noformat} [Tue Nov 06 07:55:18 2012] [emerg] create_mem_node C:/tmp/jboss-ews-2.0/var/cache/mod_cluster/manager.node failed: Access is denied. Configuration Failed {noformat} * yes, the permissions are sufficient Strangely, the files actually *are being created*: {noformat} PS C:\tmp\jboss-ews-2.0\var\cache\mod_cluster> ls Directory: C:\tmp\jboss-ews-2.0\var\cache\mod_cluster Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 11/6/2012 7:55 AM 65536 manager.node.nodes -a--- 11/6/2012 7:55 AM 0 manager.node.nodes.lock {noformat} With *UAC Disabled*, the problem disappears and Apache starts normally.
Link: Added: This issue is related to JBPAPP-7336
Docs QE Status: Removed: NEW
This issue was marked with priority Major and since only Critical or Blocker issues are considered at this time, the issue is moved to TBD EAP 6. Should this be considered, please contact the EAP PM team.
Cause: On windows UAC prevents to create files and directories (a bit like SELinux), mod_cluster doesn't have any configuration script to configure UAC so it won't be able to create the shared memory associated with files in /var/cache/mod_cluster/ Consequence: httpd won't start. Workaround (if any): Disable UAC Result:
What should probably happen is that it doesn't put them in var/cache, but instead uses the Windows API to get a location it can write to under UAC. The C# API is: Environment.GetFolderPath(EnvironmentFolders.SpecialFolders.LocalApplicationData)
It has been concluded that this is a Windows administration error now. With a proper path set in MemManagerFile, there is no problem with UAC unless the user running Apache HTTP Server service presents ill configured permissions. This might happen especially in Domain Controlled environments, but it's definitely not our error. Domain Administrator must grant the proper Domain permissions so as UAC won't recognize MemManagerFile as a threat.