[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
Thu Jan 7 13:13:30 EST 2010
[ https://jira.jboss.org/jira/browse/MODCLUSTER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12502790#action_12502790 ]
Jean-Frederic Clere commented on MODCLUSTER-120:
------------------------------------------------
BTW: How did you compiled mod_proxy_cluster.c?
I have the following:
+++
mod_proxy_cluster.c:1740: error: 'struct proxy_alias' has no member named 'regex'
mod_proxy_cluster.c:1741: error: 'struct proxy_alias' has no member named 'regex'
mod_proxy_cluster.c:1749: error: 'proxy_dir_conf' has no member named 'interpolate_env'
mod_proxy_cluster.c:1750: error: 'struct proxy_alias' has no member named 'flags'
mod_proxy_cluster.c:1750: error: 'PROXYPASS_INTERPOLATE' undeclared (first use in this function)
mod_proxy_cluster.c:1750: error: (Each undeclared identifier is reported only once
mod_proxy_cluster.c:1750: error: for each function it appears in.)
mod_proxy_cluster.c: In function 'find_route_worker':
mod_proxy_cluster.c:1814: warning: implicit declaration of function 'PROXY_WORKER_IS_STANDBY'
mod_proxy_cluster.c: At top level:
mod_proxy_cluster.c:2007: warning: no previous prototype for 'remove_session_route'
mod_proxy_cluster.c: In function 'proxy_cluster_pre_request':
mod_proxy_cluster.c:2226: error: 'proxy_worker_stat' has no member named 'busy'
mod_proxy_cluster.c: In function 'proxy_cluster_post_request':
mod_proxy_cluster.c:2278: error: 'proxy_worker_stat' has no member named 'busy'
mod_proxy_cluster.c:2279: error: 'proxy_worker_stat' has no member named 'busy'
+++
> 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
> 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