influxdata / influxdata/influxdb
influxdb does not bind 8086 to all address
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. Keep ipv6 enable on centos.
2. install influxdb-1.7.9-1
3. Keep default config which is (bind-address = ":8086")
4. Start influxd service
5. ss -aln
__Expected behavior:__
you should see 8086 is listen on all IP address
__Actual behavior:__
Describe
I only see 8086 was listen on ipv6 IP address. not on ipv4 (host's IP and 127.0.0.1)
[root@host influxdb]# ss -an | grep 8086
tcp LISTEN 0 128 :::8086
__Environment info:__
* System info: Linux 3.10.0-957.el7.x86_64 x86_64
* InfluxDB version: influxdb-1.7.9-1
* Other relevant environment details: Container runtime, disk info, etc
__Config:__
Use default config
__Logs:__
Include snippet of errors in log.

__Performance:__
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.
```sh
# Commands should be run when the bug is actively happening.
# Note: This command will run for at least 30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=true"
curl -o vars.txt "http://localhost:8086/debug/vars"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz`, `vars.txt`, and `iostat.txt` output files.
```
Contributor guide
Research direction
Reproduce the reported behavior with the default bind-address setting on Linux, starting the influxd service and checking port 8086 with ss -aln. Compare the expected IPv4 and IPv6 listeners with the actual output, then identify the bind-address handling involved; done means the default configuration listens on the intended addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100