influxdata / influxdata/kapacitor
kapacitor listen 9093
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
I understand that kapacitor can set the listening port by changing the bind-address of the configuration file
[http]
bind-address = ":9093"
auth-enabled = false
log-enabled = true
write-tracing = false
pprof-enabled = false
https-enabled = false
https-certificate = "/etc/ssl/kapacitor.pem"
shutdown-timeout = "10s"
shared-secret = ""
The bind-address value is changed to 9093, and the service starts with an error：
[srv] 2023/12/13 04:09:31 I! Kapacitor hostname: 9e98087f12ad
[srv] 2023/12/13 04:09:31 I! ClusterID: da070130-b2b4-445f-803c-14e060e001ce ServerID: bfcdbc20-63f1-4632-8fc0-99543dba5ced
[task_master:main] 2023/12/13 04:09:31 I! opened
[httpd] 2023/12/13 04:10:31 I! Closed HTTP service
[httpd] 2023/12/13 04:10:31 I! Closed HTTP service
[run] 2023/12/13 04:39:02 I! Kapacitor starting, version 1.3.1, branch master, commit 3b5512f7276483326577907803167e4bb213c613
[run] 2023/12/13 04:39:02 I! Go version go1.7.5
[srv] 2023/12/13 04:39:02 I! Kapacitor hostname: xxx
[srv] 2023/12/13 04:39:02 I! ClusterID: da070130-b2b4-445f-803c-14e060e001ce ServerID: bfcdbc20-63f1-4632-8fc0-99543dba5ced
[task_master:main] 2023/12/13 04:39:02 I! opened
Why did the changes to the config file not work
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the [http] bind-address setting in the Kapacitor 1.3.1 configuration and comparing it with the startup and HTTP service logs shown here. Done means determining why :9093 is not honored and documenting or fixing the configuration behavior so the service listens on the requested port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100