September 2013 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-363) Rather unsettling warnings in Solaris build logs

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-363?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-363: ------------------------------------------------ libtool: install: warning: remember to run `libtool --finish /tmp/xbroot/ROOT/lib64/httpd/modules' "mod_manager.c", line 576: warning: assignment type mismatch: pointer to function(pointer to struct request_rec {pointer to struct apr_pool_t {..} pool, pointer to struct conn_rec {..} connection, pointer to struct server_rec {..} server, pointer to struct request_rec {..} next, pointer to struct request_rec {..} prev, pointer to struct request_rec {..} main, pointer to char the_request, int assbackwards, int proxyreq, int header_only, pointer to char protocol, int proto_num, pointer to const char hostname, long request_time, pointer to const char status_line, int status, pointer to const char method, int method_number, long allowed, pointer to struct apr_array_header_t {..} allowed_xmethods, pointer to struct ap_method_list_t {..} allowed_methods, long sent_bodyct, long bytes_sent, long mtime, int chunked, pointer to const char range, long clength, long remaining, long read_length, int read_body, int read_chunked, unsigned int expecting_100, pointer to struct apr_table_t {..} headers_in, pointer to struct apr_table_t {..} headers_out, pointer to struct apr_table_t {..} err_headers_out, pointer to struct apr_table_t {..} subprocess_env, pointer to struct apr_table_t {..} notes, pointer to const char content_type, pointer to const char handler, pointer to const char content_encoding, pointer to struct apr_array_header_t {..} content_languages, pointer to char vlist_validator, pointer to char user, pointer to char ap_auth_type, int no_cache, int no_local_copy, pointer to char unparsed_uri, pointer to char uri, pointer to char filename, pointer to char canonical_filename, pointer to char path_info, pointer to char args, struct apr_finfo_t {..} finfo, struct apr_uri_t {..} parsed_uri, int used_path_info, pointer to struct ap_conf_vector_t {..} per_dir_config, pointer to struct ap_conf_vector_t {..} request_config, pointer to const struct htaccess_result {..} htaccess, pointer to struct ap_filter_t {..} output_filters, pointer to struct ap_filter_t {..} input_filters, pointer to struct ap_filter_t {..} proto_output_filters, pointer to struct ap_filter_t {..} proto_input_filters, int eos_sent}) returning void "=" pointer to void libtool: install: warning: remember to run `libtool --finish /tmp/xbroot/ROOT/lib64/httpd/modules' libtool: install: warning: remember to run `libtool --finish /tmp/xbroot/ROOT/lib64/httpd/modules' "mod_advertise.c", line 810: warning: argument #5 is incompatible with prototype: prototype: pointer to const void : "/tmp/xbroot/ROOT/include/httpd/ap_provider.h", line 50 argument : pointer to function(pointer to struct request_rec {pointer to struct apr_pool_t {..} pool, pointer to struct conn_rec {..} connection, pointer to struct server_rec {..} server, pointer to struct request_rec {..} next, pointer to struct request_rec {..} prev, pointer to struct request_rec {..} main, pointer to char the_request, int assbackwards, int proxyreq, int header_only, pointer to char protocol, int proto_num, pointer to const char hostname, long request_time, pointer to const char status_line, int status, pointer to const char method, int method_number, long allowed, pointer to struct apr_array_header_t {..} allowed_xmethods, pointer to struct ap_method_list_t {..} allowed_methods, long sent_bodyct, long bytes_sent, long mtime, int chunked, pointer to const char range, long clength, long remaining, long read_length, int read_body, int read_chunked, unsigned int expecting_100, pointer to struct apr_table_t {..} headers_in, pointer to struct apr_table_t {..} headers_out, pointer to struct apr_table_t {..} err_headers_out, pointer to struct apr_table_t {..} subprocess_env, pointer to struct apr_table_t {..} notes, pointer to const char content_type, pointer to const char handler, pointer to const char content_encoding, pointer to struct apr_array_header_t {..} content_languages, pointer to char vlist_validator, pointer to char user, pointer to char ap_auth_type, int no_cache, int no_local_copy, pointer to char unparsed_uri, pointer to char uri, pointer to char filename, pointer to char canonical_filename, pointer to char path_info, pointer to char args, struct apr_finfo_t {..} finfo, struct apr_uri_t {..} parsed_uri, int used_path_info, pointer to struct ap_conf_vector_t {..} per_dir_config, pointer to struct ap_conf_vector_t {..} request_config, pointer to const struct htaccess_result {..} htaccess, pointer to struct ap_filter_t {..} output_filters, pointer to struct ap_filter_t {..} input_filters, pointer to struct ap_filter_t {..} proto_output_filters, pointer to struct ap_filter_t {..} proto_input_filters, int eos_sent}) returning void libtool: install: warning: remember to run `libtool --finish /tmp/xbroot/ROOT/lib64/httpd/modules' libtool: install: warning: remember to run `libtool --finish /tmp/xbroot/ROOT/lib/httpd/modules' "mod_manager.c", line 576: warning: assignment type mismatch: pointer to function(pointer to struct request_rec {pointer to struct apr_pool_t {..} pool, pointer to struct conn_rec {..} connection, pointer to struct server_rec {..} server, pointer to struct request_rec {..} next, pointer to struct request_rec {..} prev, pointer to struct request_rec {..} main, pointer to char the_request, int assbackwards, int proxyreq, int header_only, pointer to char protocol, int proto_num, pointer to const char hostname, long long request_time, pointer to const char status_line, int status, pointer to const char method, int method_number, long long allowed, pointer to struct apr_array_header_t {..} allowed_xmethods, pointer to struct ap_method_list_t {..} allowed_methods, long long sent_bodyct, long long bytes_sent, long long mtime, int chunked, pointer to const char range, long long clength, long long remaining, long long read_length, int read_body, int read_chunked, unsigned int expecting_100, pointer to struct apr_table_t {..} headers_in, pointer to struct apr_table_t {..} headers_out, pointer to struct apr_table_t {..} err_headers_out, pointer to struct apr_table_t {..} subprocess_env, pointer to struct apr_table_t {..} notes, pointer to const char content_type, pointer to const char handler, pointer to const char content_encoding, pointer to struct apr_array_header_t {..} content_languages, pointer to char vlist_validator, pointer to char user, pointer to char ap_auth_type, int no_cache, int no_local_copy, pointer to char unparsed_uri, pointer to char uri, pointer to char filename, pointer to char canonical_filename, pointer to char path_info, pointer to char args, struct apr_finfo_t {..} finfo, struct apr_uri_t {..} parsed_uri, int used_path_info, pointer to struct ap_conf_vector_t {..} per_dir_config, pointer to struct ap_conf_vector_t {..} request_config, pointer to const struct htaccess_result {..} htaccess, pointer to struct ap_filter_t {..} output_filters, pointer to struct ap_filter_t {..} input_filters, pointer to struct ap_filter_t {..} proto_output_filters, pointer to struct ap_filter_t {..} proto_input_filters, int eos_sent}) returning void "=" pointer to void libtool: install: warning: remember to run `libtool --finish /tmp/xbroot/ROOT/lib/httpd/modules' libtool: install: warning: remember to run `libtool --finish /tmp/xbroot/ROOT/lib/httpd/modules' "mod_advertise.c", line 810: warning: argument #5 is incompatible with prototype: prototype: pointer to const void : "/tmp/xbroot/ROOT/include/httpd/ap_provider.h", line 50 argument : pointer to function(pointer to struct request_rec {pointer to struct apr_pool_t {..} pool, pointer to struct conn_rec {..} connection, pointer to struct server_rec {..} server, pointer to struct request_rec {..} next, pointer to struct request_rec {..} prev, pointer to struct request_rec {..} main, pointer to char the_request, int assbackwards, int proxyreq, int header_only, pointer to char protocol, int proto_num, pointer to const char hostname, long long request_time, pointer to const char status_line, int status, pointer to const char method, int method_number, long long allowed, pointer to struct apr_array_header_t {..} allowed_xmethods, pointer to struct ap_method_list_t {..} allowed_methods, long long sent_bodyct, long long bytes_sent, long long mtime, int chunked, pointer to const char range, long long clength, long long remaining, long long read_length, int read_body, int read_chunked, unsigned int expecting_100, pointer to struct apr_table_t {..} headers_in, pointer to struct apr_table_t {..} headers_out, pointer to struct apr_table_t {..} err_headers_out, pointer to struct apr_table_t {..} subprocess_env, pointer to struct apr_table_t {..} notes, pointer to const char content_type, pointer to const char handler, pointer to const char content_encoding, pointer to struct apr_array_header_t {..} content_languages, pointer to char vlist_validator, pointer to char user, pointer to char ap_auth_type, int no_cache, int no_local_copy, pointer to char unparsed_uri, pointer to char uri, pointer to char filename, pointer to char canonical_filename, pointer to char path_info, pointer to char args, struct apr_finfo_t {..} finfo, struct apr_uri_t {..} parsed_uri, int used_path_info, pointer to struct ap_conf_vector_t {..} per_dir_config, pointer to struct ap_conf_vector_t {..} request_config, pointer to const struct htaccess_result {..} htaccess, pointer to struct ap_filter_t {..} output_filters, pointer to struct ap_filter_t {..} input_filters, pointer to struct ap_filter_t {..} proto_output_filters, pointer to struct ap_filter_t {..} proto_input_filters, int eos_sent}) returning void libtool: install: warning: remember to run `libtool --finish /tmp/xbroot/ROOT/lib/httpd/modules' > Rather unsettling warnings in Solaris build logs > ------------------------------------------------ > > Key: MODCLUSTER-363 > URL: https://issues.jboss.org/browse/MODCLUSTER-363 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.6.Final > Environment: Solaris sparc, x86 > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Fix For: 1.2.7.Final > > > Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. > Bugspotter: [~vtunka] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-361) session affinity not maintained when multiple balancers are used on 1.0.10.GA_CP

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-361?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-361. -------------------------------------------- Resolution: Done merged > session affinity not maintained when multiple balancers are used on 1.0.10.GA_CP > -------------------------------------------------------------------------------- > > Key: MODCLUSTER-361 > URL: https://issues.jboss.org/browse/MODCLUSTER-361 > Project: mod_cluster > Issue Type: Bug > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04 > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > Session affinity not maintained when multiple balancers are used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-363) Rather unsettling warnings in Solaris build logs

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-363?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-363: -------------------------------------- Description: Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. Bugspotter: [~vtun] was:Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. > Rather unsettling warnings in Solaris build logs > ------------------------------------------------ > > Key: MODCLUSTER-363 > URL: https://issues.jboss.org/browse/MODCLUSTER-363 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.6.Final > Environment: Solaris sparc, x86 > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Fix For: 1.2.7.Final > > > Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. > Bugspotter: [~vtun] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-363) Rather unsettling warnings in Solaris build logs

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-363?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-363: -------------------------------------- Description: Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. Bugspotter: [~vtunka] was: Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. Bugspotter: [~vtun] > Rather unsettling warnings in Solaris build logs > ------------------------------------------------ > > Key: MODCLUSTER-363 > URL: https://issues.jboss.org/browse/MODCLUSTER-363 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.6.Final > Environment: Solaris sparc, x86 > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Fix For: 1.2.7.Final > > > Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. > Bugspotter: [~vtunka] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-363) Rather unsettling warnings in Solaris build logs

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-363?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-363: -------------------------------------- Description: Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. (was: Configure and compilation steps e.g. in [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] build.) > Rather unsettling warnings in Solaris build logs > ------------------------------------------------ > > Key: MODCLUSTER-363 > URL: https://issues.jboss.org/browse/MODCLUSTER-363 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.6.Final > Environment: Solaris sparc, x86 > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Fix For: 1.2.7.Final > > > Configure and compilation steps e.g. in these builds: [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] and [mod_cluster-solaris10-x86|https://jenkins.mw.lab.eng.bos.redhat.com/hudso...]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-363) Rather unsettling warnings in Solaris build logs

