June 2015 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-458) Add JVMRoute or node identifier to httpd/mod_cluster errors

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-458?page=com.atlassian.jira.pl... ] Michal Karm Babacek closed MODCLUSTER-458. ------------------------------------------ > Add JVMRoute or node identifier to httpd/mod_cluster errors > ----------------------------------------------------------- > > Key: MODCLUSTER-458 > URL: https://issues.jboss.org/browse/MODCLUSTER-458 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Reporter: Coty Sutherland > Assignee: Michal Karm Babacek > Fix For: 1.3.2.Alpha1 > > > Messages such as: > [Tue Apr 14 10:38:56 2015] [warn] manager_handler STATUS error: MEM: Can't read node > are very difficult to troubleshoot given the limited context provided. It would be great if we could add some sort of node identifier or the JVMRoute of the node to the message above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-458) Add JVMRoute or node identifier to httpd/mod_cluster errors

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-458?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-458: ------------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 1.3.2.Alpha1 Resolution: Done > Add JVMRoute or node identifier to httpd/mod_cluster errors > ----------------------------------------------------------- > > Key: MODCLUSTER-458 > URL: https://issues.jboss.org/browse/MODCLUSTER-458 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Reporter: Coty Sutherland > Assignee: Michal Karm Babacek > Fix For: 1.3.2.Alpha1 > > > Messages such as: > [Tue Apr 14 10:38:56 2015] [warn] manager_handler STATUS error: MEM: Can't read node > are very difficult to troubleshoot given the limited context provided. It would be great if we could add some sort of node identifier or the JVMRoute of the node to the message above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-458) Add JVMRoute or node identifier to httpd/mod_cluster errors

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-458?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-458: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/148, https://github.com/modcluster/mod_cluster/pull/147 Done. The new implementation shows error messages such as: {noformat} 21:33:11,301 ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error MEM sending STATUS command to 192.168.122.1/192.168.122.1:6666, configuration will be reset: MEM: Can't read node with "Worker-1" JVMRoute {noformat} or {noformat} MEM: Old node with "WORKER-001" JVMRoute still exists {noformat} instead the old ambiguous: {noformat} MEM: Can't read node {noformat} > Add JVMRoute or node identifier to httpd/mod_cluster errors > ----------------------------------------------------------- > > Key: MODCLUSTER-458 > URL: https://issues.jboss.org/browse/MODCLUSTER-458 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Reporter: Coty Sutherland > Assignee: Michal Babacek > > Messages such as: > [Tue Apr 14 10:38:56 2015] [warn] manager_handler STATUS error: MEM: Can't read node > are very difficult to troubleshoot given the limited context provided. It would be great if we could add some sort of node identifier or the JVMRoute of the node to the message above. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-459) mod_cluster subsystem remains silent if connector set to http

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-459?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-459: ------------------------------------------- This is what happens if you don't have any http connector defined in UT subsystem - can you check your config? > mod_cluster subsystem remains silent if connector set to http > ------------------------------------------------------------- > > Key: MODCLUSTER-459 > URL: https://issues.jboss.org/browse/MODCLUSTER-459 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.3.1.Final > Reporter: Michal Babacek > Assignee: Radoslav Husar > Fix For: 1.3.2.Alpha1 > > > If one sets mod_cluster subsystem {{connector="http"}} there is nothing in the log about any mod_cluster subsystem being initialized, no warning, nothing. It appears to be dead silent even with log level DEBUG. > When switched back to {{connector="ajp"}}, there are the well known comforting messages: > {noformat} > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364 > {noformat} > Weird. Any obvious misconfiguration or explanation? The config is the default standalone-ha.xml otherwise. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-459) mod_cluster subsystem remains silent if connector set to http

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-459?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-459: ----------------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > mod_cluster subsystem remains silent if connector set to http > ------------------------------------------------------------- > > Key: MODCLUSTER-459 > URL: https://issues.jboss.org/browse/MODCLUSTER-459 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.3.1.Final > Reporter: Michal Babacek > Assignee: Radoslav Husar > Fix For: 1.3.2.Alpha1 > > > If one sets mod_cluster subsystem {{connector="http"}} there is nothing in the log about any mod_cluster subsystem being initialized, no warning, nothing. It appears to be dead silent even with log level DEBUG. > When switched back to {{connector="ajp"}}, there are the well known comforting messages: > {noformat} > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364 > {noformat} > Weird. Any obvious misconfiguration or explanation? The config is the default standalone-ha.xml otherwise. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues June 2015