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

Michal Karm Babacek (JIRA) issues at jboss.org
Wed Jul 20 09:48:00 EDT 2016


     [ https://issues.jboss.org/browse/MODCLUSTER-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Karm Babacek updated MODCLUSTER-526:
-------------------------------------------
    Description: 
* 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

{code}
h==9005== Thread 5:
==9005== Source and destination overlap in memcpy(0x4021068, 0x4021068, 304)
==9005==    at 0x4C2B403: memcpy@@GLIBC_2.14 (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==9005==    by 0xB28ECA1: insert_update (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
==9005==    by 0xB07BCC2: ap_slotmem_do (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_cluster_slotmem.so)
==9005==    by 0xB28ED6B: insert_update_node (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
==9005==    by 0xB28666D: process_node_cmd (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
==9005==    by 0xB286AA7: process_appl_cmd (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
==9005==    by 0xB28745A: process_remove (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
==9005==    by 0xB28B619: manager_handler (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
==9005==    by 0x44CEEF: ap_run_handler (config.c:170)
==9005==    by 0x44D438: ap_invoke_handler (config.c:434)
==9005==    by 0x461D89: ap_process_async_request (http_request.c:410)
==9005==    by 0x45E4AF: ap_process_http_connection (http_core.c:154)
==9005== 
==9005== Thread 3:
==9005== Invalid write of size 8
==9005==    at 0x4C2B473: memcpy@@GLIBC_2.14 (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==9005==    by 0xB499EE5: remove_workers_node (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_proxy_cluster.so)
==9005==    by 0xB49E165: remove_workers_nodes (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_proxy_cluster.so)
==9005==    by 0xB49E353: proxy_cluster_watchdog_func (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_proxy_cluster.so)
==9005==    by 0x5B5FEE4: start_thread (pthread_create.c:309)
==9005==    by 0x606DD1C: clone (clone.S:111)
==9005==  Address 0x0 is not stack'd, malloc'd or (recently) free'd

{code}

  was:
* 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



> 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
>            Reporter: Michal Karm Babacek
>            Assignee: Michal Karm Babacek
>            Priority: Blocker
>             Fix For: 1.3.4.Final
>
>
> * 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
> {code}
> h==9005== Thread 5:
> ==9005== Source and destination overlap in memcpy(0x4021068, 0x4021068, 304)
> ==9005==    at 0x4C2B403: memcpy@@GLIBC_2.14 (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==9005==    by 0xB28ECA1: insert_update (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
> ==9005==    by 0xB07BCC2: ap_slotmem_do (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_cluster_slotmem.so)
> ==9005==    by 0xB28ED6B: insert_update_node (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
> ==9005==    by 0xB28666D: process_node_cmd (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
> ==9005==    by 0xB286AA7: process_appl_cmd (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
> ==9005==    by 0xB28745A: process_remove (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
> ==9005==    by 0xB28B619: manager_handler (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_manager.so)
> ==9005==    by 0x44CEEF: ap_run_handler (config.c:170)
> ==9005==    by 0x44D438: ap_invoke_handler (config.c:434)
> ==9005==    by 0x461D89: ap_process_async_request (http_request.c:410)
> ==9005==    by 0x45E4AF: ap_process_http_connection (http_core.c:154)
> ==9005== 
> ==9005== Thread 3:
> ==9005== Invalid write of size 8
> ==9005==    at 0x4C2B473: memcpy@@GLIBC_2.14 (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==9005==    by 0xB499EE5: remove_workers_node (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_proxy_cluster.so)
> ==9005==    by 0xB49E165: remove_workers_nodes (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_proxy_cluster.so)
> ==9005==    by 0xB49E353: proxy_cluster_watchdog_func (in /home/karm/Projects/MOD_CLUSTER/httpd-2.4.20-build/modules/mod_proxy_cluster.so)
> ==9005==    by 0x5B5FEE4: start_thread (pthread_create.c:309)
> ==9005==    by 0x606DD1C: clone (clone.S:111)
> ==9005==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the mod_cluster-issues mailing list