by Michal Babacek (JIRA)

Michal Babacek created MODCLUSTER-363: ----------------------------------------- Summary: Rather unsettling warnings in Solaris build logs Key: MODCLUSTER-363 URL: https://issues.jboss.org/browse/MODCLUSTER-363 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.6.Final Environment: Solaris sparc, x86 Reporter: Michal Babacek Assignee: Jean-Frederic Clere Fix For: 1.2.7.Final Configure and compilation steps e.g. in [mod_cluster-solaris10-sparc64|https://jenkins.mw.lab.eng.bos.redhat.com/h...] build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-362) configuration example for simple-load-provider has wrong attribute

by Vittorio Rigamonti (JIRA)

Vittorio Rigamonti created MODCLUSTER-362: --------------------------------------------- Summary: configuration example for simple-load-provider has wrong attribute Key: MODCLUSTER-362 URL: https://issues.jboss.org/browse/MODCLUSTER-362 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.0.Final Reporter: Vittorio Rigamonti Assignee: Jean-Frederic Clere The configuraton example in the gray box here: http://docs.jboss.org/mod_cluster/1.2.0/html/java.AS7config.html#SimpleLo... shoud be: <simple-load-provider factor="1"/> instead of <simple-load-provider load="1"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-361) session affinity not maintained when multiple balancers are used on 1.0.10.GA_CP

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-361?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-361: ------------------------------------ Git Pull Request: https://github.com/modcluster/mod_cluster/pull/43 > session affinity not maintained when multiple balancers are used on 1.0.10.GA_CP > -------------------------------------------------------------------------------- > > Key: MODCLUSTER-361 > URL: https://issues.jboss.org/browse/MODCLUSTER-361 > Project: mod_cluster > Issue Type: Bug > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04 > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > Session affinity not maintained when multiple balancers are used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-361) session affinity not maintained when multiple balancers are used on 1.0.10.GA_CP

