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

Radoslav Husar (JIRA) jira-events at lists.jboss.org
Thu Jan 7 08:37:30 EST 2010


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

Radoslav Husar updated MODCLUSTER-120:
--------------------------------------

    Attachment: MODCLUSTER-120.log


Finally I managed to reproduce and get a log since this issue seems to be non-deterministic (or just dont know the precoditions yet).

Attaching a bash log, watch closely how on each call to startup via /usr/sbin/httpd.worker -d /tmp/hudson/httpd     a new temporary mod_cluster file is created. Then at the end it starts up (possibly its a bug related to pid file?).


> 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, Server version: Apache/2.2.3, Server built:   Jul  6 2009 05:29:28
>            Reporter: Radoslav Husar
>            Assignee: Jean-Frederic Clere
>         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