Influxdb timeout preventing daemon from starting #1275
Comments
kizniche
changed the title
Bingo-Curios
changed the title
kizniche
changed the title
|
The title should only be a brief explanation of the issue. Do not put more than a few words in it. Please attach your Mycodo/install/setup.log. |
kizniche
changed the title
|
ok ... let me do this again, the last log I have is the successful log. I will attempt it again on the zero and capture the log. |
|
Here is the setuplog of a fresh install ... looks like it was timing out on connecting to the db. ... this was done on the Raspberry Pi Zero |
|
This does not look like the initial install because influxdb was already installed. Is this the case? |
|
yes... because, I deleted the successful install from Pi 4 and reinstalled... if you want a clean one done, I can rebuild all the way from the OS. |
|
You can't "delete an install", you deleted a directory and reinitiated an install that merely skipped many of the install processes that had already been completed. Without the log from the initial install, it's impossible to know what, if anything, went wrong during the initial install. |
|
now doing a full install.. just rebuilt my SD card with the OS and going on to install Mycodo |
|
Which OS? |
|
Raspberry PI OS Lite 32 bit |
|
Here is the new setup.log file after a full fresh install. Sequence - |
|
No idea what could be wrong. Do you get any errors attempting to start the daemon manually? (Note: do not run the daemon in a production environment this way). |
|
Daemon start okay when started manually. Here are a few other observations if it helps: If I restart the system, the daemon will not start. It will start if started manually as you mention above. This is on the Pi Zero Let me know if any other logs will help. |
|
I have the same error on a fresh install, also Raspberry Pi zero with same OS: Raspberry PI OS Lite 32 bit |
|
What is the status? |
|
gg@hector:~ $ sudo service mycodo status |
|
Looks like it's stuck on ExecStartPre Line 12 in 247adbf Which checks if influxdb is accessible What is the status of influxdb? |
|
aah the good old influxdb loop gg@hector:~ $ sudo service influxdb status Feb 15 15:47:15 hector influxd-systemd-start.sh[18243]: InfluxDB API unavailable after 31 attempts... |
|
Perhaps try increasing the timeout in the service file, as this comment suggests. |
|
so create this file /etc/systemd/system/influxdb.service.d/override.conf |
|
I've never used an override, I've always just edited the service file itself. You can see in the output you pasted the location of the file. Don't forget to issue the daemon-reload command. Then you can issue |
|
ok, and then just add [Service] ? |
|
The Service section should already exist, so all you need to do is add TimeoutStartSec |
|
ok think I'm in the wrong file as I only see this sudo vi influxd.service If you modify this, please also make sure to edit init.sh[Unit] [Service] [Install] |
|
after changing sleep to 5 gg@hector:/etc/systemd/system $ sudo service influxdb restart Feb 15 17:11:46 hector influxd-systemd-start.sh[23816]: ts=2023-02-15T15:11:46.603550Z lvl=info msg="Go runtime" log_id=0g1PxPbl000 version=go1.13.8 maxprocs=1 |
|
Did you run the daemon-reload command so the changes take effect? |
yes this is the content of /etc/systemd/system/influxd.service after changing sleep to 5 i ran: sudo service influxdb restart and in the output it shows sleep is 5 so it should have taken affect? |
|
I asked about whether you issued the daemon-reload command. Also, how long have you given influxdb to start? Your log indicates it has only been attempting to start for less than a minute. |
|
can you give me the daemon-reload commnd please? gets to about 12 attempts and then says this gg@hector:/etc/systemd/system $ sudo service influxdb status Feb 15 19:33:45 hector influxd-systemd-start.sh[13641]: InfluxDB API unavailable after 3 attempts... Feb 15 19:35:03 hector systemd[1]: Starting InfluxDB is an open-source, distributed, time series database... |
|
See #1275 (comment) |
|
done, still the same gg@hector:/etc/systemd/system $ sudo service influxdb status Feb 15 19:57:21 hector influxd-systemd-start.sh[23064]: InfluxDB API unavailable after 6 attempts... Feb 15 19:58:22 hector systemd[1]: Starting InfluxDB is an open-source, distributed, time series database... |
|
In all the service files you pasted, I don't see the TimeoutStartSec added. |
|
So, I had the same conclusion that this has to do with influxdb and on searching around, last night, I found that commenting out the the line |
|
added TimeoutStartSec, reloaded daemon, influxdb is now running but unable to access UI. |
kizniche
changed the title
|
This issue has been mentioned on Radical DIY Forum. There might be relevant details there: https://forum.radicaldiy.com/t/error-mycodo-influx-unknown-influxdb-version/1773/5 |
this threat will refer to this one, recursive |
|
still not solved: |
So I have created a brand new deployment using the fresh SD card and pulled the install using the curl script/command. The installation goes through fine except at the end where it is trying to restart the daemon! It gets stuck there. This is on Raspberry Pi Zero. Now I take the same SD card over to a Raspberry Pi 4, remove my Mycodo folder and do another fresh install. Everything works fine as it should! Thanks. Next I take the SD card and pop it into Raspberry Pi Zero and I see that the daemon does not start. I look at the logs and see a message that something has terminated the daemon. I try this multiple times and try to start the daemon without much luck but then I run daemon in the debug mode on the Raspberry Pi Zero and again everything is fine. Not sure what his happening. Likely some timing issue with the slower processor. Any advice on how to fix this?
The text was updated successfully, but these errors were encountered: