VIKEnut'
VIKEnut'
Melden Sie sich anEinloggen

De

RuEsPt
 
cassandradatastaxopscenter

datastax Opscenter kann keine Knoten hinzufügen, "Fehler beim Bereitstellen des Clusters: Anforderungs-ID ist ungültig",

Update 2

Da war einFehle In Opscenter stimmt die dsc22-Konfiguration nicht mit der Cassandra-Community-Version überein.

Aktualisiere

Nach dem erneuten Lesen des opscenter-Protokolls glaube ich, dass tatsächlich etwas mit den 4 Authentifizierungsfeldern oder einer ssh-Konfiguration nicht stimmt, aber ich weiß immer noch nicht, was genau zu tun ist )

das Szenario sieht wie folgt aus:

Ich habe 4 Knoten mit vagrant und ansible installiert, von denen jeder über dsc22, opscenter (redundant, wie ich weiß), Datastax-Agent, Cassandra-Tool und Oracle Java 8 verfügt.configuration belownodetool Status, alles ist gut, alle sehen sichIch erstelle einen Keyspace, er wird auf alle Nodes repliziert.uf meinem Host-Rechner öffne ich den Datenstützpunkt zum Beispiel über den weitergeleiteten Port von node0 Zum ersten Mal sehe ich zwei Möglichkeitenadd existing cluster odermanage existing one Wenn ich versuche, einen vorhandenen Cluster zu verwalten> 192.168.50.3 hinzufügen, wird Folgendes angezeigt:So versuche ich, 127.0.0.1 zu verwenden, es funktioniert einwandfrei, aber ich sehe nur diesen lokalen Cassandra-Rechnerknoten.So versuche ich Knoten von innen hinzuzufügen, wenn ich einen Dialog erhalte Ich denke, das ist wichtig) Es hat Anmeldeinformationsfelder, die ich als admin, admin für das Repository und admin, admin für den lokalen Benutzernamen hinzufüge. Ich weiß nicht, was ich in diese 4 Felder einfügen soll, ob diese erstellt wurden oder woanders vorkonfiguriert sind. Nachdem ich dem Rechenzentrum einen Knoten mit RAC-Informationen usw. hinzugefügt habe, wird die Meldung "Fehler beim Bereitstellen des Clusters: Anforderungs-ID ist ungültig" angezeigt.

Ich habe keine Ahnung, wo das Problem liegt. Der einzige unbekannte Schritt, den ich ausgeführt habe, war die Berechtigungsnachweissache (Repository-Benutzername / Pass, lokaler Benutzername / Pass), wenn ich Knoten von innen hinzufüge. Aber warum kann ich das bestehende verwalten nicht von Anfang an wo ich nur rein komme wenn ich 127.0.0.1 als ip benutze.

So ist hier der Datastax-Agent:

