Wie kann der Fehler "Fehler beim Verbinden mit dem Speicher-Cluster" behoben werden?

Ich versuche, den Red Hat RHQ-Server auf meinem lokalen Rechner zu installieren . Ich habe eine PostgreSQL-Datenbank gemäß dieser Anleitung installiert und konfiguriert .

Danach wechselte ich wieder auf die offizielle Kurzanleitung zur Installation und Konfiguration der rhq-server.properties Datei, wie es dort beschrieben ist. In Anbetracht der rhq-storage.properties folgte ich dem Link, um seine Bedeutung zu sehen, und entschied mich dazu, die Datei nicht zu bearbeiten. Dies ist nur zu Demonstrationszwecken.

Meine rhq-server.properties sieht so aus:

 #################### RHQ Server Configuration Properties ####################  ############################################################################# # Database Settings # ----------------- # INSTALLATION ACTION REQUIRED! # All properties must be explicitly set for the desired database vendor. # # These should point to the database that your RHQ Server will use as # its backend RDBMS storage. # If you are using Oracle: # - comment out the Postgres settings # - uncomment the Oracle settings below # - adjust the values to match your environment # # NOTE: rhq.server.database.password is not to be set to the actual password # but instead should be the encoded password value as generated by: # rhq-encode-value.sh(.bat) #############################################################################  # PostgreSQL database rhq.server.database.connection-url=jdbc:postgresql://127.0.0.1:5432/rhq rhq.server.database.user-name=rhqadmin rhq.server.database.password=1eeb2f255e832171df8592078de921bc rhq.server.database.type-mapping=PostgreSQL rhq.server.database.server-name=127.0.0.1 rhq.server.database.port=5432 rhq.server.database.db-name=rhq hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect rhq.server.quartz.driverDelegateClass=org.quartz.impl.jdbcjobstore.PostgreSQLDelegate  # Oracle database #rhq.server.database.connection-url=jdbc:oracle:thin:@127.0.0.1:1521:xe #rhq.server.database.user-name=rhqadmin #rhq.server.database.password=1eeb2f255e832171df8592078de921bc #rhq.server.database.type-mapping=Oracle10g #hibernate.dialect=org.hibernate.dialect.Oracle10gDialect #rhq.server.quartz.driverDelegateClass=org.quartz.impl.jdbcjobstore.oracle.OracleDelegate  ############################################################################# # Server Settings # --------------- # UPGRADE ACTION REQUIRED! The following property must be explicitly set: # rhq.server.high-availability.name # # These are miscellaneous settings that the server will use to customize itself # to the environment in which it is running. These are settings you usually # want to change or at least be aware of. #############################################################################  # Defines what this server's name is to be known as to the RHQ system. # It doesn't necessarily have to be an IP address or hostname, but it can be. # If left blank, the RHQ Server will pick a name for itself based on the # hostname it is running on. # NOTE! If you are upgrading an existing server, this must be the same name # as the server being upgraded. rhq.server.high-availability.name=  # Email settings used to connect to an SMTP server to send alert emails. rhq.server.email.smtp-host=localhost rhq.server.email.smtp-port=25 rhq.server.email.from-address=rhqadmin@localhost  ############################################################################# # Host and Port Bindings # ---------------------- # INSTALLATION ACTION REQUIRED! The following property must be explicitly set: # jboss.bind.address # # These define the ports the RHQ Server will bind to. Most of the time # you can leave these alone. You can change these default values to # conform to your own environment's requirements, such as the IP address # the RHQ Server will bind to (jboss.bind.address) and the ports # browsers will use to access the RHQ web application # (rhq.server.socket.binding.port.http, rhq.server.socket.binding.port.https) # If you change the binding address, you might also want to change # "rhq.autoinstall.public-endpoint-address" as well. #############################################################################  # The bind address for the RHQ server (jboss server). To bind the server on # all network interfaces set to 0.0.0.0, otherwise a specific IP address. # jboss.bind.address=0.0.0.0 jboss.bind.address=0.0.0.0  # By default only local management connections  jboss.bind.address.management=127.0.0.1  jboss.socket.binding.port-offset=0  jboss.management.native.port=6999 jboss.management.http.port=6990 jboss.management.https.port=6443  rhq.server.socket.binding.port.ajp=7009 rhq.server.socket.binding.port.http=7080 rhq.server.socket.binding.port.https=7443 rhq.server.socket.binding.port.jacorb=2528 rhq.server.socket.binding.port.jacorb-ssl=2529 rhq.server.socket.binding.port.messaging=4449 rhq.server.socket.binding.port.messaging-throughput=4455 rhq.server.socket.binding.port.osgi-http=7090 rhq.server.socket.binding.port.remoting=3447 rhq.server.socket.binding.port.txn-recovery-environment=3712 rhq.server.socket.binding.port.txn-status-manager=3713  # Some left out comments due to length restrictions..  rhq.autoinstall.enabled=true rhq.autoinstall.database=overwrite rhq.autoinstall.public-endpoint-address= rhq.autoinstall.public-endpoint-port= rhq.autoinstall.public-endpoint-secure-port= rhq.autoinstall.server.admin.password=ISMvKXpXpadDiUoOSoAfww==  ############################################################################# # Advanced Settings # ----------------- # The settings below can usually be left as-is. These are advanced settings # and should only be changed if you know what you are doing. #############################################################################  # Enable debug messages from RHQ code rhq.server.log-level=INFO  # Set this to true to have the server reject agent requests upon startup. rhq.server.maintenance-mode-at-startup=false  # RHQ Server's remote endpoint for agents to talk to # bind-address and bind-port are derived from the HA server definition, # if you set the address/port here, they will override the HA server # definition found in the database rhq.communications.connector.transport=servlet rhq.communications.connector.bind-address= rhq.communications.connector.bind-port= rhq.communications.connector.transport-params=/jboss-remoting-servlet-invoker/ServerInvokerServlet  # Multicast detector configuration for auto-discovery rhq.communications.multicast-detector.enabled=false rhq.communications.multicast-detector.bind-address= rhq.communications.multicast-detector.multicast-address=224.16.16.16 rhq.communications.multicast-detector.port=16162  # Server-side SSL Security Configuration for HTTPS thru Tomcat # These are used for browser https access and # for incoming messages from agents over sslservlet transport. # [Due to issue https://issues.jboss.org/browse/WFLY-1177, you cannot change # rhq.server.tomcat.security.keystore.file or rhq.server.tomcat.security.truststore.file # after you install RHQ. If you need to change those again, you must manually do so in standalone-full.xml.] # Note that security algorithm settings are commented out - the defaults will be determined at runtime # based on the JVM the server is running in (for IBM JVMs, the algorithm will default to "IbmX509", # for all other JVMs, the algorithm will default to "SunX509"). If you need a specific algorithm value, # you may hardcode it here in this file by uncommenting the lines and setting the values explicitly. rhq.server.tomcat.security.client-auth-mode=false rhq.server.tomcat.security.secure-socket-protocol=TLS #rhq.server.tomcat.security.algorithm=SunX509 rhq.server.tomcat.security.keystore.alias=RHQ rhq.server.tomcat.security.keystore.file=$/rhq.keystore rhq.server.tomcat.security.keystore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13 rhq.server.tomcat.security.keystore.type=JKS rhq.server.tomcat.security.truststore.file=$/rhq.truststore rhq.server.tomcat.security.truststore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13 rhq.server.tomcat.security.truststore.type=JKS  # Server-side SSL Security Configuration (for incoming messages from agents) # These are used when secure transports other than sslservlet are used rhq.communications.connector.security.secure-socket-protocol=TLS rhq.communications.connector.security.keystore.file=$/rhq.keystore #rhq.communications.connector.security.keystore.algorithm=SunX509 rhq.communications.connector.security.keystore.type=JKS rhq.communications.connector.security.keystore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13 rhq.communications.connector.security.keystore.key-password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13 rhq.communications.connector.security.keystore.alias=RHQ rhq.communications.connector.security.truststore.file=$/rhq.truststore #rhq.communications.connector.security.truststore.algorithm=SunX509 rhq.communications.connector.security.truststore.type=JKS rhq.communications.connector.security.truststore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13 rhq.communications.connector.security.client-auth-mode=none  # Client-side SSL Security Configuration (for outgoing messages to agents) rhq.server.client.security.secure-socket-protocol=TLS rhq.server.client.security.keystore.file=$/rhq.keystore #rhq.server.client.security.keystore.algorithm=SunX509 rhq.server.client.security.keystore.type=JKS rhq.server.client.security.keystore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13 rhq.server.client.security.keystore.key-password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13 rhq.server.client.security.keystore.alias=RHQ rhq.server.client.security.truststore.file=$/rhq.truststore #rhq.server.client.security.truststore.algorithm=SunX509 rhq.server.client.security.truststore.type=JKS rhq.server.client.security.truststore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13 rhq.server.client.security.server-auth-mode-enabled=false  # Operations/controls timeout # Defines the default timeout for all operations (specified in seconds) rhq.server.operation-timeout=600  # Additional Quartz settings rhq.server.quartz.selectWithLockSQL=SELECT * FROM LOCKS ROWLOCK WHERE LOCK_NAME = ? FOR UPDATE rhq.server.quartz.lockHandlerClass=org.quartz.impl.jdbcjobstore.StdRowLockSemaphore  # Concurrency limits for incoming UI and agent messages rhq.server.startup.web.max-connections=200 rhq.server.agent-downloads-limit=45 rhq.server.client-downloads-limit=5 rhq.communications.global-concurrency-limit=30 rhq.server.concurrency-limit.inventory-report=5 rhq.server.concurrency-limit.availability-report=25 rhq.server.concurrency-limit.inventory-sync=10 rhq.server.concurrency-limit.content-report=5 rhq.server.concurrency-limit.content-download=5 rhq.server.concurrency-limit.measurement-report=10 rhq.server.concurrency-limit.measurement-schedule-request=10 rhq.server.concurrency-limit.configuration-update=10  # Content Local Filesystem Repository rhq.server.content.filesystem=$/packagebits  # The frequency (in millis) the server checks for updated plugins rhq.server.plugin-scan-period-ms=300000  # When this is enabled, the server at start up will compare its endpoint # address to the host name/address found on the host machine. If they differ, # the server endpoint address will be updated to the value found on the host # machine. This is targeted for use in cloud deployments where IP addresses # change frequently, but it can be of use in other deployment settings where # you have to deal with IP address changes. rhq.sync.endpoint-address=false  # When this is enabled, the server will request that agents send content for # for binary files that are being monitored for drift. The content for those # files will then be persisted on the server. By default, the server does not # persist content for well known binary file types like .ear, .war, .zip, .so, # etc. The server does however persist content for text files or any other # files that are not known binary types. #rhq.server.drift.store-binary-content=false  # The installer will create a default EAP management user named 'rhqadmin'. # The password is generated and obfuscated and specified here. This should # not be edited. rhq.server.management.password=-48a5a318c4946b8207a6df87216de44   ############################################################################# # Storage cluster configuration settings # # IMPORTANT NOTE: # - Storage Node properties will be stored in the database # after the initial install. The server will use database stored # properties during operation and after restarts. # - Additional servers in an HA topology will use database stored Storage # Node properties. So properties set in this configuration file will be # overriden on install with the database values. #############################################################################  # The username RHQ will use to authenticate against the Storage Cluster. # The value is generated and should not be edited. rhq.storage.username=dlkalkts  # The password RHQ will use to authenticate against the Storage Cluster. # The value is generated and obfuscated and should not be edited. rhq.storage.password=2d9950f423505d79df8592078de921bc  # A comma-delimited list of storage nodes. Each Storage node uses this list as # contact points to find other nodes in the cluster and learn the ring # topology. The RHQ server(s) use this list to connect to the cluster; # therefore, this property MUST BE SET in order for RHQ to talk to the Storage. # Cluster. The of an entry is as follows: # # hostname1,hostname2 # # Note that this is actually an installer setting. Changing the value after # installation will have no effect. rhq.storage.nodes=FG074  # The ports used by storage nodes to communicate with each other # and used by the RHQ server(s) to communicate with the cluster. # Both properties are required. # rhq.storage.cql-port=9142 rhq.storage.gossip-port=7100  ############################################################################# # Storage client settings # # The following are advanced settings the client (i.e., driver) that # communicates with the storage cluster #############################################################################  # The request limit will automatically change by this amount when there is a # topology change event. The change will be persisted to this file. Topology # change events include nodes being added/removed and nodes going up/down. # Defaults 30,000 if undefined.. If specified the value is parsed as a double. rhq.storage.request.limit.topology-delta=30000  # When a request times out, the request limit as specified by # rhq.storage.request.limit will be decreased. The change will be persisted to # this file. The value is parsed as a double and should be expressed as a # percentage (i.e., a value between 0 and 1). For example, a value of 0.3 means # that on a request timeout, the the request limit will decrease by 30%. # Defaults to 0.2 if undefined. rhq.storage.request.limit.timeout-delta=0.2  # If a request timeout occurs, there is a good possibility that it could be # followed by successive timeouts due to read/write patterns. This property # specifies a dampening period such that the request throughput will only be # decreased once for all timeouts that occur during said period. Defaults to # 30 seconds if undefined. The value is specified in milliseconds and is parsed # as a long. rhq.storage.request.limit.timeout-dampening=30000  # Sets the maximum throttling. In other words, the request limit will not # decrease lower than this value. Defaults to 5,000 if undefined. The value is # parsed as a double. rhq.storage.request.limit.min=5000  ############################################################################## # Metrics aggregation settings # # Note that if you commit the RHQ Server into inventory, these settings can be # managed through the resource configuration of the Measurement Subsystem. # Changes made through the Measurement Subsystem resource are applied # dynamically at runtime whereas directly editing these properties requires a # a server restart for changes to take effect. ##############################################################################  # Specifies the number of schedules for which data will be fetched per thread. # A higher value can improve aggregation performance at the cost of greater # memory utilization. rhq.metrics.aggregation.batch-size=5  # Specifies the number of batches that can be processed in parallel. A higher # value can improve aggregation performance at the cost of greater memory # utilization. rhq.metrics.aggregation.parallelism=3  # The number of threads to use during aggregation. It defaults to # ceiling(5, num_cores). rhq.metrics.aggregation.workers=4  # A limit, specified in days, on the age of raw data that is ingested. If raw # data has a timestamp that is more than limit days old, then it is not stored. # This prevents raw data that is for example a year old from being stored. rhq.metrics.data.age-limit=3 

