[Support] Crocs - Tube Archivist

[Vyressi]

On 5/14/2023 at 7:27 PM, mathomas3 said:

I was able to apply the update by forcing it... seems like this issue isnt caused by the docker... hoping that others will read this and follow suit... im sure there are others

There was a bug recently in unraid's docker that made containers regularly report "unavailable" and be unable to update automatically, but still able to update manually.  It's been resolved as far as I know in the latest version, but versions that came before that needed a patch plugin from the community store to rpevent this.

 

Regardless when the issue is corrected, you still need to manually update all of the affected containers before automatic can work again.

[rexkwondo]

I'm trying to set up tubearchivist and thought I had everything set correctly, but it won't start. Here's the log, appreciate any guidance on getting this working.

[andreey]

So I setup the containers according to: https://docs.tubearchivist.com/installation/unraid/

The redis and ES container are running fine, no erros in the logs.

 

But everytime I try to start the TA container it just stops itself immediately. I also checked the permissions of the folders:
 

 

The TA config

 

I checked the ES Password multiple times and it's definitely correct. Then I changed the port to 8001 hoping that maybe there's an issue with another service running on 8000 which prevents the container to start. It's hard to identify the problem because I can't inspect the logs.

 

 

 

 

Edited July 20 by andreey

[burgsth]

Tubearchivist is working great so far, except the tubearchivist container does not autostart. TubeArchivist-RedisJSON and TubeArchivist-ES autostart at boottime, but TubeArchivist does not. When starting the container manual everything works great.

I've already tried to set wait time to 30 seconds without any luck.

[CorneliousJD]

54 minutes ago, burgsth said:

Tubearchivist is working great so far, except the tubearchivist container does not autostart. TubeArchivist-RedisJSON and TubeArchivist-ES autostart at boottime, but TubeArchivist does not. When starting the container manual everything works great.

I've already tried to set wait time to 30 seconds without any luck.

 

I see the same thing after my weekly CA appdata backup. 

I've been getting around this by simply using a userscript to run at 7:30AM daily (30 7 * * *)

 

#!/bin/bash
docker start TubeArchivist

 

[kri kri]

Getting this error now on RedisJSON 

 

8:M 25 Aug 2023 13:50:52.551 * <redisgears_2> Failed loading RedisAI API.
8:M 25 Aug 2023 13:50:52.551 * <redisgears_2> RedisGears v2.0.11, sha='0aa55951836750ceabd9733decb200f8a5e7bac3', build_type='release', built_for='Linux-ubuntu22.04.x86_64'.
8:M 25 Aug 2023 13:50:52.558 * <redisgears_2> Registered backend: js.
8:M 25 Aug 2023 13:50:52.559 * Module 'redisgears_2' loaded from /opt/redis-stack/lib/redisgears.so
8:M 25 Aug 2023 13:50:52.559 * Server initialized
8:M 25 Aug 2023 13:50:52.560 * <search> Loading event starts
8:M 25 Aug 2023 13:50:52.560 * <redisgears_2> Got a loading start event, clear the entire functions data.
8:M 25 Aug 2023 13:50:52.560 * Loading RDB produced by version 6.2.13
8:M 25 Aug 2023 13:50:52.560 * RDB age 794829 seconds
8:M 25 Aug 2023 13:50:52.560 * RDB memory usage when created 1.10 Mb
8:M 25 Aug 2023 13:50:52.560 # The RDB file contains AUX module data I can't load: no matching module 'graphdata'

[aglyons]

On 8/25/2023 at 9:51 AM, kri kri said:

Getting this error now on RedisJSON 

 

8:M 25 Aug 2023 13:50:52.551 * <redisgears_2> Failed loading RedisAI API.
8:M 25 Aug 2023 13:50:52.551 * <redisgears_2> RedisGears v2.0.11, sha='0aa55951836750ceabd9733decb200f8a5e7bac3', build_type='release', built_for='Linux-ubuntu22.04.x86_64'.
8:M 25 Aug 2023 13:50:52.558 * <redisgears_2> Registered backend: js.
8:M 25 Aug 2023 13:50:52.559 * Module 'redisgears_2' loaded from /opt/redis-stack/lib/redisgears.so
8:M 25 Aug 2023 13:50:52.559 * Server initialized
8:M 25 Aug 2023 13:50:52.560 * <search> Loading event starts
8:M 25 Aug 2023 13:50:52.560 * <redisgears_2> Got a loading start event, clear the entire functions data.
8:M 25 Aug 2023 13:50:52.560 * Loading RDB produced by version 6.2.13
8:M 25 Aug 2023 13:50:52.560 * RDB age 794829 seconds
8:M 25 Aug 2023 13:50:52.560 * RDB memory usage when created 1.10 Mb
8:M 25 Aug 2023 13:50:52.560 # The RDB file contains AUX module data I can't load: no matching module 'graphdata'

 

