Influx Backup with backitup fails - /bin/sh: 1: influx: not found

[manoloxxl]

Description

Hi,

I've issues when i try to backup influx db with backitup inside iobroker container:

Error: Command failed: influx backup --bucket XXX --host http://X.X.X.X:8086 -t TOKEN "/opt/iobroker/backups/influxDB_2023_03_22-12_09_27_backupiobroker" /bin/sh: 1: influx: not found

Do i need to add a package also like it was needed for redis?

Best Regards

Manuel

Image version

7.2.0

Docker logs

Setting up arp-scan (1.9.7-2) ...
Setting up libhttp-date-perl (6.05-1) ...
Setting up libfile-listing-perl (6.14-1) ...
Setting up libnet-http-perl (6.20-1) ...
Setting up libwww-robotrules-perl (6.02-1) ...
Setting up libhtml-parser-perl (3.75-1+b1) ...
Setting up libio-socket-ssl-perl (2.069-1) ...
Setting up libhttp-message-perl (6.28-1) ...
Setting up libhtml-form-perl (6.07-1) ...
Setting up libhttp-negotiate-perl (6.01-1) ...
Setting up libhttp-cookies-perl (6.10-1) ...
Setting up libhtml-tree-perl (5.07-2) ...
Setting up libhtml-format-perl (2.12-1.1) ...
Setting up libnet-smtp-ssl-perl (1.04-1) ...
Setting up libmailtools-perl (2.21-1) ...
Setting up libhttp-daemon-perl (6.12-1+deb11u1) ...
Setting up libwww-perl (6.52-1) ...
Setting up liblwp-protocol-https-perl (6.10-1) ...
Processing triggers for libc-bin (2.31-13+deb11u5) ...
Done.
bluetooth is not installed. Installing...
sudo: unable to resolve host iobrokerW54: Name or service not known
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin: 
Selecting previously unselected package libapparmor1:amd64.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 30261 files and directories currently installed.)
Preparing to unpack .../0-libapparmor1_2.13.6-10_amd64.deb ...
Unpacking libapparmor1:amd64 (2.13.6-10) ...
Selecting previously unselected package dbus.
Preparing to unpack .../1-dbus_1.12.24-0+deb11u1_amd64.deb ...
Unpacking dbus (1.12.24-0+deb11u1) ...
Selecting previously unselected package libasound2-data.
Preparing to unpack .../2-libasound2-data_1.2.4-1.1_all.deb ...
Unpacking libasound2-data (1.2.4-1.1) ...
Selecting previously unselected package libasound2:amd64.
Preparing to unpack .../3-libasound2_1.2.4-1.1_amd64.deb ...
Unpacking libasound2:amd64 (1.2.4-1.1) ...
Selecting previously unselected package libdw1:amd64.
Preparing to unpack .../4-libdw1_0.183-1_amd64.deb ...
Unpacking libdw1:amd64 (0.183-1) ...
Selecting previously unselected package kmod.
Preparing to unpack .../5-kmod_28-1_amd64.deb ...
Unpacking kmod (28-1) ...
Selecting previously unselected package bluez.
Preparing to unpack .../6-bluez_5.55-3.1_amd64.deb ...
Unpacking bluez (5.55-3.1) ...
Selecting previously unselected package alsa-topology-conf.
Preparing to unpack .../7-alsa-topology-conf_1.2.4-1_all.deb ...
Unpacking alsa-topology-conf (1.2.4-1) ...
Selecting previously unselected package alsa-ucm-conf.
Preparing to unpack .../8-alsa-ucm-conf_1.2.4-2_all.deb ...
Unpacking alsa-ucm-conf (1.2.4-2) ...
Selecting previously unselected package bluetooth.
Preparing to unpack .../9-bluetooth_5.55-3.1_all.deb ...
Unpacking bluetooth (5.55-3.1) ...
Setting up libdw1:amd64 (0.183-1) ...
Setting up libapparmor1:amd64 (2.13.6-10) ...
Setting up kmod (28-1) ...
Setting up libasound2-data (1.2.4-1.1) ...
Setting up dbus (1.12.24-0+deb11u1) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up alsa-topology-conf (1.2.4-1) ...
Setting up libasound2:amd64 (1.2.4-1.1) ...
Setting up alsa-ucm-conf (1.2.4-2) ...
Setting up bluez (5.55-3.1) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of force-reload.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up bluetooth (5.55-3.1) ...
Processing triggers for libc-bin (2.31-13+deb11u5) ...
Processing triggers for dbus (1.12.24-0+deb11u1) ...
Done.
bluez is already installed.
libbluetooth-dev is not installed. Installing...
sudo: unable to resolve host iobrokerW54: Name or service not known
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin: 
Selecting previously unselected package libbluetooth3:amd64.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 30783 files and directories currently installed.)
Preparing to unpack .../libbluetooth3_5.55-3.1_amd64.deb ...
Unpacking libbluetooth3:amd64 (5.55-3.1) ...
Selecting previously unselected package libbluetooth-dev:amd64.
Preparing to unpack .../libbluetooth-dev_5.55-3.1_amd64.deb ...
Unpacking libbluetooth-dev:amd64 (5.55-3.1) ...
Setting up libbluetooth3:amd64 (5.55-3.1) ...
Setting up libbluetooth-dev:amd64 (5.55-3.1) ...
Processing triggers for libc-bin (2.31-13+deb11u5) ...
Done.
libudev-dev is already installed.
net-tools is already installed.
Done.
 