und die rhq-storage.properties (Pastebin wegen Längenbeschränkung)

(alles als Kommentar, wie vorgeschlagen)

Wenn ich versuche zu laufen rhqctl install --start, erhalte ich folgende Fehler:

11:34:30,183 ERROR [org.rhq.enterprise.server.installer.InstallerServiceImpl] Failed to connect to the storage cluster. Please check the following: 1) At least one storage node is running 2) The rhq.storage.nodes property specifies the correct hostname/address of at least one storage node 3) The rhq.storage.cql-port property has the correct value  11:34:30,185 ERROR [org.rhq.enterprise.server.installer.Installer] The installer will now exit due to previous errors: java.lang.Exception: Could not connect to the storage cluster: All host(s) tried for query failed (tried: FG074/192.168.56.1 ([FG074/192.168.56.1] Cannot connect)) at org.rhq.enterprise.server.installer.InstallerServiceImpl.prepareStorageSchema(InstallerServiceImpl.java:767) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.InstallerServiceImpl.prepareDatabase(InstallerServiceImpl.java:684) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.InstallerServiceImpl.install(InstallerServiceJava HotSpot(TM) Client VM warning: ignoring option PermSize=128M; support was removed in 8.0 Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=128M; support was removed in 8.0 Impl.java:433) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.Installer.doInstall(Installer.java:135) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.Installer.main(Installer.java:59) [rhq-installer-util-4.13.0.jar:4.13.0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_77] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_77] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_77] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_77] at org.jboss.modules.Module.run(Module.java:292) [jboss-modules.jar:1.3.0.Final-redhat-2] at org.jboss.modules.Main.main(Main.java:455) [jboss-modules.jar:1.3.0.Final-redhat-2] 

