- 03 Sep, 2018 1 commit
-
-
Jérome Perrin authored
-
- 22 Jun, 2018 1 commit
-
-
Vincent Pelletier authored
Filename is split as an URL path, and joined in OS-dependent manner. Remove corresponding comment in all buildout.hash.cfg files.
-
- 09 Feb, 2018 1 commit
-
-
Jérome Perrin authored
See https://docs.influxdata.com/influxdb/v1.4/administration/config/#bind-address-127-0-0-1-8088 This should not be reachable from outside because it can be used to pull a backup. Because we usually have reachable ipv6 and local only ipv4, make it ipv4 and add a note in README because this is not always true. Also make ports use explicit names in profile and fix promise that should check http-port and not rpc-port
-
- 25 Jan, 2018 4 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
Otherwise telegraf start but does not create database and does not send data: ``` 2018-01-17T03:44:54Z I! Database creation failed: Post https://[2001:67c:1254:e:....]:8086/query?q=CREATE+DATABASE+%22telegraf%22: dial tcp [2001:67c:1254:e:....]:8086: getsockopt: connection refused 2018-01-17T03:44:54Z I! Starting Telegraf v1.6.0~90b6b760 2018-01-17T03:44:54Z I! Loaded outputs: influxdb 2018-01-17T03:44:54Z I! Loaded inputs: inputs.cpu inputs.mem inputs.disk inputs.diskio inputs.system 2018-01-17T03:44:54Z I! Tags enabled: host=f114dfe44f75 2018-01-17T03:44:54Z I! Agent Config: Interval:10s, Quiet:false, Hostname:"f114dfe44f75", Flush Interval:10s 2018-01-17T03:45:10Z E! InfluxDB Output Error: Response Error: Status Code [404], expected [204], [database not found: "telegraf"] 2018-01-17T03:45:10Z E! Error writing to output [influxdb]: Could not write to any InfluxDB server in cluster ``
-
Jérome Perrin authored
-