[Bug]: New Cassandra container fails to start DSE 6.8.47 #9337

Activity

1. wendigo

   added

   type/bug

   on Oct 1, 2024
2. kiview

   added

   modules/cassandra

   on Oct 1, 2024
3. kiview commented on Oct 1, 2024

   

   kiview

   on Oct 1, 2024

   Member

   More actions

   Thanks for raising the issue @wendigo.
   Are the publicly available DSE images we can use for testing?

   To unblock you, I would recommend to continue using the deprecated CassandraContainer for now.

   👍React with 👍1Reacted by Mateusz "Serafin" Gajewski
4. wendigo commented on Oct 1, 2024

   

   wendigo

   on Oct 1, 2024

   Author

   More actions

   @kiview datastax/dse-server:6.8.47
5. maximevw commented on Oct 8, 2024

   

   maximevw

   on Oct 8, 2024

   Last edited by maximevw

   Contributor

   More actions

   Hello @wendigo

   On my side, I successfully tested it with the dse-server 6.9.2. I didn't test with the version you mentioned, but DSE images normally include cqlsh.

   Do you have some specific settings (like env variables) when you start your container?

   If you have an init script, you must also specify withWorkingDirectory("/") (because the DSE container starts in the /opt/dse directory and the init script is copied at the root of the container).

   Note the error could appear several times in the logs before the server is finally up (it could take until 10 seconds in my tests before the query is finally executed with success). Also, the logs could be improved in the new implementation in order to not log such "expected" errors because it is just checking the server is up.

   👍React with 👍1Reacted by Kevin Wittek
6. kiview

   added

   resolution/waiting-for-infoWaiting for more information of the issue author or another 3rd party.Waiting for more information of the issue author or another 3rd party.

   on Oct 11, 2024
7. kiview commented on Oct 11, 2024

   

   kiview

   on Oct 11, 2024

   Member

   More actions

   I can confirm, the following works for me:

   CassandraContainer cassandraContainer = new CassandraContainer(DockerImageName.parse("datastax/dse-server:6.8.47")
                   .asCompatibleSubstituteFor("cassandra"))
                   .withEnv("DS_LICENSE", "accept")

   However, since I am running an x86 image here in my AppleSilicon through emulation, it is slow and you will indeed see the error logged multiple times:

   15:03:25.399 ERROR org.testcontainers.cassandra.delegate.CassandraDatabaseDelegate - CQL script execution failed with error: 
   Connection error: ('Unable to connect to any servers', {'127.0.0.1:9042': error(111, "Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection refused")})
   

   @maximevw I guess changing the log level for these interim logs would help with the experience.

   For now, I will close this issue, since I can't reproduce it, but please consider to follow up with more information @wendigo.

   👍React with 👍1Reacted by Maxime Wiewiora
8. kiview

   closed this as completedon Oct 11, 2024
9. kiview

   added

   resolution/invalid

   and removed

   resolution/waiting-for-infoWaiting for more information of the issue author or another 3rd party.Waiting for more information of the issue author or another 3rd party.

   on Oct 11, 2024
10. wendigo commented on Oct 11, 2024

    

    wendigo

    on Oct 11, 2024

    Author

    More actions

    That's not what I observe while running in the CI (x86 based).
11. wendigo commented on Oct 11, 2024

    

    wendigo

    on Oct 11, 2024

    Author

    More actions

    I'll send you a link to the run