Ich denke, dass es hier eine Lösung gibt, aber ich habe keinen Zugriff auf die Seite. Nach dem vorherigen Fehler erscheint auch dieser:

11:42:40,895 ERROR [org.rhq.enterprise.server.installer.InstallerServiceImpl] Could not complete storage cluster schema installation: All host(s) tried for query failed (tried: FG074/192.168.56.1 ([FG074/192.168.56.1] Cannot connect)): java.lang.RuntimeException: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: FG074/192.168.56.1 ([FG074/192.168.56.1] Cannot connect)) at org.rhq.cassandra.schema.VersionManager.drop(VersionManager.java:220) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.SchemaManager.drop(SchemaManager.java:147) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.InstallerServiceImpl.prepareStorageSchema(InstallerServiceImpl.java:726) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.InstallerServiceImpl.prepareDatabase(InstallerServiceImpl.java:684) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.InstallerServiceImpl.install(InstallerServiceImpl.java:433) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.Installer.doInstall(Installer.java:135) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.Installer.main(Installer.java:59) [rhq-installer-util-4.13.0.jar:4.13.0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_77] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_77] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_77] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_77] at org.jboss.modules.Module.run(Module.java:292) [jboss-modules.jar:1.3.0.Final-redhat-2] at org.jboss.modules.Main.main(Main.java:455) [jboss-modules.jar:1.3.0.Final-redhat-2] Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: FG074/192.168.56.1 ([FG074/192.168.56.1] Cannot connect)) at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:185) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:80) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:839) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster$Manager.access$100(Cluster.java:763) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster.<init>(Cluster.java:93) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster$Builder.build(Cluster.java:732) [cassandra-driver-core-1.0.8-jboss-1.jar:] at org.rhq.cassandra.util.ClusterBuilder.build(ClusterBuilder.java:130) [rhq-cassandra-util-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.SessionManager.initSession(SessionManager.java:33) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.AbstractManager.initClusterSession(AbstractJava HotSpot(TM) Client VM warning: ignoring option PermSize=128M; support was removed in 8.0 Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=128M; support was removed in 8.0 Manager.java:100) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.AbstractManager.initClusterSession(AbstractManager.java:90) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.VersionManager.drop(VersionManager.java:210) [rhq-cassandra-schema-4.13.0.jar:4.13.0] ... 12 more  11:42:40,899 ERROR [org.rhq.enterprise.server.installer.Installer] The installer will now exit due to previous errors: java.lang.Exception: Could not complete storage cluster schema installation: All host(s) tried for query failed (tried: FG074/192.168.56.1 ([FG074/192.168.56.1] Cannot connect)) at org.rhq.enterprise.server.installer.InstallerServiceImpl.prepareStorageSchema(InstallerServiceImpl.java:777) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.InstallerServiceImpl.prepareDatabase(InstallerServiceImpl.java:684) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.InstallerServiceImpl.install(InstallerServiceImpl.java:433) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.Installer.doInstall(Installer.java:135) [rhq-installer-util-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.Installer.main(Installer.java:59) [rhq-installer-util-4.13.0.jar:4.13.0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_77] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_77] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_77] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_77] at org.jboss.modules.Module.run(Module.java:292) [jboss-modules.jar:1.3.0.Final-redhat-2] at org.jboss.modules.Main.main(Main.java:455) [jboss-modules.jar:1.3.0.Final-redhat-2] Caused by: java.lang.RuntimeException: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: FG074/192.168.56.1 ([FG074/192.168.56.1] Cannot connect)) at org.rhq.cassandra.schema.VersionManager.drop(VersionManager.java:220) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.SchemaManager.drop(SchemaManager.java:147) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.enterprise.server.installer.InstallerServiceImpl.prepareStorageSchema(InstallerServiceImpl.java:726) [rhq-installer-util-4.13.0.jar:4.13.0] ... 10 more Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: FG074/192.168.56.1 ([FG074/192.168.56.1] Cannot connect)) at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:185) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:80) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:839) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster$Manager.access$100(Cluster.java:763) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster.<init>(Cluster.java:93) [cassandra-driver-core-1.0.8-jboss-1.jar:] at com.datastax.driver.core.Cluster$Builder.build(Cluster.java:732) [cassandra-driver-core-1.0.8-jboss-1.jar:] at org.rhq.cassandra.util.ClusterBuilder.build(ClusterBuilder.java:130) [rhq-cassandra-util-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.SessionManager.initSession(SessionManager.java:33) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.AbstractManager.initClusterSession(AbstractManager.java:100) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.AbstractManager.initClusterSession(AbstractManager.java:90) [rhq-cassandra-schema-4.13.0.jar:4.13.0] at org.rhq.cassandra.schema.VersionManager.drop(VersionManager.java:210) [rhq-cassandra-schema-4.13.0.jar:4.13.0] ... 12 more 

Wie kann ich diese Probleme lösen?