influxdata / influxdata/influxdata-docker

Irregular SIGSEGV

Open
#364 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
364
Forks
255
Avg merge
3h 18m
Merged PRs (30d)
7

Description

I'm running into irregular SIGSEGVs from InfluxDB, to the point where it is able to kill the Docker deamon, or even an SSH on the Docker host. The versions are:

OS: Debian Buster in KVM
Docker: 5:19.03.5~3-0~debian-buster
InfluxDB: 1.7.8

InfluxDB conf: [influxdb.txt](https://github.com/influxdata/influxdata-docker/files/4110660/influxdb.txt)

Docker compose file: [docker-compose.txt](https://github.com/influxdata/influxdata-docker/files/4110653/docker-compose.txt)

Log from the docker container around the time of the segfault: [syslog-sigsegv.log](https://github.com/influxdata/influxdata-docker/files/4110621/syslog-sigsegv.log)

I have two containers, both of them are segfaulting in different intervals. Both of them are practically not used at all - just sitting there, filled with some data and very occasional access from Grafana running in another container.

Right now, I tried to upgrade to 1.7.9, to see if it helps, but I appreciate any ideas. Thanks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing syslog-sigsegv.log alongside docker-compose.txt and influxdb.txt, using the reported Debian, Docker, and InfluxDB versions as reproduction context. Compare behavior between InfluxDB 1.7.8 and 1.7.9 and document a reproducible cause or a concrete next step for the container crashes.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
databases, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.