I am using influxdb 1.7.9 version and facing “out of memory” issue while restarting influxd service. Also while running influx command to connect database it is giving “Failed to connect to http://localhost:8086 ”
This is the second time that I encounterred this issue, it has been worked well for more then 1 month.
I did change anything in influxdb.conf. The size of database looks well.
And I found influxd occupied the CPU
Request help on fixing these issues
List of issues:
Aug 23 03:22:40 ip-10-51-72-215 influxd: fatal error: runtime: out of memory
Aug 23 03:22:40 ip-10-51-72-215 systemd: influxdb.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Aug 23 03:22:40 ip-10-51-72-215 influxd: runtime stack:
Aug 23 03:22:40 ip-10-51-72-215 influxd: runtime.throw(0x1539721, 0x16)
Aug 23 03:22:40 ip-10-51-72-215 influxd: /usr/local/go/src/runtime/panic.go:617 +0x72
Aug 23 03:22:40 ip-10-51-72-215 influxd: runtime.sysMap(0xc024000000, 0x4000000, 0x3165998)
Aug 23 03:22:40 ip-10-51-72-215 influxd: /usr/local/go/src/runtime/mem_linux.go:170 +0xc7
Aug 23 03:22:40 ip-10-51-72-215 influxd: runtime.(*mheap).sysAlloc(0x314ca40, 0x2000, 0x314ca50, 0x1)
Thanks for your reply, what do you mean by "core dump ", I just created database, no other configuration. Influxd has been working well for more than 1 month, but now it can’t work even though I restart it again and again. Could you please tell me how to upgrade to 1.8 version safe? Since it can’t work, I can’t backup my database.
Core dumps are a dump of memory at the point a process crashes , here’s a generic page from arch that gives some background - note your distro might save them somewhere else, but a look under /tmp, and /var/lib/systemd/coredump
They are usually named core.12345 where 12345 was the pid number… basically that file is a dump from memory (which it ran out of) and can be analysed what it was full of / doing , at the point it died.
