[JBoss JIRA] Created: (MODCLUSTER-160) Include link to mod_cluster config generator in publication mod_cluster User Guide.
by Gary Meintjes (JIRA)
Include link to mod_cluster config generator in publication mod_cluster User Guide.
-----------------------------------------------------------------------------------
Key: MODCLUSTER-160
URL: https://jira.jboss.org/browse/MODCLUSTER-160
Project: mod_cluster
Issue Type: Task
Reporter: Gary Meintjes
Assignee: Gary Meintjes
Priority: Minor
Insert a link in the publication to the mod_cluster configuration generating tool: http://lbconfig.appspot.com.
Envisaged: Update trunk document for inclusion in EAP 5.1 release in August 2010.
--
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
12 years, 11 months
- 3
- 4
[JBoss JIRA] Created: (MODCLUSTER-120) Apache with mod_cluster refuses to start at first, after 7 retries it starts up
by Radoslav Husar (JIRA)
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
When starting up Apache with mod cluster, by command:
[hudson@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@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_cl...
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
12 years, 12 months
- 4
- 32
[JBoss JIRA] (MODCLUSTER-264) jboss-admin.sh accepts crazy values for :add-proxy()
by Misty Stanley-Jones (Created) (JIRA)
jboss-admin.sh accepts crazy values for :add-proxy()
----------------------------------------------------
Key: MODCLUSTER-264
URL: https://issues.jboss.org/browse/MODCLUSTER-264
Project: mod_cluster
Issue Type: Bug
Environment: modcluster subsystem of AS 7.1 trunk
Reporter: Misty Stanley-Jones
Assignee: Jean-Frederic Clere
I am allowed to use all of these kinds of syntax with :add-proxy():
[domain@localhost:9999 subsystem=modcluster] :add-proxy(host=abc.com,port=123)
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined},
"server-operations" => [{
"servers" => [],
"operation" => {
"address" => [("subsystem" => "modcluster")],
"operation" => "add-proxy",
"port" => 123,
"host" => "abc.com",
"operation-headers" => {"execute-for-coordinator" => true}
}
}]
}
}
[domain@localhost:9999 subsystem=modcluster] :add-proxy(host=def.com)
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined},
"server-operations" => [{
"servers" => [],
"operation" => {
"address" => [("subsystem" => "modcluster")],
"operation" => "add-proxy",
"host" => "def.com",
"operation-headers" => {"execute-for-coordinator" => true}
}
}]
}
}
[domain@localhost:9999 subsystem=modcluster] :add-proxy(port=999)
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined},
"server-operations" => [{
"servers" => [],
"operation" => {
"address" => [("subsystem" => "modcluster")],
"operation" => "add-proxy",
"port" => 999,
"operation-headers" => {"execute-for-coordinator" => true}
}
}]
}
}
I think only the first one should be valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months
- 5
- 4
- ← Newer
- 1
- Older →