Red Hat Bugzilla – Bug 900518
Jdr script utility isn't able to connect to localhost:9990 at all
Last modified: 2014-07-31 23:52:09 EDT
Affects: Release Notes project_key: JBPAPP6 Starting $EAP_HOME/bin/jdr.sh script on running server(standalone or domain), in any case, even using management user credentials I see in generated zip in /sos_reports/sos.txt rows like this: - alerts: ! INFO: The JBoss installation directory supplied to SOS is /home/vrastsel/jboss-eap-6.0 ! JBOSS API call failed, falling back to HTTP: Controller Client is not available ! JBOSS API call failed, falling back to HTTP: Controller Client is not available ! JBOSS API call failed, falling back to HTTP: Controller Client is not available ! Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error ! JBOSS API call failed, falling back to HTTP: Controller Client is not available Looks like utility isn't able to connect to this URL.
Labels: Added: eap6_need_triage
Please assign it to correct person, there is no default assignee for 'Scripts and Commands'. Thanks.
sos_strings/as7/cluster-proxies-configuration.json contains error too: 'Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error'
Can you try to determine the other side of the 500 error? Can you see any corresponding information in the server.log?
server.log doesn't contain information about it.
Can you set the logging to DEBUG and try it again then post the log?
Link: Added: This issue is related to JBPAPP-9134
The debug output is the same, like reported in JBPAPP-9134
Link: Added: This issue is a dependency of JBPAPP-9188
Link: Removed: This issue is a dependency of JBPAPP-9188
Release Notes Docs Status: Added: Documented as Known Issue Release Notes Text: Added: The JDR utility (<filename><replaceable>EAP_HOME</replaceable>/bin/jdr.sh</filename> or <filename>jdr.bat</filename>) fails to connect to the localhost, with the message <code>JBOSS API call failed, falling back to HTTP: Controller Client is not available</code>. The cause of this error is still under investigation. Affects: Added: Release Notes
I'm unable to reproduce this on the latest AS7 or the EAP6.0.0 release. (I assume you have a management user configured via bin/add-user.sh prior to using jdr.sh)
Labels: Removed: eap6_need_triage Added: eap601candidate
I can reproduce it on today's AS7 with management user added. Moreover, there is JBPAPP-9134 bug presented too. In report file(see path above) I see: - alerts: ! INFO: The JBoss installation directory supplied to SOS is /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT ! JBOSS API call failed, falling back to HTTP: Controller Client is not available ! JBOSS API call failed, falling back to HTTP: Controller Client is not available ! JBOSS API call failed, falling back to HTTP: Controller Client is not available ! Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error ! JBOSS API call failed, falling back to HTTP: Controller Client is not available ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/jboss/resteasy/resteasy-jaxb-provider/main/resteasy-jaxb-provider-2.3.3.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/jboss/resteasy/resteasy-jettison-provider/main/resteasy-jettison-provider-2.3.3.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/jboss/resteasy/resteasy-jsapi/main/resteasy-jsapi-2.3.3.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/jboss/resteasy/resteasy-multipart-provider/main/resteasy-multipart-provider-2.3.3.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/jboss/resteasy/resteasy-atom-provider/main/resteasy-atom-provider-2.3.3.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/jboss/resteasy/resteasy-jackson-provider/main/resteasy-jackson-provider-2.3.3.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/jboss/resteasy/resteasy-yaml-provider/main/resteasy-yaml-provider-2.3.3.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/jboss/resteasy/resteasy-jaxrs/main/async-http-servlet-3.0-2.3.3.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/jboss/resteasy/resteasy-jaxrs/main/resteasy-jaxrs-2.3.3.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/picketlink/main/picketlink-core-2.1.1.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/picketlink/main/picketlink-jbas7-2.1.1.Final-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/org/picketlink/main/picketlink-core-2.1.1.Final-jandex-jandex.jar. Error: 'META-INF/MANIFEST.MF' ! ERROR: reading manifest from /home/vrastsel/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules/javax/inject/api/main/javax.inject-1.jar. Error: 'META-INF/MANIFEST.MF'
I see the error now, I had been looking in the wrong places. I think the subject of this JIRA might be a little misleading. There are a couple of things going on here: The 500 error "Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error" is generated because gathering cluster-proxies-configuration results in a 500 unless it is configured and running. Out of the box, it is not configured. This error is normal and ok. You can see this again if you look in the corresponding file in sos_strings/as7/cluster-proxies-configuration.json "JBOSS API call failed, falling back to HTTP: Controller Client is not available" is normal and ok for using jdr.sh. The 401 errors in the log are normal and expected as well. The way the http client in python works is by trying then retrying with credentials, it's chatty, but normal and expected. These messages do certainly show up in the report, however I don't think that any of what has been documented indicates that JDR is not able to connect to localhost:9990.
I'm little bit confused with last comment. Does it mean everything is fine? And log files contain to much noise which confused us? If yes, than customers would be confused too and it would affect GSS - explaining several time that it's expected behavior.
Yes, everything is fine. I agree with you that there is a lot of noise in the log files. Some of that can possibly be cleaned up over time in the upstream sosreport project.
Writer: Added: mistysj
Release Notes Text: Removed: The JDR utility (<filename><replaceable>EAP_HOME</replaceable>/bin/jdr.sh</filename> or <filename>jdr.bat</filename>) fails to connect to the localhost, with the message <code>JBOSS API call failed, falling back to HTTP: Controller Client is not available</code>. The cause of this error is still under investigation. Added: The following error messages occur in the following contexts if the <code>clusters-proxy-configuration</code> is unconfigured: <itemizedlist> <listitem> <para> Server logs: Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error </para> </listitem> <listitem> <para> When running the <filename>jdr.sh</filename> script: JBOSS API call failed, falling back to HTTP: Controller Client is not available </para> </listitem> </itemizedlist> These errors are normal, and only indicate that the <code>clusters-proxy-configuration</code> is unconfigured. These messages are created because of implementations in the upstream <code>sosreport</code> project, and they may be modified or removed in the future.
Release Notes Text: Removed: The following error messages occur in the following contexts if the <code>clusters-proxy-configuration</code> is unconfigured: <itemizedlist> <listitem> <para> Server logs: Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error </para> </listitem> <listitem> <para> When running the <filename>jdr.sh</filename> script: JBOSS API call failed, falling back to HTTP: Controller Client is not available </para> </listitem> </itemizedlist> These errors are normal, and only indicate that the <code>clusters-proxy-configuration</code> is unconfigured. These messages are created because of implementations in the upstream <code>sosreport</code> project, and they may be modified or removed in the future. Added: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error * When running the `jdr.sh` script: JBOSS API call failed, falling back to `HTTP: Controller Client is not available These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future.
Release Notes Text: Removed: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error * When running the `jdr.sh` script: JBOSS API call failed, falling back to `HTTP: Controller Client is not available These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future. Added: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error * When running the `jdr.sh` script: JBOSS API call failed, falling back to `HTTP: Controller Client is not available These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future.
Release Notes Text: Removed: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error * When running the `jdr.sh` script: JBOSS API call failed, falling back to `HTTP: Controller Client is not available These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future. Added: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: `Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error` * When running the `jdr.sh` script: `JBOSS API call failed, falling back to `HTTP: Controller Client is not available` These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future.
Release Notes Text: Removed: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: `Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error` * When running the `jdr.sh` script: `JBOSS API call failed, falling back to `HTTP: Controller Client is not available` These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future. Added: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: `Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error` * When running the `jdr.sh` script: `JBOSS API call failed, falling back to `HTTP: Controller Client is not available` These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future.
Release Notes Text: Removed: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: `Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error` * When running the `jdr.sh` script: `JBOSS API call failed, falling back to `HTTP: Controller Client is not available` These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future. Added: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: `Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error` * When running the `jdr.sh` script: `JBOSS API call failed, falling back to HTTP: Controller Client is not available` These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future.
Release Notes Docs Status: Removed: Documented as Known Issue Writer: Removed: mistysj Release Notes Text: Removed: The following error messages occur in the following contexts if the `clusters-proxy-configuration` is unconfigured: * Server logs: `Could not query url: http://localhost:9990/management; error: HTTP Error 500: Internal Server Error` * When running the `jdr.sh` script: `JBOSS API call failed, falling back to HTTP: Controller Client is not available` These errors are normal, and only indicate that the `clusters-proxy-configuration` is unconfigured. These messages are created because of implementations in the upstream `sosreport` project, and they may be modified or removed in the future. Docs QE Status: Removed: NEW
Info from jjaggars via IRC: <rdickens> jjaggars> ping; i am an eap 6 docs writer and i need help with the release notes' item for: https://bugzilla.redhat.com/show_bug.cgi?id=900518 <unifiedbot> [900518] Jdr script utility isn't able to connect to localhost:9990 at all [JBoss Enterprise Application Platform 6] [jjaggars@redhat.com:VERIFIED] <rdickens> jjaggars> i am trying to confirm: what was the root cause of the bug and what code changes resolved it? <jjaggars_> rdickens: the root cause is the way JDR on that version of jboss attempts to contact the management API. It connects over HTTP as it's final method, and if that fails it puts the HTTP error in the logs and output file. In many cases the cluster stuff isn't enabled or configured so a 500 error is captured. <rdickens> jjaggars> awesome. thanks for that. so were code changes made to rectify the problem? <jjaggars_> rdickens: in version 6.1 JDR was re-written in pure java and this issue no longer exists <rdickens> jjaggars> thankyou. i'll cut-and-paste this into the BZ ticket and work from there.