October 2011 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-263) Apache with mod_cluster refuses to start (create_mem_node)

by Michal Babacek (Updated) (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-263?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-263: -------------------------------------- Attachment: httpd.conf Attaching httpd conf. If you comment out Mod_cluster modules and configs at the bottom of that file, Apache httpd starts normally. > Apache with mod_cluster refuses to start (create_mem_node) > ---------------------------------------------------------- > > Key: MODCLUSTER-263 > URL: https://issues.jboss.org/browse/MODCLUSTER-263 > Project: mod_cluster > Issue Type: Bug > Environment: Windows 2008 R2 x86_64 > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Priority: Blocker > Attachments: httpd.conf > > > 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: > {code:java|title=httpd\\logs\\error_log} > [emerg] create_mem_node C:/tmp/work/httpd/logs/manager.node failed > Configuration Failed > {code} > 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: > {code:java|title=httpd\\logs} > 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 > {code} > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-263) Apache with mod_cluster refuses to start (create_mem_node)

by Michal Babacek (Updated) (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-263?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-263: -------------------------------------- Attachment: (was: httpd.conf) > Apache with mod_cluster refuses to start (create_mem_node) > ---------------------------------------------------------- > > Key: MODCLUSTER-263 > URL: https://issues.jboss.org/browse/MODCLUSTER-263 > Project: mod_cluster > Issue Type: Bug > Environment: Windows 2008 R2 x86_64 > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Priority: Blocker > Attachments: httpd.conf > > > 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: > {code:java|title=httpd\\logs\\error_log} > [emerg] create_mem_node C:/tmp/work/httpd/logs/manager.node failed > Configuration Failed > {code} > 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: > {code:java|title=httpd\\logs} > 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 > {code} > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-263) Apache with mod_cluster refuses to start (create_mem_node)

by Michal Babacek (Updated) (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-263?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-263: -------------------------------------- Description: 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: {code:java|title=httpd\\logs\\error_log} [emerg] create_mem_node C:/tmp/work/httpd/logs/manager.node failed Configuration Failed {code} 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: {code:java|title=httpd\\logs} 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 {code} 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. was: If you try to run httpd from [EWS 1.0.2_CR5-windows64-x86_64|http://download.devel.redhat.com/devel/candida...] with Mod_cluster modules from [EAP 5.1.2-ER1-windows64-x86_64|http://download.devel.redhat.com/devel/candida...] natives, you will encounter a failure: {code:java|title=Enterprise Web Server\\logs\\error_log} [emerg] create_mem_node C:/tmp/work/Red Hat/Enterprise Web Server/logs/manager.node failed Configuration Failed {code} 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: {code:java|title=Enterprise Web Server\\logs} C:\tmp\work\Red Hat\Enterprise Web Server\logs>ls access_log manager.node.nodes ssl_access_log ssl_request_log error_log manager.node.nodes.lock ssl_error_log {code} 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. > Apache with mod_cluster refuses to start (create_mem_node) > ---------------------------------------------------------- > > Key: MODCLUSTER-263 > URL: https://issues.jboss.org/browse/MODCLUSTER-263 > Project: mod_cluster > Issue Type: Bug > Environment: Windows 2008 R2 x86_64 > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Priority: Blocker > Attachments: httpd.conf > > > 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: > {code:java|title=httpd\\logs\\error_log} > [emerg] create_mem_node C:/tmp/work/httpd/logs/manager.node failed > Configuration Failed > {code} > 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: > {code:java|title=httpd\\logs} > 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 > {code} > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-263) Apache with mod_cluster refuses to start (create_mem_node)

by Michal Babacek (Moved) (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-263?page=com.atlassian.jira.pl... ] Michal Babacek moved JBPAPP-7337 to MODCLUSTER-263: --------------------------------------------------- Project: mod_cluster (was: JBoss Enterprise Application Platform) Key: MODCLUSTER-263 (was: JBPAPP-7337) Affects Version/s: (was: EAP_EWP 5.1.2 ER1) Component/s: (was: mod_cluster) Security: (was: Public) Fix Version/s: (was: EAP_EWP 5.1.2 ER2) Docs QE Status: (was: NEW) > Apache with mod_cluster refuses to start (create_mem_node) > ---------------------------------------------------------- > > Key: MODCLUSTER-263 > URL: https://issues.jboss.org/browse/MODCLUSTER-263 > Project: mod_cluster > Issue Type: Bug > Environment: Windows 2008 R2 x86_64 > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Priority: Blocker > Attachments: httpd.conf > > > If you try to run httpd from [EWS 1.0.2_CR5-windows64-x86_64|http://download.devel.redhat.com/devel/candida...] with Mod_cluster modules from [EAP 5.1.2-ER1-windows64-x86_64|http://download.devel.redhat.com/devel/candida...] natives, you will encounter a failure: > {code:java|title=Enterprise Web Server\\logs\\error_log} > [emerg] create_mem_node C:/tmp/work/Red Hat/Enterprise Web Server/logs/manager.node failed > Configuration Failed > {code} > 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: > {code:java|title=Enterprise Web Server\\logs} > C:\tmp\work\Red Hat\Enterprise Web Server\logs>ls > access_log manager.node.nodes ssl_access_log ssl_request_log > error_log manager.node.nodes.lock ssl_error_log > {code} > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (MODCLUSTER-262) Errors on Bean XML Configuration Updates

by Stefan Negrea (JIRA)

Errors on Bean XML Configuration Updates ----------------------------------------- Key: MODCLUSTER-262 URL: https://issues.jboss.org/browse/MODCLUSTER-262 Project: mod_cluster Issue Type: Bug Affects Versions: MOD_CLUSTER_1_0_10_GA_CP01 Reporter: Stefan Negrea Assignee: Jean-Frederic Clere Attachments: mod_cluster_eap_errors.log Any changes to the mod_cluster bean configuration xml file result in a bunch of errors in the log file and all the applications undeployed from the container. This basically renders the entire EAP instance useless until restart. I followed the installation documentation to setup mod_cluster on EAP 5.1.1. mod_cluster version: 1.0.10 (the version distributed with EAP 5.1.1) JBoss EAP 5.1.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues October 2011