me too. And then TA shuts down after a series of connection attempts.

 

I really am not a fan of multiple container operations for a single service to function.

[Dor]

On 8/25/2023 at 4:51 PM, kri kri said:

Getting this error now on RedisJSON 

 

8:M 25 Aug 2023 13:50:52.551 * <redisgears_2> Failed loading RedisAI API.
8:M 25 Aug 2023 13:50:52.551 * <redisgears_2> RedisGears v2.0.11, sha='0aa55951836750ceabd9733decb200f8a5e7bac3', build_type='release', built_for='Linux-ubuntu22.04.x86_64'.
8:M 25 Aug 2023 13:50:52.558 * <redisgears_2> Registered backend: js.
8:M 25 Aug 2023 13:50:52.559 * Module 'redisgears_2' loaded from /opt/redis-stack/lib/redisgears.so
8:M 25 Aug 2023 13:50:52.559 * Server initialized
8:M 25 Aug 2023 13:50:52.560 * <search> Loading event starts
8:M 25 Aug 2023 13:50:52.560 * <redisgears_2> Got a loading start event, clear the entire functions data.
8:M 25 Aug 2023 13:50:52.560 * Loading RDB produced by version 6.2.13
8:M 25 Aug 2023 13:50:52.560 * RDB age 794829 seconds
8:M 25 Aug 2023 13:50:52.560 * RDB memory usage when created 1.10 Mb
8:M 25 Aug 2023 13:50:52.560 # The RDB file contains AUX module data I can't load: no matching module 'graphdata'

 

On 8/28/2023 at 9:51 PM, aglyons said:

 

me too. And then TA shuts down after a series of connection attempts.

 

I really am not a fan of multiple container operations for a single service to function.

 

Change the TubeArchivisit-RedisJSON container to use 

redis/redis-stack-server:6.2.6-v9

 

Annoyingly this is not the first time an update to redis broke TubeArchivist's setup.

[kri kri]

On 8/28/2023 at 1:51 PM, aglyons said:

 

me too. And then TA shuts down after a series of connection attempts.

 

I really am not a fan of multiple container operations for a single service to function.

Same, I think I will go back to youtubdl-material as that one just works. Maybe they can bundle one docker in the future. 

[chuckthetekkie]

I updated TA today and now it stops after about 15-20 seconds of running.

 

The last line of the logs:

{"log":"ValueError: failed to add item to index\n","stream":"stderr","time":"2023-09-03T17:02:40.557601173Z"}

 

ta-logs.logta-log2.log

 

I thought it might have been a permission issue but I ran "chmod -R 777 /mnt/user/appdata/TubeArchivist/es" and it didn't help.

415e2febe313b2ad2ee443a20756c34e8770e944ec2eb1905f639bb16b2337e6-json.log 7e8910deb776d49a63a3926d98c7a21186125f97a3fbb6c45957b1a1e03aa124-json.log 86fc62e2790a3e5d34d841a2ab8c1f47cafbce882fa5579aae93cb00c786104e-json.log

Edited September 3 by chuckthetekkie

[DrBazUK]

Has anyone successfully managed to get the traffic from this container routed through another container (VPN) - I've attempted to use SpaceInvader One's tutorial from 3 years ago to direct all traffic through Binhex's rtorrentvpn container but wasn't able to get it to work.

 

I was able to bash in to the consolse and use "curl ifconfig.io" to confirm the IP address was updated to use the VPN endpoint but I couldn't then access the web ui at all.

 

Didn't matter if I pointed all TA containers to use the proxy or just the TA server and left redis and ES on bridge.

 

Any help very gratefully received.