Registering maintenance script as command... Done.
 
--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------
 
Existing installation of ioBroker detected in "/opt/iobroker".
 
--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)setting permissions (This might take a while! Please be patient!)... Done.
 
Fixing "sudo-bug" by replacing sudo with gosu... Done.
 
Hostname in ioBroker matches the hostname of this container.
No action required.
 
--------------------------------------------------------------------------------
-----                Step 4 of 5: Applying special settings                -----
--------------------------------------------------------------------------------
 
Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).
 
IOB_BACKITUP_EXTDB is "true". Unlocking features... Done.
 
Checking for custom states db settings... 
IOB_STATESDB_TYPE is set and value meets detected ioBroker installation.
IOB_STATESDB_HOST is set and value meets detected ioBroker installation.
IOB_STATESDB_PORT is set and value meets detected ioBroker installation.
Done.
 
Userscript for first start detected and this is the first start of a new container.
Running userscript_firststart.sh... 
 
I'm your startscript userscript_firststart.sh. I will run only on the FIRST startup of the container.
 
sudo: unable to resolve host iobrokerW54: Name or service not known
sudo: unable to resolve host iobrokerW54: Name or service not known
sudo: unable to resolve host iobrokerW54: Name or service not known
sudo: unable to resolve host iobrokerW54: Name or service not known
sudo: unable to resolve host iobrokerW54: Name or service not known
sudo: unable to resolve host iobrokerW54: Name or service not known
Done.
 
Userscript for every start detected. Running userscript_everystart.sh... 
 
I'm your startscript userscript_everystart.sh. I will run on EVERY container startup.
 
Starting system message bus: dbus.
Starting bluetooth: bluetoothd.
Done.
 
--------------------------------------------------------------------------------
-----                    Step 5 of 5: ioBroker startup                     -----
--------------------------------------------------------------------------------
 
Starting ioBroker... 
 
##### #### ### ## # iobroker.js-controller log output # ## ### #### #####
host.iobrokerW54 check instance "system.adapter.admin.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.email.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.history.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.influxdb.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.javascript.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.hm-rega.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.hm-rpc.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.hm-rpc.1" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.hm-rpc.2" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.hm-rpc.3" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.mqtt.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.nuki-extended.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.radar2.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.sonoff.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.tr-064.1" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.backitup.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.daswetter.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.deconz.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.dwd.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.echarts.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.ecovacs-deebot.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.fahrplan.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.feiertage.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.jarvis.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.lgtv.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.musiccast.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.simple-api.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.tankerkoenig.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.tvspielfilm.0" for host "iobrokerW54"
host.iobrokerW54 check instance "system.adapter.web.0" for host "iobrokerW54"
Send diag info: {"uuid":"e2b7333e-5c23-0f2e-679d-de582b5c00c0","language":"de","country":"Germany","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.19.1","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"backitup":{"version":"2.5.12","platform":"Javascript/Node.js"},"daswetter":{"version":"3.1.7","platform":"Javascript/Node.js"},"deconz":{"version":"1.3.21","platform":"Javascript/Node.js"},"dwd":{"version":"2.8.3","platform":"Javascript/Node.js"},"echarts":{"version":"1.0.12","platform":"Javascript/Node.js"},"ecovacs-deebot":{"version":"1.4.13","platform":"Javascript/Node.js"},"email":{"version":"1.1.4","platform":"Javascript/Node.js"},"fahrplan":{"version":"1.2.2","platform":"Javascript/Node.js"},"feiertage":{"version":"1.1.0","platform":"Javascript/Node.js"},"history":{"version":"2.2.4","platform":"Javascript/Node.js"},"hm-rega":{"version":"3.0.44","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.15.16","platform":"Javascript/Node.js"},"influxdb":{"version":"3.2.0","platform":"Javascript/Node.js"},"jarvis":{"version":"2.2.5","platform":"Javascript/Node.js"},"javascript":{"version":"6.1.4","platform":"Javascript/Node.js"},"lgtv":{"version":"1.1.10","platform":"Javascript/Node.js"},"mqtt":{"version":"4.0.7","platform":"Javascript/Node.js"},"musiccast":{"version":"0.1.5","platform":"Javascript/Node.js"},"nuki-extended":{"version":"2.6.5","platform":"Javascript/Node.js"},"radar2":{"version":"2.0.7","platform":"Javascript/Node.js"},"rpi2":{"version":"1.2.0","platform":"javascript/Node.js"},"simple-api":{"version":"2.7.2","platform":"Javascript/Node.js"},"socketio":{"version":"3.0.9","platform":"Javascript/Node.js"},"sonoff":{"version":"2.5.1","platform":"Javascript/Node.js"},"tankerkoenig":{"version":"2.1.1","platform":"javascript/Node.js"},"tr-064":{"version":"4.2.18","platform":"Javascript/Node.js"},"tvspielfilm":{"version":"2.0.4","platform":"javascript/Node.js"},"web":{"version":"4.3.0","platform":"Javascript/Node.js"}},"statesType":"redis","objectsType":"jsonl","noInstances":30,"compactMode":false,"noCompactInstances":0,"model":"Common KVM processor","cpus":2,"mem":4121358336,"ostype":"Linux","city":"X"}
================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging]

