[mod_cluster-issues] [JBoss JIRA] Commented: (MODCLUSTER-120) Apache with mod_cluster refuses to start at first, after 7 retries it starts up

Jean-Frederic Clere (JIRA) jira-events at lists.jboss.org
Tue Feb 16 05:24:10 EST 2010


    [ https://jira.jboss.org/jira/browse/MODCLUSTER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12514622#action_12514622 ] 

Jean-Frederic Clere commented on MODCLUSTER-120:
------------------------------------------------

it takes a while to reproduce but it is linked with the kill -9 you use in the script.
the shared memory is created but not cleaned, somehow the file of the ftok()  is cleaned. (httpd child processes dectect the death of their father).

The removal fails because the file doesn't exist then new creation (creates the file) but failed because the shared memory exists in a second run the file exists and the removal is successful.


> Apache with mod_cluster refuses to start at first, after 7 retries it starts up
> -------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-120
>                 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-120
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.0.2.GA
>         Environment: x64, RHEL 5.2, Server version: Apache/2.2.13 (Unix) 
>            Reporter: Radoslav Husar
>            Assignee: Jean-Frederic Clere
>            Priority: Critical
>         Attachments: MODCLUSTER-120.log
>
>
> When starting up Apache with mod cluster, by command:
> [hudson at perf10 httpd]$ /usr/sbin/apachectl -k start -d /tmp/hudson/httpd
> It refuses to start, but creates files in logs one-by-one and then when all files are created it accepts to start.
> [hudson at perf10 httpd]$ cat logs/error_log 
> [Tue Jan 05 12:01:11 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
> [Tue Jan 05 12:01:11 2010] [notice] Digest: generating secret for digest authentication ...
> [Tue Jan 05 12:01:11 2010] [notice] Digest: done                                           
> [Tue Jan 05 12:01:11 2010] [emerg] create_mem_node /tmp/hudson/httpd/logs/manager.node failed
> Configuration Failed                                                                         
> [Tue Jan 05 12:01:37 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)     
> [Tue Jan 05 12:01:37 2010] [notice] Digest: generating secret for digest authentication ...  
> [Tue Jan 05 12:01:37 2010] [notice] Digest: done                                             
> [Tue Jan 05 12:01:37 2010] [emerg] create_mem_context failed                                 
> Configuration Failed                                                                         
> [Tue Jan 05 12:02:40 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)     
> [Tue Jan 05 12:02:40 2010] [notice] Digest: generating secret for digest authentication ...  
> [Tue Jan 05 12:02:40 2010] [notice] Digest: done                                             
> [Tue Jan 05 12:02:40 2010] [emerg] create_mem_host failed                                    
> Configuration Failed                                                                         
> [Tue Jan 05 12:04:43 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)     
> [Tue Jan 05 12:04:43 2010] [notice] Digest: generating secret for digest authentication ...  
> [Tue Jan 05 12:04:43 2010] [notice] Digest: done                                             
> [Tue Jan 05 12:04:43 2010] [emerg] create_mem_balancer failed                                
> Configuration Failed                                                                         
> [Tue Jan 05 12:04:44 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)     
> [Tue Jan 05 12:04:44 2010] [notice] Digest: generating secret for digest authentication ...  
> [Tue Jan 05 12:04:44 2010] [notice] Digest: done                                             
> [Tue Jan 05 12:04:44 2010] [emerg] create_mem_sessionid failed                               
> Configuration Failed                                                                         
> [Tue Jan 05 12:04:45 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)     
> [Tue Jan 05 12:04:45 2010] [notice] Digest: generating secret for digest authentication ...  
> [Tue Jan 05 12:04:45 2010] [notice] Digest: done                                             
> [Tue Jan 05 12:04:45 2010] [emerg] create_mem_domain failed                                  
> Configuration Failed
> [Tue Jan 05 12:04:46 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
> [Tue Jan 05 12:04:46 2010] [notice] Digest: generating secret for digest authentication ...
> [Tue Jan 05 12:04:46 2010] [notice] Digest: done
> [Tue Jan 05 12:04:46 2010] [notice] Advertise initialized for process 1713
> [Tue Jan 05 12:04:46 2010] [notice] Apache/2.2.3 (Red Hat) configured -- resuming normal operations
> The configuration is here:
> https://svn.devel.redhat.com/repos/jboss-qa/load-testing/etc/httpd/mod_cluster/
> Is there a workaround? What might be causing this?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the mod_cluster-issues mailing list