Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Influxdb v1.5.1 not loading/reading the graphite configuration though setting the flag "enabled = true" #9635

Closed
kamalvpm777 opened this issue Mar 26, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@kamalvpm777
Copy link

commented Mar 26, 2018

Description : On installing the influxdb latest ver 1.5.1 and updating the config file with enabling the graphite value, then reloading the config still influxdb is not picking up the updated graphite value. Could someone take a look and provide your inputs on why influxdb is not picking up the graphite service when reloading with the updated config

Bug report

System info: [Include InfluxDB version, operating system name, and other relevant details]
Influx DB ver - 1.5.1
Operating system - Mac OS

Steps to reproduce:

  1. Update the config file(influxdb.conf) with below uncommented graphite values
    [[graphite]]

Determines whether the graphite endpoint is enabled.

enabled = true
database = "graphite"
retention-policy = ""
bind-address = ":2003"
protocol = "tcp"
consistency-level = "one"
batch-size = 5000
batch-pending = 10
batch-timeout = "1s"
udp-read-buffer = 0
separator = "."

  1. influxd -config /usr/local/etc/influxdb.conf
  2. Please verify the below output of above command, which doesnt have any entries related to graphite

__Expected behavior:
we expected to see the "Starting Graphite service with Batch details,addr" as part of updated config reload

__Actual behavior: As you can see it didnt load any service related to graphite on reloading the influxd with latest configuration

8888888 .d888 888 8888888b. 888888b.
888 d88P" 888 888 "Y88b 888 "88b
888 888 888 888 888 888 .88P
888 88888b. 888888 888 888 888 888 888 888 888 8888888K.
888 888 "88b 888 888 888 888 Y8bd8P' 888 888 888 "Y88b
888 888 888 888 888 888 888 X88K 888 888 888 888
888 888 888 888 888 Y88b 888 .d8""8b. 888 .d88P 888 d88P
8888888 888 888 888 888 "Y88888 888 888 8888888P" 8888888P"

2018-03-26T19:47:05.975318Z info InfluxDB starting {"log_id": "074yRrTl000", "version": "v1.5.1", "branch": "master", "commit": "cdae4ccde4c67c3390d8ae8a1a06bd3b4cdce5c5"}
2018-03-26T19:47:05.975346Z info Go runtime {"log_id": "074yRrTl000", "version": "go1.10", "maxprocs": 8}
run: open server: listen: listen tcp 127.0.0.1:8088: bind: address already in use

@mark-rushakoff

This comment has been minimized.

Copy link
Member

commented Mar 26, 2018

run: open server: listen: listen tcp 127.0.0.1:8088: bind: address already in use

You have an influxd instance or something else already running on 8088, so you need to shut down the other process, or change your configuration to use a different bind-address.

@kamalvpm777

This comment has been minimized.

Copy link
Author

commented Mar 27, 2018

Thanks for the help. This is solved by shutting down the influxd instances which was running at same port

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.