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

[Baptiste MATHUS (JIRA)]

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

Baptiste MATHUS commented on MODCLUSTER-120:
--------------------------------------------

I'm having the same problem. After some analysis, I don't think this problem is related to shared memory or so. 
I think it's only related to right management, as stated in the first comment. I thinks the fact that it's able to start the seventh time (which I can't reproduce) is related to some particular config or case.

More precisely, I think it's related to the fact that httpd typically starts itself as root since it must commonly be able to bind on <1024. Once done, it immediately changes user to another one (commonly "apache").

I guess the manager.node is created by the corresponding module before changing execution user. Then, after user change, as "apache" user isn't root, it gives the error saying it's not able to access the previously created file.



On a related note, I'm wondering: is there a way to know the version of an installed mod_xxx_.so with some command?

Thanks a lot.
PS :
RHEL platform, (official rpms I seem to remember), and using the modules coming from JBoss5.1-EAP DVD.

> Apache with mod_cluster refuses to start at first, after 7 retries it starts up
> -------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-120
>                 URL: https://jira.jboss.org/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
>             Fix For: 1.1.0.CR1
>
>         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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira