influxdata / influxdata/influxdb

infuxdb2 starts with failure after update to 2.4.0.1 on Ubuntu focal on RPi 4 and does not start either after reinstall

Open
#23,679 0 comments 0 reactions 0 assignees View on GitHub
kind/bug team/edge team/ui
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

## About the bug

**Steps to reproduce:**
List the minimal actions needed to reproduce the behavior.

Did an update of influxdb2 yesterday.
Followup: removed inflluxdb2 completely, reinstalled from "deb [signed-by=/etc/apt/trusted.gpg.d/influxdb.gpg] https://repos.influxdata.com/ubuntu focal stable"
after that InfluxDB does not start because of "influxdb.service: Failed at step EXEC spawning /usr/lib/influxdb/scripts/influxd-systemd-start.sh: No such file or directory"
starting "influx" from command line as root works.

-- failure where I came from

1. influxdb started
sudo systemctl status influxdb
● influxdb.service - InfluxDB is an open-source, distributed, time series database
Loaded: loaded (/lib/systemd/system/influxdb.service; enabled; vendor preset: enabled)
Active: activating (start) since Tue 2022-08-23 07:52:01 CEST; 1min 14s ago
Docs: https://docs.influxdata.com/influxdb/
Cntrl PID: 47928 (influxd-systemd)
Tasks: 12 (limit: 2101)
CGroup: /system.slice/influxdb.service
├─47928 /bin/bash -e /usr/lib/influxdb/scripts/influxd-systemd-start.sh
├─47929 /usr/bin/influxd
└─47963 curl -k -s -o /dev/null http://localhost:8086/ready -w %{http_code}

Aug 23 07:52:10 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:10.198489Z lvl=info msg="Reading file" log_id=0cUJygMW000 service=storage-engine engine=tsm1 service=cacheloader path=/var/lib>
Aug 23 07:52:10 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:10.813870Z lvl=info msg="Opened shard" log_id=0cUJygMW000 service=storage-engine service=store op_name=tsdb_open index_version>
Aug 23 07:52:11 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:11.761825Z lvl=info msg="Opened shard" log_id=0cUJygMW000 service=storage-engine service=store op_name=tsdb_open index_version>
Aug 23 07:52:11 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:11.773940Z lvl=info msg="Open store (end)" log_id=0cUJygMW000 service=storage-engine service=store op_name=tsdb_open op_event=>
Aug 23 07:52:11 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:11.774888Z lvl=info msg="Starting retention policy enforcement service" log_id=0cUJygMW000 service=retention check_interval=30m
Aug 23 07:52:11 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:11.775936Z lvl=info msg="Starting precreation service" log_id=0cUJygMW000 service=shard-precreation check_interval=10m advance>
Aug 23 07:52:11 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:11.781141Z lvl=info msg="Starting query controller" log_id=0cUJygMW000 service=storage-reads concurrency_quota=1024 initial_me>
Aug 23 07:52:11 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:11.788308Z lvl=info msg="Configuring InfluxQL statement executor (zeros indicate unlimited)." log_id=0cUJygMW000 max_select_po>
Aug 23 07:52:11 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:11.853131Z lvl=info msg=Listening log_id=0cUJygMW000 service=tcp-listener transport=http addr=:8086 port=8086
Aug 23 07:52:11 mosquitto01 influxd-systemd-start.sh[47929]: ts=2022-08-23T05:52:11.853473Z lvl=info msg=Starting log_id=0cUJygMW000 service=telemetry interval=8h

2. Opened influx GUI, entering user credentials, creating a query on data
3. some time it gives "unauthorised access", mostly just a session time out
4. some times it just didn't answer
5. "sudo systemctl restart influxes" just hangs without any notice.

**Expected behavior:**

Just showing the data of a query

**Actual behavior:**

3. some time it gives "unauthorised access", mostly just a session time out
4. some times it just didn't answer
5. "sudo systemctl restart influxes" just hangs without any notice.
**Visual Proof:**

image

## About your environment

**Environment info:**

Linux 5.4.0-1065-raspi aarch64
InfluxDB v2.4.0 (git: de247bab08) build_date: 2022-08-18T19:41:08Z
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 14996236 11064676 3277984 78% /

**Config:**

**Logs:**

**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.
# 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

Open the contributing guide

Research direction

Start by reproducing the package installation on Ubuntu focal for a Raspberry Pi 4, then inspect the influxdb.service unit and /usr/lib/influxdb/scripts/influxd-systemd-start.sh, comparing service startup with running influxd directly. Check the reported authorization, timeout, and restart behavior; done means the packaged service starts reliably after installation and the GUI remains usable for queries.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, linux, ubuntu
Domain
databases, devops, operating-systems
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.