Starting DataStax agent monitor datastax_agent_monitor.
 INFO [main] 2015-08-24 22:39:59,506 Loading conf files: /var/lib/datastax-agent/conf/address.yaml
  INFO [main] 2015-08-24 22:39:59,657 Java vendor/version: Java HotSpot(TM) 64-Bit Server VM/1.8.0_60
  INFO [main] 2015-08-24 22:39:59,657 DataStax Agent version: 5.2.0
  INFO [main] 2015-08-24 22:39:59,732 Default config values: {:cassandra_port 9042, :rollups300_ttl 2419200, :settings_cf "settings", :restore_req_update_period 60, :my_$
  INFO [main] 2015-08-24 22:39:59,740 Waiting for the config from OpsCenter
  INFO [main] 2015-08-24 22:39:59,752 Starting Stomp
  INFO [main] 2015-08-24 22:39:59,752 Starting up agent communcation with OpsCenter.
  INFO [main] 2015-08-24 22:39:59,753 Reconnecting to a backup OpsCenter instance
  INFO [main] 2015-08-24 22:39:59,756 SSL communication is disabled
  INFO [main] 2015-08-24 22:39:59,757 Creating stomp connection to 192.168.50.3:61620
  INFO [async-dispatch-1] 2015-08-24 22:39:59,756 Using 127.0.0.1 as the cassandra broadcast address
  INFO [async-dispatch-1] 2015-08-24 22:39:59,762 New JMX connection (127.0.0.1:7199)
  INFO [StompConnection receiver] 2015-08-24 22:39:59,787 Reconnecting in 0s.
  INFO [main] 2015-08-24 22:39:59,791 Starting Jetty server: {:join? false, :ssl? false, :host nil, :port 61621}
  INFO [StompConnection receiver] 2015-08-24 22:39:59,872 Connected to 192.168.50.3:61620
  INFO [StompConnection receiver] 2015-08-24 22:40:00,200 Got new config from OpsCenter [note values in address.yaml override those from OpsCenter]: {:cassandra_port 904$
  INFO [StompConnection receiver] 2015-08-24 22:40:00,224 Starting up agent collection.
  INFO [StompConnection receiver] 2015-08-24 22:40:00,225 New JMX connection (127.0.0.1:7199)
  INFO [Jetty] 2015-08-24 22:40:00,347 Jetty server started
  INFO [StompConnection receiver] 2015-08-24 22:40:00,452 agent RPC address is  127.0.0.1
  INFO [async-dispatch-1] 2015-08-24 22:40:00,454 cassandra RPC address is  nil
  INFO [StompConnection receiver] 2015-08-24 22:40:00,471 Starting OS metric collectors (Linux)
  INFO [StompConnection receiver] 2015-08-24 22:40:00,516 Starting Cassandra JMX metric collectors
  INFO [install-location-finder] 2015-08-24 22:40:00,614 New JMX connection (127.0.0.1:7199)
  INFO [StompConnection receiver] 2015-08-24 22:40:00,639 New JMX connection (127.0.0.1:7199)
  INFO [StompConnection receiver] 2015-08-24 22:40:00,793 New JMX connection (127.0.0.1:7199)
  INFO [clojure-agent-send-off-pool-0] 2015-08-24 22:40:02,094 Attempting to load stored metric values.

Hier ist das vollständige Opscenter-Protokollhttp: //pastebin.com/fXT2vkF Folgendes ist ein Ausschnitt daraus:

 2015-08-24 23:13:38+0000 [Test_Cluster]  WARN: Ignoring scheduled job with type=best-practice, which is only supported with DataStax Enterprise.
2015-08-24 23:13:38+0000 [Test_Cluster]  INFO: Done loading persisted scheduled job descriptions
2015-08-24 23:13:40+0000 [Test_Cluster]  INFO: Using 192.168.50.4 as the RPC address for node 127.0.0.1
2015-08-24 23:13:40+0000 [Test_Cluster]  INFO: Node <Node 127.0.0.1='-6574032654670847999'> changed version to {'search': None, 'jobtracker': None, 'tasktracker': None, 'spark': {u'master': None, u'version': None, u'worker': None}, 'dse': None, 'cassandra': u'2.2.0'}
2015-08-24 23:13:40+0000 [Test_Cluster]  INFO: Processing spark version {u'master': None, u'version': None, u'worker': None}
2015-08-24 23:13:40+0000 [Test_Cluster]  INFO: Node <Node 127.0.0.1='-6574032654670847999'> changed version to {u'search': None, u'jobtracker': None, u'tasktracker': None, u'spark': {u'master': None, u'version': None, u'worker': None}, u'dse': None, u'cassandra': u'2.2.0'}
2015-08-24 23:13:40+0000 [Test_Cluster]  INFO: Processing spark version {u'master': None, u'version': None, u'worker': None}
2015-08-24 23:13:40+0000 [Test_Cluster]  INFO: Node 127.0.0.1 changed its mode to normal
2015-08-24 23:13:40+0000 [Test_Cluster]  INFO: Done loading persisted alert rules
2015-08-24 23:13:41+0000 [Test_Cluster]  INFO: OpsCenter starting up.
2015-08-24 23:13:42+0000 [Test_Cluster]  INFO: Using 192.168.50.2 as the RPC address for node 127.0.0.1
2015-08-24 23:13:42+0000 [Test_Cluster]  INFO: Node <Node 127.0.0.1='-6574032654670847999'> changed version to {'search': None, 'jobtracker': None, 'tasktracker': None, 'spark': {u'master': None, u'version': None, u'worker': None}, 'dse': None, 'cassandra': u'2.2.0'}
2015-08-24 23:13:42+0000 [Test_Cluster]  INFO: Processing spark version {u'master': None, u'version': None, u'worker': None}
2015-08-24 23:13:42+0000 [Test_Cluster]  INFO: Node <Node 127.0.0.1='-6574032654670847999'> changed version to {u'search': None, u'jobtracker': None, u'tasktracker': None, u'spark': {u'master': None, u'version': None, u'worker': None}, u'dse': None, u'cassandra': u'2.2.0'}
2015-08-24 23:13:42+0000 [Test_Cluster]  INFO: Processing spark version {u'master': None, u'version': None, u'worker': None}
2015-08-24 23:13:42+0000 [Test_Cluster]  INFO: Node 127.0.0.1 changed its mode to normal
2015-08-24 23:13:42+0000 []  INFO: Starting to update agents' configuration
2015-08-24 23:13:47+0000 [Test_Cluster]  INFO: Using 192.168.50.5 as the RPC address for node 127.0.0.1
2015-08-24 23:13:48+0000 [Test_Cluster]  INFO: Using 192.168.50.4 as the RPC address for node 127.0.0.1
2015-08-24 23:13:49+0000 [Test_Cluster]  INFO: Using 192.168.50.3 as the RPC address for node 127.0.0.1
2015-08-24 23:13:49+0000 [Test_Cluster]  INFO: Node <Node 127.0.0.1='-6574032654670847999'> changed version to {'search': None, 'jobtracker': None, 'tasktracker': None, 'spark': {u'master': None, u'version': None, u'worker': None}, 'dse': None, 'cassandra': u'2.2.0'}
2015-08-24 23:13:49+0000 [Test_Cluster]  INFO: Processing spark version {u'master': None, u'version': None, u'worker': None}
2015-08-24 23:13:49+0000 [Test_Cluster]  INFO: Node <Node 127.0.0.1='-6574032654670847999'> changed version to {u'search': None, u'jobtracker': None, u'tasktracker': None, u'spark': {u'master': None, u'version': None, u'worker': None}, u'dse': None, u'cassandra': u'2.2.0'}
2015-08-24 23:13:49+0000 [Test_Cluster]  INFO: Processing spark version {u'master': None, u'version': None, u'worker': None}
2015-08-24 23:13:49+0000 [Test_Cluster]  INFO: Node 127.0.0.1 changed its mode to normal
2015-08-24 23:13:58+0000 [Test_Cluster]  INFO: Using 192.168.50.3 as the RPC address for node 127.0.0.1
2015-08-24 23:13:58+0000 [Test_Cluster]  INFO: Using 192.168.50.2 as the RPC address for node 127.0.0.1
2015-08-24 23:14:22+0000 []  INFO: Testing SSH connectivity to 192.168.50.4
2015-08-24 23:14:23+0000 []  INFO: Testing SSH login to 192.168.50.4
2015-08-24 23:14:29+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed

2015-08-24 23:14:29+0000 []  INFO: Sleeping before retrying ssh login.
2015-08-24 23:14:41+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed

2015-08-24 23:14:41+0000 []  INFO: Sleeping before retrying ssh login.
2015-08-24 23:14:52+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed

2015-08-24 23:14:52+0000 []  INFO: Sleeping before retrying ssh login.
2015-08-24 23:15:03+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed

2015-08-24 23:15:03+0000 []  INFO: Sleeping before retrying ssh login.
2015-08-24 23:15:14+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed

2015-08-24 23:15:14+0000 []  INFO: Sleeping before retrying ssh login.
2015-08-24 23:15:26+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed

2015-08-24 23:15:26+0000 []  INFO: Sleeping before retrying ssh login.
2015-08-24 23:15:38+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed

2015-08-24 23:15:38+0000 []  INFO: Sleeping before retrying ssh login.
2015-08-24 23:15:50+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed

2015-08-24 23:15:50+0000 []  INFO: Sleeping before retrying ssh login.
2015-08-24 23:16:01+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed

2015-08-24 23:16:01+0000 []  INFO: Sleeping before retrying ssh login.
2015-08-24 23:16:13+0000 [] There was a problem verifying an ssh login on 192.168.50.4
    Traceback (most recent call last):
    Failure: opscenterd.SecureShell.SshFailed: ssh to u'192.168.50.4' failed
Aufba

Ich benutze Vagrant, um meine VMS mit @ zu erstelle

... a section from the vagrantfile
config.vm.define "node02" do |node|
    node.vm.host_name = "node02"
    node.vm.network :forwarded_port, guest: 8888, host: 3023
    node.vm.network "private_network", ip: "192.168.50.2", virtualbox__intnet: "intnet"
end
...

Ein Abschnitt aus der cassandra.yaml in jedem Knoten

- seeds: "192.168.50.xx, 192.168.50.xx, ... rest of nodes"

Die address.yaml in jedem Knoten

# couple of nodes that have opscenter
# The following hosts line is commented out because when I use it the datastax-agent doesn't connect to any nodes, so I guess the default is 127.0.0.1 which works fine
# hosts: ["192.168.50.xx","192.168.50.xx"]

local_interface: 127.0.0.1

# opscenter ip
stomp_interface: 192.168.50.xx  
# this nodeXX ip
agent_rpc_broadcast_address: 192.168.50.xx

Abschnitt aus cassandra-env.sh, Anmerkung Ich verwende keine Authentifizierung für jmx

LOCAL_JMX=NO

if [ "$LOCAL_JMX" = "yes" ]; then
  JVM_OPTS="$JVM_OPTS -Dcassandra.jmx.local.port=$JMX_PORT -XX:+DisableExplicitGC"
else
  JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.port=$JMX_PORT"
  JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.rmi.port=$JMX_PORT"
  JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.ssl=false"
  JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.authenticate=false"

nodetool status:

--  Address       Load       Tokens       Owns    Host ID                               Rack
UN  192.168.50.2  982.74 KB  256          ?       a35..  RAC1
UN  192.168.50.3  679.05 KB  256          ?       e6c..  RAC1
UN  192.168.50.4  912.1 KB   256          ?       634..  RAC1
UN  192.168.50.5  939.55 KB  256          ?       0a...  RAC1
Zu kommentieren

Antworten auf die Frage(0)

Ihre Antwort auf die Frage

Top Fragen

0 die antwort

Git als Backup- und Versionskontrollsystem

0 die antwort

Abhängigkeitsinjektion mit Autodraht = &quot;Konstruktor&quot;, wenn mehrere Konstruktoren vorhanden sind?

0 die antwort

Wie bekomme ich alle Schlüssel mit dem gleichen höchsten Wert?

0 die antwort

iOS 7 NSURLSession Mehrere Dateien im Hintergrund herunterladen

0 die antwort

Was sind die funktionalen Unterschiede zwischen einfach und doppelt zitierten HTML-Attributen?