by Aaron Ogburn (JIRA)

Aaron Ogburn created MODCLUSTER-361: --------------------------------------- Summary: session affinity not maintained when multiple balancers are used on 1.0.10.GA_CP Key: MODCLUSTER-361 URL: https://issues.jboss.org/browse/MODCLUSTER-361 Project: mod_cluster Issue Type: Bug Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04 Reporter: Aaron Ogburn Assignee: Jean-Frederic Clere Session affinity not maintained when multiple balancers are used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-356) BalancerMember directives cause httpd crash when using mod_cluster 1.2.x

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-356?page=com.atlassian.jira.pl... ] Weinan Li edited comment on MODCLUSTER-356 at 9/16/13 10:11 AM: ---------------------------------------------------------------- Yeah if I restart httpd it will always throw: {code} Error null sending STATUS command to min/10.0.1.13:10001, configuration will be reset: null {code} And here is the log from httpd: {code} [Mon Sep 16 22:04:51 2013] [notice] Apache/2.2.25 (Unix) mod_ssl/2.2.25 OpenSSL/1.0.1e mod_cluster/1.2.6.Final configured -- resuming normal operations [Mon Sep 16 22:04:55 2013] [warn] manager_handler STATUS error: MEM: Can't read node [Mon Sep 16 22:04:56 2013] [warn] manager_handler STATUS error: MEM: Can't read node [Mon Sep 16 22:05:05 2013] [notice] Balancer other-server-group changed [Mon Sep 16 22:05:06 2013] [notice] Balancer other-server-group changed [Mon Sep 16 22:05:06 2013] [notice] Balancer other-server-group changed [Mon Sep 16 22:05:06 2013] [notice] Balancer other-server-group changed [Mon Sep 16 22:05:06 2013] [notice] Balancer other-server-group changed [Mon Sep 16 22:05:08 2013] [notice] Balancer other-server-group changed [Mon Sep 16 22:05:09 2013] [notice] Balancer other-server-group changed [Mon Sep 16 22:05:09 2013] [notice] Balancer other-server-group changed {code} If I access the cluster it will throw 503 error: {code} min:~ weinanli$ telnet 10.0.1.13 80 Trying 10.0.1.13... Connected to mini. Escape character is '^]'. GET / <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Temporarily Unavailable</title> </head><body> <h1>Service Temporarily Unavailable</h1> <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p> </body></html> Connection closed by foreign host. min:~ weinanli$ {code} And the log reported by httpd: {code} [Mon Sep 16 22:05:46 2013] [error] proxy: CLUSTER: (balancer://other-server-group). All workers are in error state [Mon Sep 16 22:05:46 2013] [error] proxy: CLUSTER: (balancer://other-server-group). All workers are in error state [Mon Sep 16 22:05:47 2013] [error] proxy: CLUSTER: (balancer://other-server-group). All workers are in error state {code} I could see the nodes are registered from mod_cluster-management: {code} mod_cluster/1.2.6.Final Auto Refresh show DUMP output show INFO output Node 770b156a-97b5-372f-9750-717824bf9aed (ajp://10.0.1.19:8009): Enable Contexts Disable Contexts Balancer: other-server-group,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 1,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 100 Node 30b18166-b3c4-3388-8fbe-50af073c7657 (ajp://10.0.1.13:8009): Enable Contexts Disable Contexts Balancer: other-server-group,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 1,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 100 {code} So I believe when httpd start up all the nodes are in error state because of that STATUS error: {code} manager_handler STATUS error: MEM: Can't read node {code} was (Author: weinanli): Yeah if I restart httpd/EAP sometimes it will throw: {code} Error null sending STATUS command to min/10.0.1.13:10001, configuration will be reset: null {code} And this just happen during server restart to me. The httpd crashing stopped after I've upgrade mod_cluster to 1.2.6.Final in httpd. No crashing anymore, and no error log from both EAP and httpd sides, and node could be seen correctly from '/mod_cluster-manager'. From wireshark analyse the CPING/CPONG of AJP port between EAP/httpd are fine. But the "<title>503 Service Temporarily Unavailable</title>" still exists. The node is not serving. I've also tried to upgrade mod_cluster in EAP side also to 1.2.6.Final and the problem still there. Not sure where the problem could be. Because Wireshark doesn't understand the MCMP in 10001 port, so it's hard for me to see if there are any problems. > BalancerMember directives cause httpd crash when using mod_cluster 1.2.x > ------------------------------------------------------------------------ > > Key: MODCLUSTER-356 > URL: https://issues.jboss.org/browse/MODCLUSTER-356 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.4.Final > Environment: SLES-11-SP1 x86_64 running httpd 2.2.24 or 2.4.6 with any mod_cluster-1.2.x version and JBoss-AS-7.2.0.Final > Reporter: Marco Danti > Assignee: Jean-Frederic Clere > Labels: balancerMember, crash, httpd, mod_cluster > > httpd dumps core in mod_proxy_cluster.c if the httpd.conf file contains BalancerMember directives. > this happens at least with the following two setups: > 1) httpd-2.4.6 and mod_cluster-1.2.x > 2) httpd-2.2.24 and mod_cluster-1.2.3.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues September 2013