Redeployed with KEEP_WATCHING blank and testing...
The contents are different, which is why I thought it might be an issue
If it still fails maybe @bnhf what do you think about opening a WSL terminal going cd /mnt/n/olivetin/ah4c/scripts/dtvospreydeeplinks and making sure they didn't get flipped to not being executable by Windows or some other weird permission.
Same thing happened here
@mackid1993 I'm thinking he should try ADBTuner. Can you give him a few basics on using that project with Osprey/Gemini boxes?
late to the party, but do you have another ah4c container running?
I agree, or pick up a Raspberry Pi. This will be easy in straight docker compose on a Pi. WSL is breaking this I think.
I don't have another instance running yet. I have an additional source or two that I'd like to setup after IU get the main one working correctly.
WEIRD. I am out of ideas.
I know, it is weird -- which is why I think trying ADBTuner might be a reasonable alternative.
2 Likes
ok. don't think that's the issue, but for my 'main' one and to help make sure it just worked, I left mine default ( delete line- AH4C_CONTAINER=1 ) I used the numbered ones for my playing around.
what is your olivetin compose? did you use an ezstart?
I did use the one click compose. I went ahead and updated to remove the number for the container and created a brand new stack.
I'd like to see the olivetin env
The issue did follow to a new ah4c with no container number.
For olivetin itself, here is the environment values:
TAG=latest
DOMAIN=localdomain
HOST_PORT=1337
CHANNELS_DVR_HOST=192.168.8.132
CHANNELS_DVR_PORT=8089
CHANNELS_CLIENTS=
ALERT_SMTP_SERVER=
ALERT_EMAIL_FROM=
ALERT_EMAIL_PASS=
ALERT_EMAIL_TO=
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
TZ=US/Eastern
HOST_DIR=N:\olivetin
DVR_SHARE=/mnt/n/channelsdvr
LOGS_SHARE=/mnt/c/programdata/channelsdvr
TUBEARCHIVIST_SHARE=/mnt/n/channelsdvr
DVR2_SHARE=
LOGS2_SHARE=
TUBEARCHIVIST2_SHARE=
DVR3_SHARE=
LOGS3_SHARE=
TUBEARCHIVIST3_SHARE=
HOST_SFS_PORT=8080
FOLDER=/web
cat: /config/olivetin.token: No such file or directory=
PORTAINER_TOKEN=ptr_TR+WGTaxceJ1+iznKuRAJjQft1Gazl76qf2YchOKeV0=
PORTAINER_HOST=192.168.8.132
PORTAINER_PORT=9443
PORTAINER_ENV=2
PERSISTENT_LOGS=false
I'd suggest you give ADBTuner a try. Whatever is going on with ah4c is not jumping out for any of us. Recent versions of ADBTuner work with Ospreys, so it should do the same job for you.
There's an OliveTin Action to populate ADBTuner with all of your subscribed DTV channels, so the setup should be pretty straightforward. There's a Project One-Click Action to spin it up as well.
Be sure to stop the ah4c stack before proceeding -- if you decide to try ADBTuner. You can't run them at the same time with the same streaming devices and encoder.
not sure how that got in there, should be
HOST_SFS_PORT=8080
FOLDER=/web
PORTAINER_TOKEN=
also
HOST_DIR=N:\olivetin
needs to be
HOST_DIR=/mnt/n/olivetin
or I recommend (md n:\data)
HOST_DIR=/mnt/n/data
also belive it's recommended to use tz format
TZ=america/new_york
Trying this one now - I'll have to play around with it a little bit. It's all setup but not changing channels, instead it pauses whatever is on the device. I'll go through my settings and if I need help use the correct forum here.
Thanks for all the efforts in trying to get ah4c to work.
1 Like
agree on giving it a try, but likely would encounter issues regardless until we get windows and linux playing nice.
FYI there are lots of directions on the web saying C:/directory, and that may work if other things get setup differently. but my experience as documented here says always go for /mnt/C/directory when using WSL(2) and Docker Desktop
forgot to mention that I'm not sure why it matters where the olivetin HOST_DIR is in relation to other containers. other than the adb keys persistance, but again, ah4c handes that, not olivetin. but somehow it seems too. (still nailing that part down exactly)
it may be one-click related, or another backend engine shared by both containers.