[buanet]

Hi Manuel,

please read the docs: https://docs.buanet.de/iobroker-docker-image/docs/#backup-remote-databases-with-iobroker-backitup-in-docker
Thank you.

Regards,
André

[NOTE] I converted this issue to a discussion. Please do not use Issues for support questions.

[manoloxxl]

Hi André,

i followed those instructions and also the draft version with the help for extrenal backup. But for influx there is just a "Sorry, no information available/ not tested yet!

#"

So i decided to ask here :)

BTW:
Redis is working but it's needed to use the real IP of the host, also when it's on the same server. 127.0.0.1 does not work in backitup for redis, also when its working good in the iobroker-redis-config & ENV of your image.
Maybe you can add this as hint in your docs.

[buanet]

Hi Manuel,
the problem is, you opened an issue (the 2nd time) for a support question. This is not what it`s for.
If you got problems using the ioBroker Docker image, you can ask for help here, in discussions section, or join one of the ioBroker communities and ask your questions there.

As I personally think, backing up external databases with the help of iobroker.backitup adapter is not the way you should backup your databases in Docker, I will not invest time to complete the documentation at this point by figuring out how it's gonna work.
Nevertheless I hope if someone gets a solution to this, he or she may let me know what I have to put into the docs. :) Feel free to contribute!

Redis is working but it's needed to use the real IP of the host, also when it's on the same server. 127.0.0.1 does not work in backitup for redis, also when its working good in the iobroker-redis-config & ENV of your image.
Maybe you can add this as hint in your docs.

Of course 127.0.0.1 is not working! It`s on the same server, but it is running with Docker! Hopefully nobody told you to use the localhost ip address in the iobroker-redis-config & ENV. That's not the correct configuration.
Please do me a favour and get yourself some basic information about networking in Docker. They have one of the best docs website I've seen so far... https://docs.docker.com/network/
This is really essential for operating different Docker containers on your Docker host.

Regards,
André

[manoloxxl]

I can fully understand - the discussion part and also the db backup part. I must tell you, i just recognized this discussion option for git short time ago. Such backups should be done in another way (and i do it also by using proxmox backup server).
I just was trying what is working. I also think, this backitup backups should only be just an additional option.

For the localhost entry i was reading the doc (and yes, the doc is very good) and also some discussions. As in my case the ioBroker Container is running in host mode and the redis in bridge with published ports to the host, they can talk by using localhost option. This is handled by docker as far as i understud the discussions and also it reduces network traffic. But i'm not a docker pro, maybe i'm wrong.

I'm sure i will find another solution for future as i wanna give redis sentinel a try. I've seen, that its part of v8 of your image and i like to run my little setup a bit more reliable. That should be possible after switching to 3 Proxmox "Server" on Thin Clients. A bit oversized but i want to prevent restore work - this work always is needed whenver there is no time for :)

Thanks for your time!