raintank / raintank-collector

Raintank Remote Collector Agent
26 stars 4 forks source link

404 Error #46

Open kisienya opened 8 years ago

kisienya commented 8 years ago

Hi,

Thanks for this initiative.

I am configuring a private probe on fedora 22, Grafana 3.0. My config.json is as follows

{ "collector": { "name": "customName" }, "numCPUs": 1, "serverUrl": "https://app.raintank.io", "apiKey": "", "probeServerPort": 8284, "logLevel": "ALL" }

I get the following error

[2016-04-30 00:30:16.605] [ERROR] PID:7933 - serviceManager connection error. { [Error: websocket error] description: { [Error: unexpected server response (404)] target: { domain: null, _events: [Object], _maxListeners: 10, _socket: null, _ultron: null, _closeReceived: false, bytesReceived: 0, readyState: 0, supports: [Object], extensions: {}, _isServer: false, url: 'wss://app.raintank.io/socket.io/?apiKey=eyJrIjoiM2N0MlA1U2NrTnNKbEZ2ekFXM1pMVkVERWVkMnFmZXUiLCJuIjoiYWRtaW5FZGl0S2V5IiwiaWQiOjJ9&name=monitor.alkira.com&version=0.1.4&EIO=3&transport=websocket', protocolVersion: 13, binaryType: 'buffer' } } } Error: websocket error at WS.Transport.onError (/opt/raintank-collector/node_modules/socket.io-client/node_modules/engine.io-client/lib/transport.js:62:13) at WebSocket.ws.onerror (/opt/raintank-collector/node_modules/socket.io-client/node_modules/engine.io-client/lib/transports/websocket.js:135:10) at WebSocket.onError (/opt/raintank-collector/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:428:14) at WebSocket.emit (events.js:95:17) at ClientRequest.response (/opt/raintank-collector/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:696:12) at ClientRequest.g (events.js:180:16) at ClientRequest.emit (events.js:95:17) at HTTPParser.parserOnIncomingClient as onIncoming at HTTPParser.parserOnHeadersComplete as onHeadersComplete at CleartextStream.socketOnData as ondata

What am I doing wrong? Whats the meaning of "serverUrl" in config.json? Is there a simpler way of installing on fedora 22 using yum as there is on ubuntu using apt?

Many thanks for your help

woodsaj commented 8 years ago

the server_url is the address of the backend system that controlls the collectors. But the address should be "https://worldping-api.raintank.io"

kisienya commented 8 years ago

Much appreciate the reply. An improvement...... Now it says "invalid API key". I have generated my key using the local grafana. The key seems to connect with curl -H "Authorization: Bearer " https://mygrafanaserver:3000/

kisienya commented 8 years ago

I am getting ####################################################### [2016-04-30 02:28:49.040] [INFO] PID:7911 - starting up raintank-probe server [2016-04-30 02:28:49.052] [INFO] PID:7911 - launching worker process. [2016-04-30 02:28:49.076] [INFO] PID:7911 - raintank-probe server starting up on port 8284

[2016-04-30 02:28:50.255] [INFO] PID:7914 - connected to socket.io server [2016-04-30 02:28:50.278] [ERROR] PID:7914 - controller emitted an error - Invalid API Key [2016-04-30 02:28:50.283] [INFO] PID:7914 - disconnected from socket.io server. io client disconnect [2016-04-30 02:28:50.288] [ERROR] PID:7911 - worker 7914 died, restarting. [2016-04-30 02:28:50.289] [INFO] PID:7911 - 1 restarts in last 2 minutes. [2016-04-30 02:28:51.533] [INFO] PID:7924 - connected to socket.io server [2016-04-30 02:28:51.604] [ERROR] PID:7924 - controller emitted an error - Invalid API Key [2016-04-30 02:28:51.609] [INFO] PID:7924 - disconnected from socket.io server. io client disconnect [2016-04-30 02:28:51.613] [ERROR] PID:7911 - worker 7924 died, restarting. [2016-04-30 02:28:51.613] [INFO] PID:7911 - 2 restarts in last 2 minutes. [2016-04-30 02:28:52.908] [INFO] PID:7930 - connected to socket.io server [2016-04-30 02:28:52.993] [ERROR] PID:7930 - controller emitted an error - Invalid API Key [2016-04-30 02:28:52.998] [INFO] PID:7930 - disconnected from socket.io server. io client disconnect [2016-04-30 02:28:53.002] [ERROR] PID:7911 - worker 7930 died, restarting. [2016-04-30 02:28:53.002] [INFO] PID:7911 - 3 restarts in last 2 minutes. [2016-04-30 02:28:54.186] [INFO] PID:7936 - connected to socket.io server [2016-04-30 02:28:54.207] [ERROR] PID:7936 - controller emitted an error - Invalid API Key [2016-04-30 02:28:54.213] [INFO] PID:7936 - disconnected from socket.io server. io client disconnect [2016-04-30 02:28:54.216] [ERROR] PID:7911 - worker 7936 died, restarting. [2016-04-30 02:28:54.216] [INFO] PID:7911 - 4 restarts in last 2 minutes. [2016-04-30 02:28:55.452] [INFO] PID:7942 - connected to socket.io server [2016-04-30 02:28:55.471] [ERROR] PID:7942 - controller emitted an error - Invalid API Key [2016-04-30 02:28:55.475] [INFO] PID:7942 - disconnected from socket.io server. io client disconnect [2016-04-30 02:28:55.479] [ERROR] PID:7911 - worker 7942 died, restarting. [2016-04-30 02:28:55.479] [INFO] PID:7911 - 5 restarts in last 2 minutes. [2016-04-30 02:28:56.726] [INFO] PID:7948 - connected to socket.io server [2016-04-30 02:28:56.776] [ERROR] PID:7948 - controller emitted an error - Invalid API Key [2016-04-30 02:28:56.785] [INFO] PID:7948 - disconnected from socket.io server. io client disconnect [2016-04-30 02:28:56.790] [ERROR] PID:7911 - worker 7948 died, restarting. [2016-04-30 02:28:56.790] [INFO] PID:7911 - 6 restarts in last 2 minutes. [2016-04-30 02:28:56.791] [FATAL] PID:7911 - workers are restarting too quickly.

########################################################