-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] With today update from 21.06, it dont start anymore #3985
Comments
Could you please provide a bit more logs (use |
@SamantazFox Sure. Sry for the inconvience. @unixfox hmac key is set already since about 2-3 weeks. after setting it, the warning gone away about to set hmac key and that it is mandotory. |
What command are you using for compiling invidious? |
Im using https://github.com/tmiland/invidious-updater/blob/master/invidious_update.sh linked from the invidious documentation. |
I'd recommend to check with tmiland on his repository. Seems like your database is misconfigured. Related: #2938 Feel free to reopen if you think this is not caused by the reason above! |
Thanks. Have done what tmiland suggested. tmiland/invidious-updater#106 But that dont seem to be the problem. I rolled back to last working state (21.06), and figuring tomorrow out how to migrate to the docker version (easiest way would be to export my subscriptions and import it i guess). |
I just upgraded and am experiencing the same issue. Running on arch linux with invidious-updater.sh as well. tried uninstalling and reinstalling, tried the docker version, tried the steps given by tmiland, nothing working. |
Docker version 100% work. We have tests that are ran for every code change. tmiland's invidious updater is not officially supported. |
Hi, I had tested the docker version from within the tmiland invidious updater, that's the one that didn't work for me.
|
Please start from scratch and follow https://docs.invidious.io/installation/#docker Don't frankenstein two projects by using both tmiland invidious updater and our own docker-compose project. I won't give any further reply, if you follow our documentation from scratch everything will work fine. |
Hi, I did start from scratch. I uninstalled the tmiland version and deleted the directory, then I tried as per https://docs.invidious.io/installation/#docker |
It's causing too many issues and wasting our time. iv-org/invidious#3985 And more issues if you search in the issues tracker
I purged the /var/lib/docker directory to get rid of any left over tmiland files and tried again with the official docker and it worked. Apologies for any trouble I caused with my numerous posts |
Hmm. For some Reason the Docker Method dont work for me. => [invidious builder 2/14] RUN apk add --no-cache sqlite-static yaml-static On this Step, it runs infinity. But i can download that file with wget. So, no Networkissue. |
You don't have to compile it yourself, you can use the official image from the documentation. |
im following the documentation. and it hangs now on docker compose pull -d (1100 secounds in) |
Make sure to correctly follow the section You are doing something wrong, it works fine when you follow correctly the documentation. |
I have done exactly what is written there: https://docs.invidious.io/installation/#docker-compose-method-production bash history:1925 git clone https://github.com/iv-org/invidious.git Edit: I deleted the invidious folder. and redid these commands. its now seem to go further. Edit2: Ok. Something is wrong, or i dont understand the documentation. the invidious container is stuck in a loop (restarting status) Edit3: With exact the same Errors, like it was in the standalone (without docker) installation: invidious-invidious-1 | Caused by: Cannot establish connection (PQ::ConnectionError) (it is a total fresh install of debian 12) |
Reinstalled my VM with Debian 12. Followed the Documentation (Docker Production install). Get the same error like posted yesterday (and OP where it was installed directly). |
Yeah, the implementation is done due to the official version not working properly at the time it was implemented. |
Describe the bug
Updated today from 21.06.23. Now it dont start anymore. This is the Error:
● invidious.service - Invidious (An alternative YouTube front-end)
Loaded: loaded (/lib/systemd/system/invidious.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2023-07-14 15:45:57 CEST; 1s ago
Process: 4821 ExecStart=/home/invidious/invidious/invidious -o invidious.log (code=exited, status=1/FAILURE)
Main PID: 4821 (code=exited, status=1/FAILURE)
CPU: 453ms
Jul 14 15:45:58 invidious invidious[4821]: from lib/db/src/db/pool.cr:214:27 in 'build_resource'
Jul 14 15:45:58 invidious invidious[4821]: from /usr/share/crystal/src/int.cr:525:11 in 'build_database'
Jul 14 15:45:58 invidious invidious[4821]: from src/invidious.cr:63:15 in '__crystal_main'
Jul 14 15:45:58 invidious invidious[4821]: from /usr/share/crystal/src/crystal/main.cr:115:5 in 'main'
Jul 14 15:45:58 invidious invidious[4821]: from /lib/x86_64-linux-gnu/libc.so.6 in '??'
Jul 14 15:45:58 invidious invidious[4821]: from /lib/x86_64-linux-gnu/libc.so.6 in '__libc_start_main'
Jul 14 15:45:58 invidious invidious[4821]: from /home/invidious/invidious/invidious in '_start'
Jul 14 15:45:58 invidious invidious[4821]: from ???
Jul 14 15:45:57 invidious systemd[1]: invidious.service: Main process exited, code=exited, status=1/FAILURE
Jul 14 15:45:57 invidious systemd[1]: invidious.service: Failed with result 'exit-code'.
I read something about crystal1.8 in the latest commits. so i tried crystal1.8 (deleted .cache everytime). but after a rebuild, the same error shows up.
Now i have again crystal1.4. Deleted .cache too and rebuilded. Still cant start invidious.
Thanks for help!
The text was updated successfully, but these errors were encountered: