[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617148#comment-17617148
]
Brandon Williams commented on CASSANDRA-17922:
----------------------------------------------
I changed all the prints to proper logging messages because Jenkins seems to
eat the output, or at least I can't find it. A run with those changes have
yielded this interesting bit:
{noformat}
19:11:42 00:11:42,241 tools.jmxutils INFO Port 8778 open for jolokia
19:11:44 00:11:43,956 tools.jmxutils WARNING Failed to start jolokia agent
(command was: /usr/lib/jvm/java-8-openjdk-amd64/bin/java -cp
/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar
org.jolokia.jvmagent.client.AgentLauncher --host 127.0.0.1 --port 8778 start
2190): Command '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp',
'/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.1', '--port',
'8778', 'start', '2190')' returned non-zero exit status 1.
19:11:44 00:11:43,957 tools.jmxutils WARNING Exit status was: 1
19:11:44 00:11:43,958 tools.jmxutils WARNING Output was: b"Couldn't start agent
for PID 2190\nPossible reason could be that port '8778' is already
occupied.\nPlease check the standard output of the target process for a
detailed error message.\n"
19:11:46 00:11:46,546 tools.jmxutils WARNING Failed to start jolokia agent
(command was: /usr/lib/jvm/java-8-openjdk-amd64/bin/java -cp
/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar
org.jolokia.jvmagent.client.AgentLauncher --host 127.0.0.1 --port 8778 start
2190): Command '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp',
'/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.1', '--port',
'8778', 'start', '2190')' returned non-zero exit status 1.
19:11:46 00:11:46,547 tools.jmxutils WARNING Exit status was: 1
19:11:46 00:11:46,548 tools.jmxutils WARNING Output was: b'Jolokia is already
attached to PID 2190\nhttp://127.0.0.1:8778/jolokia/\n'
19:11:49 FAILED
{noformat}
This seems to indicate these initial "couldn't start agent" failures are at
least sometimes bogus, as jolokia was actually successful according to the
second error.
> Jolokia agent fails to connect though port is available
> -------------------------------------------------------
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
> {code}
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '{-}cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '{-}{-}host', '127.0.0.2',
> '{-}-port', '8778', 'start', '1123')' returned non-zero exit status 1.
> {code}
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
