Let’s go back and run a command we did some while ago, to see whether the
result is still the same.
As root:
grep -r “808[678]” /etc
Also as root:
netstat -lptn | grep influx
Antony.
Let’s go back and run a command we did some while ago, to see whether the
result is still the same.
As root:
grep -r “808[678]” /etc
Also as root:
netstat -lptn | grep influx
Antony.
I tried , No results, both output blank
grep -r “808[678]” /etc
netstat -lptn | grep influx
Also Checked
$sudo netstat -lptn
No listen port on influx
grep -r “808[678]” /etc
netstat -lptn | grep influx
I tried , No results, both output blank
That is inconsistent with the following:
**Config file is default
[http]
#bind-address = “.8086” (default, commented)
You say you have a default influxdb.conf file (which should have :8086 in it,
and not .8086, but I’ll assume that’s a typo instead of copy&paste from the
file itself), and that that file contains the string “8086”, and yet you say
that the command:
grep -r “808[678]” /etc
produces nothing.
That either means:
a) you have typed at least one of the commands incorrectly
b) your influxdb.conf file is not under /etc (I expect it to be in /etc/influxdb)
c) the file has changed since you told me it contained:
#bind-address = “.8086” (default, commented)
Finally, if “netstat -lptn | grep influx” produced no output, then either:
a) you did not run it as root as requested, or
b) influxdb was not running at the time (please start it and re-run the netstat
command)
Antony.
I follow your points step by step.
System Restarted
goroutine 13655 [running]:
runtime.throw(0xfd75ae, 0xd)
/usr/local/go/src/runtime/panic.go:774 +0x5c fp=0x16b7868c sp=0x16b78678 pc=0x41644
runtime.(*mcache).refill(0x76ef1008, 0x1f)
/usr/local/go/src/runtime/mcache.go:140 +0xfc fp=0x16b786a0 sp=0x16b7868c pc=0x262ec
runtime.(*mcache).nextFree(0x76ef1008, 0x1f, 0x0, 0x40d5c, 0x37af974)
/usr/local/go/src/runtime/malloc.go:854 +0x7c fp=0x16b786c0 sp=0x16b786a0 pc=0x1b0f4
runtime.mallocgc(0xe0, 0x0, 0x0, 0x40)
/usr/local/go/src/runtime/malloc.go:1022 +0x7a0 fp=0x16b78728 sp=0x16b786c0 pc=0x1ba40
runtime.rawbyteslice(0xd8, 0x0, 0x0, 0x0)
/usr/local/go/src/runtime/string.go:272 +0x84 fp=0x16b78744 sp=0x16b78728 pc=0x5f908
runtime.stringtoslicebyte(0x0, 0x4d902a0, 0xd8, 0x4b505d0, 0x0, 0x0)
/usr/local/go/src/runtime/string.go:161 +0xa4 fp=0x16b78764 sp=0x16b78744 pc=0x5f354
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*ring).apply.func1(0x1dde0dd4, 0x1cbf668, 0x1892b140, 0x7a05000)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/ring.go:160 +0xc0 fp=0x16b787dc sp=0x16b78764 pc=0xd1187c
runtime.goexit()
/usr/local/go/src/runtime/asm_arm.s:868 +0x4 fp=0x16b787dc sp=0x16b787dc pc=0x73610
created by github.com/influxdata/influxdb/tsdb/engine/tsm1.(*ring).apply
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/ring.go:155 +0xb >
4.$influx ( this output showing not connection refused)
Failed to connect to http://localhost:8086: Get http://localhost:8086/ping: dial tcp [::1]:8086: connect: connection refused
Please check your connection settings and ensure ‘influxd’ is running.
$sudo netstat -lptn
Influxdb not listen any port
*** I tried to run again
$ sudo influxd
$ influx (failed to connect , the same problem)
Please go through my influxd config file, is copied below
# Bind address to use for the RPC service for backup and restore.
# bind-address ="127.0.0.0:8088"
[meta]
# Where the metadata/raft database is stored
dir = "/var/lib/influxdb/meta"
# Automatically create a default retention policy when creating a database.
# retention-autocreate = true
# If log messages are printed for the meta service
# logging-enabled = true
[data]
# The directory where the TSM storage engine stores TSM files.
dir = "/var/lib/influxdb/data"
# The directory where the TSM storage engine stores WAL files.
wal-dir = "/var/lib/influxdb/wal"
[http]
# auth-enabled = true
# pprof-enabled = false
# pprof-auth-enabled = true
# ping-auth-enabled = true
# Determines whether HTTP endpoint is enabled.
# enabled = true
# Determines whether the Flux query endpoint is enabled.
# flux-enabled = true
# Determines whether the Flux query logging is enabled.
# flux-log-enabled = false
# The bind address used by the HTTP service.
# bind-address = ":8086"
# Determines whether user authentication is enabled over HTTP/HTTPS.
# auth-enabled = false
# The default realm sent back when issuing a basic auth challenge.
# realm = "InfluxDB"
# Determines whether HTTP request logging is enabled.
# log-enabled = true
- $ sudo influxd (loading more files, then finally end like this;)
This seems like a strange way of starting influxd to me. You are running this
on Raspbian Stretch.
Previously you have been using the command “$ sudo systemctl start influxdb”
which looks far more standard to me.
If you start the service like that, does it still produce all these errors?
goroutine 13655 [running]:
runtime.throw(0xfd75ae, 0xd)
/usr/local/go/src/runtime/panic.go:774 +0x5c fp=0x16b7868c sp=0x16b78678
pc=0x41644 runtime.(*mcache).refill(0x76ef1008, 0x1f)
/usr/local/go/src/runtime/mcache.go:140 +0xfc fp=0x16b786a0 sp=0x16b7868c
pc=0x262ec runtime.(*mcache).nextFree(0x76ef1008, 0x1f, 0x0, 0x40d5c,
0x37af974) /usr/local/go/src/runtime/malloc.go:854 +0x7c fp=0x16b786c0
sp=0x16b786a0 pc=0x1b0f4 runtime.mallocgc(0xe0, 0x0, 0x0, 0x40)
/usr/local/go/src/runtime/malloc.go:1022 +0x7a0 fp=0x16b78728
sp=0x16b786c0 pc=0x1ba40 runtime.rawbyteslice(0xd8, 0x0, 0x0, 0x0)
/usr/local/go/src/runtime/string.go:272 +0x84 fp=0x16b78744 sp=0x16b78728
pc=0x5f908 runtime.stringtoslicebyte(0x0, 0x4d902a0, 0xd8, 0x4b505d0, 0x0,
0x0) /usr/local/go/src/runtime/string.go:161 +0xa4 fp=0x16b78764
sp=0x16b78744 pc=0x5f354
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*ring).apply.func1(0x1dde
0dd4, 0x1cbf668, 0x1892b140, 0x7a05000)
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/ring.go:160 +0xc0
fp=0x16b787dc sp=0x16b78764 pc=0xd1187c runtime.goexit()
/usr/local/go/src/runtime/asm_arm.s:868 +0x4 fp=0x16b787dc sp=0x16b787dc
pc=0x73610 created by
github.com/influxdata/influxdb/tsdb/engine/tsm1.(*ring).apply
/go/src/github.com/influxdata/influxdb/tsdb/engine/tsm1/ring.go:155 +0xb >
You need to find out why influxd is complaining that much when you start it
before it makes any sense to go further.
That output is beyond my expertise to diagnose, so:
a) please start influxd with the normal command:
$ sudo systemctl start influxdb
b) if that doesn’t work and you still get the same errors, I hope someone with
more understanding of what those errors mean can help you.
Regards,
Antony.
Thanks for your support and sparing time with me. I will try find a better solution.
I think the RPC service (backup restore) may be running, and blocked the normal operation. In previous days it working perfectly, when power & internet connection failed after it will not working.
We should find the solution.
“In previous days it working perfectly, when power & internet connection
failed after it will not working.”
I think it would have been very helpful for everyone involved if you had said
that from the start.
Antony.
@Pooh I READ ALL your instruction carefully, I’m getting write state
time=“2022-07-12T00:49:25Z” level=error msg=“Couldn’t write stats” error=“Post "http://:3000/write?consistency=&db=performance&precision=ns&rp=": dial tcp 52.42.122.103:3000: connect: connection timed out” output=InfluxDBv
it seem like , i’m having two influxd port running with tcp/tcp6
tcp 0 0 127.0.0.1:8088 LISTEN 8460/influxd
tcp6 0 0 :::8086 LISTEN 8460/influxd
As stated in the documentation,
reporting-disabled = false
http-bind-address = “127.0.0.1:8086”
[data]
dir = “/var/lib/influxdb/data”
wal-dir = “/var/lib/influxdb/wal”
[http]
enabled = true
bind-address = “:8086”
Can u advice what’s possible wrong in my configuration
I am building up an installation on a Raspberry Pi 3 that I had laying around.
I just had exactly the same issue.
Actually, according to
sudo netstat -tulpn | grep LISTEN
influxdb was already using the port … very strange.
My solution was to remove the installation of influxDB that was there.
sudo apt-get purge influxdb
After this I installed InfluxDB v2.6 based on the instructions here: Install InfluxDB | InfluxDB OSS 2.6 Documentation
No special / additional config was needed.
After this, it just worked without any issue.
Hope this helps others as well.