October 2016 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-448) mod_cluster crashes apache thread if multiple nodes report the same AJP connect string

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-448?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-448: ------------------------------------------- Fix Version/s: 1.3.5.Final (was: 1.3.4.Final) > mod_cluster crashes apache thread if multiple nodes report the same AJP connect string > -------------------------------------------------------------------------------------- > > Key: MODCLUSTER-448 > URL: https://issues.jboss.org/browse/MODCLUSTER-448 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.2.6.Final > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Fix For: 1.2.14.Final, 1.3.5.Final > > > Reported on behalf of [Toby Murray|https://github.com/ToeBee]: > Tracking issue #[138|https://github.com/modcluster/mod_cluster/issues/138] > Let's carry on with any discussion here, on JIRA... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-430) CreateBalancers behave the same with option 0 or 2

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-430?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-430: ------------------------------------------- Fix Version/s: 1.3.5.Final (was: 1.3.4.Final) > CreateBalancers behave the same with option 0 or 2 > -------------------------------------------------- > > Key: MODCLUSTER-430 > URL: https://issues.jboss.org/browse/MODCLUSTER-430 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final, 1.2.9.Final > Environment: RHEL 6.4.0 > Apache HTTPD 2.4.10 > JBoss 6.1.1 > Mod_cluster 1.3.0 Final > Reporter: John Jerome > Assignee: Michal Karm Babacek > Fix For: 1.2.14.Final, 1.3.5.Final > > > The directive CreateBalancers with directive 0 or 2 creates the balancers on all httpd vhosts. > With option 2, the balancers should be created on the main server only, not in the vhosts. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-450) Reenable testMulticastSocketNoCrossTalk test

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-450?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-450: ------------------------------------------- Fix Version/s: 1.3.5.Final (was: 1.3.4.Final) > Reenable testMulticastSocketNoCrossTalk test > -------------------------------------------- > > Key: MODCLUSTER-450 > URL: https://issues.jboss.org/browse/MODCLUSTER-450 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.3.1.Beta2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.5.Final > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-460) Silence superflous "MODCLUSTER000033: Failed to interrupt socket reception" on shutdown

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-460?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-460: ------------------------------------------- Fix Version/s: 1.3.5.Final (was: 1.3.4.Final) > Silence superflous "MODCLUSTER000033: Failed to interrupt socket reception" on shutdown > --------------------------------------------------------------------------------------- > > Key: MODCLUSTER-460 > URL: https://issues.jboss.org/browse/MODCLUSTER-460 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 1.3.5.Final > > > This seems to be caused by the legacy code in mod_cluster, which could instead make use of interruptible channels introduced since JDK 1.4. Simpler option would be log this message onto debug. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-501) mod_proxy_cluster crash when using BalancerMember

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-501?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-501: ------------------------------------------- Fix Version/s: 1.3.5.Final (was: 1.3.4.Final) > mod_proxy_cluster crash when using BalancerMember > ------------------------------------------------- > > Key: MODCLUSTER-501 > URL: https://issues.jboss.org/browse/MODCLUSTER-501 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final > Environment: o.s.:: CentOS Linux release 7.2.1511 > httpd 2.4.6 > mod cluster 1.3.1 final > Reporter: Paolo Lutterotti > Assignee: Michal Karm Babacek > Fix For: 1.3.5.Final > > Attachments: httpd.conf, modules.txt, vhost.conf, vhost.conf > > > Hello, > I'm experiencing an issue very similar to https://issues.jboss.org/browse/MODCLUSTER-356 > When I try to use a BalancerMember directive, I get a segmentation fault, caused at line https://github.com/modcluster/mod_cluster/blob/1.3.1.Final/native/mod_pro... > I tried to remove directives from the virtual host, but the issue persists until there is at least one ProxyPass using a balancer defined with BalancerMember. I attach a .conf file where I put all of the configurations involved in the issue and which is causing the crash. > If I put a check at line 2223, there are no more segmentations, but a 503 caused by mod_proxy_cluster.c(2332): proxy: byrequests balancer FAILED > Thanks, > Paolo -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-505) ProxyErrorOverride=On causes workers in error state after 500 errors

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-505?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-505: ------------------------------------------- Fix Version/s: 1.3.5.Final (was: 1.3.4.Final) > ProxyErrorOverride=On causes workers in error state after 500 errors > --------------------------------------------------------------------- > > Key: MODCLUSTER-505 > URL: https://issues.jboss.org/browse/MODCLUSTER-505 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.12.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > Fix For: 1.2.14.Final, 1.3.5.Final > > > When a VirtualHost uses ProxyPass to proxy traffic to the backend and uses ProxyErrorOverride to host custom error pages on Apache httpd side, when the backend replies with a 50x error code mod_proxy/mod_cluster marks that worker as down, breaking session stickiness. This behaviour is quite similar to have failonstatus=500 for example. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-508) &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-508?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-508: ------------------------------------------- Fix Version/s: 1.3.5.Final (was: 1.3.4.Final) > &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful > ------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-508 > URL: https://issues.jboss.org/browse/MODCLUSTER-508 > Project: mod_cluster > Issue Type: Enhancement > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.13.Final > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Trivial > Fix For: 1.3.5.Final > > > While we compare balancers URL char by char, we start at index 11, because > the default beginning: {{balancer://}} is always there. It would be nice to change 11 to a named constant so as it is clear why it's 11 without debugger :) -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-526) SIGSEGV in remove_workers_node (mod_proxy_cluster.so) when using LoadBalancingGroup

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-526?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-526: ------------------------------------------- Fix Version/s: 1.3.5.Final (was: 1.3.4.Final) > SIGSEGV in remove_workers_node (mod_proxy_cluster.so) when using LoadBalancingGroup > ----------------------------------------------------------------------------------- > > Key: MODCLUSTER-526 > URL: https://issues.jboss.org/browse/MODCLUSTER-526 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.3.Final > Environment: Fedora 20, x86_64, httpd 2.4.20 mpm_event > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Blocker > Fix For: 1.3.5.Final > > > h3. Setup > * 3 tomcats > * 2 load balancing groups > * 1 request every 3 seconds (no load at all) > * shutdown and kill of various nodes > * no later than third kill/start iteration causes SIGSEGV > h3. SIGSEGV > {code} > #if AP_MODULE_MAGIC_AT_LEAST(20101223,1) > /* Here that is tricky the worker needs shared memory but we don't and CONFIG will reset it */ > helper->index = 0; /* mark it removed */ > worker->s = helper->shared; > crash---> memcpy(worker->s, stat, sizeof(proxy_worker_shared)); > #else > worker->id = 0; /* mark it removed */ > #endif > {code} > h3. Behavior > {code} > 957 helper = (proxy_cluster_helper *) worker->context; > 961 if (helper) { > 962 i = helper->count_active; > 963 } > 968 if (i == 0) { > 971 proxy_worker_shared *stat = worker->s; > 972 proxy_cluster_helper *helper = (proxy_cluster_helper *) worker->context; > {code} > At this point, {{helper->shared}} points to a {{proxy_worker_shared}} structure that appears to be properly filled. > {code} > 999 if (worker->cp->pool) { > 1000 apr_pool_destroy(worker->cp->pool); > 1001 worker->cp->pool = NULL; > 1002 } > {code} > Regardless of the aforementioned block being there or nor (stuffed after 1010), > {{helper->shared}} suddenly points to {{NULL}}. > {code} > 1008 helper->index = 0; > 1009 worker->s = helper->shared; > {code} > Above assignment makes {{worker->s}} pointing to NULL. > {code} > 1010 memcpy(worker->s, stat, sizeof(proxy_worker_shared)); > {code} > And here we go :( > IMHO, _other thread_ already cleared that memory and nulled the pointer, because it absolutely doesn't happen if > I run 1 process and 1 thread. > The [workaround that prevents the core|https://github.com/modcluster/mod_cluster/pull/207] looks like this: > {code} > if (helper->shared) { > worker->s = helper->shared; > memcpy(worker->s, stat, sizeof(proxy_worker_shared)); > } > {code} > h3. How do we fix it? > Any ideas? [~jfclere] -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-547) process_buff regression brought in by modcluster/mod_cluster/pull/223/

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-547?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-547: ------------------------------------------- Attachment: patch.MODCLUSTER-547 > process_buff regression brought in by modcluster/mod_cluster/pull/223/ > ---------------------------------------------------------------------- > > Key: MODCLUSTER-547 > URL: https://issues.jboss.org/browse/MODCLUSTER-547 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.4.Final > Environment: httpd 2.2.15 RHEL 6 x86_64, mod_cluster 2.0 Tomcat 8 Workers > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Priority: Blocker > Attachments: patch.MODCLUSTER-547 > > > Perfectly ordinary workers are prevented from joining the balancer: > h3. Wrong > {code} > [debug] mod_manager.c(2340): manager_trans INFO (/) > [debug] mod_manager.c(3056): manager_handler INFO (/) processing: "" > [error] process_buff: > [warn] manager_handler INFO error: SYNTAX: Can't parse MCMP message. It might have contained illegal symbols or unknown elements. > {code} > h3. Good > {code} > [debug] mod_manager.c(2301): manager_trans INFO (/) > [debug] mod_manager.c(3017): manager_handler INFO (/) processing: "" > [debug] mod_manager.c(3067): manager_handler INFO OK > [debug] mod_manager.c(2301): manager_trans CONFIG (/) > [debug] mod_manager.c(3017): manager_handler CONFIG (/) processing: "JVMRoute=little-20-worker-4&Balancer=balancerXXX&Domain=XXXXX14&Host=192.168.122.204&Port=14&StickySessionForce=No&StickySessionRemove=Yes&Type=ajp" > [debug] mod_manager.c(3067): manager_handler CONFIG OK > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-547) process_buff regression brought in by modcluster/mod_cluster/pull/223/

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-547?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-547: ------------------------------------------- Environment: httpd 2.2.15 RHEL 6 x86_64, mod_cluster 2.0 Tomcat 8 Workers (was: httpd 2.2.15 RHEL 6 x86_64) > process_buff regression brought in by modcluster/mod_cluster/pull/223/ > ---------------------------------------------------------------------- > > Key: MODCLUSTER-547 > URL: https://issues.jboss.org/browse/MODCLUSTER-547 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.4.Final > Environment: httpd 2.2.15 RHEL 6 x86_64, mod_cluster 2.0 Tomcat 8 Workers > Reporter: Michal Karm Babacek > Assignee: Jean-Frederic Clere > Priority: Blocker > > Perfectly ordinary workers are prevented from joining the balancer: > h3. Wrong > {code} > [debug] mod_manager.c(2340): manager_trans INFO (/) > [debug] mod_manager.c(3056): manager_handler INFO (/) processing: "" > [error] process_buff: > [warn] manager_handler INFO error: SYNTAX: Can't parse MCMP message. It might have contained illegal symbols or unknown elements. > {code} > h3. Good > {code} > [debug] mod_manager.c(2301): manager_trans INFO (/) > [debug] mod_manager.c(3017): manager_handler INFO (/) processing: "" > [debug] mod_manager.c(3067): manager_handler INFO OK > [debug] mod_manager.c(2301): manager_trans CONFIG (/) > [debug] mod_manager.c(3017): manager_handler CONFIG (/) processing: "JVMRoute=little-20-worker-4&Balancer=balancerXXX&Domain=XXXXX14&Host=192.168.122.204&Port=14&StickySessionForce=No&StickySessionRemove=Yes&Type=ajp" > [debug] mod_manager.c(3067): manager_handler CONFIG OK > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues October 2016