Can’t Access Server

I ran into an issue today where I can no longer access my server. The docker container had an update so I updated that today. That’s the only thing I know of that changed. I’ve tried restarting the container and the entire unraid server and still not working.

Any thoughts on how to start troubleshooting this?

Are you using @timstephens24's container? I'm not sure what the latest change was there.

First step is probably to look at the container logs to see what's going on.

2 Likes

If it was my container, I do weekly base image updates to Ubuntu 20.04, and that’s all automated. Channels itself wasn’t updated and is controlled by Channels/the user through the GUI (except on first run of the container it pulls the latest release). Mine is working fine, so I’m thinking there might be a variable issue.

3 Likes

yeah it is yours @timstephens24. The container logs only say a ton of lines of "Running Channels DVR"...any thoughts? should I remove it and re-add it?

1 Like

Yeah, when you re-add it can you paste the output of the docker creation window for me please?

Removed and re-installed the image and still the same thing...wierd. I kind of thought that would take care of it.

Pulling image: timstephens24/channels-dvr:latest
IMAGE ID [167227408]: Pulling from timstephens24/channels-dvr. 
IMAGE ID [6a362047f9a6]: Pulling fs layer. Downloading 100% of 30 MB. Download complete. Extracting. Pull complete. 
IMAGE ID [936d61079f9c]: Pulling fs layer. Downloading 100% of 278 B. Verifying Checksum. Download complete. Extracting. Pull complete. 
IMAGE ID [a6243ea6ff4e]: Pulling fs layer. Downloading 100% of 18 MB. Verifying Checksum. Download complete. Extracting. Pull complete. 
IMAGE ID [b23538d40aa4]: Pulling fs layer. Downloading 100% of 6 KB. Download complete. Extracting. Pull complete. 
IMAGE ID [7f7ed2b9ead7]: Pulling fs layer. Downloading 100% of 598 MB. Verifying Checksum. Download complete. Extracting. Pull complete. 
IMAGE ID [f278b6f355fd]: Pulling fs layer. Downloading 100% of 1010 B. Download complete. Extracting. Pull complete. 
Status: Downloaded newer image for timstephens24/channels-dvr:latest

TOTAL DATA PULLED: 646 MB

Command execution
docker run
  -d
  --name='Channels'
  --net='host'
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Haven"
  -e HOST_CONTAINERNAME="Channels"
  -e 'TCP_PORT_8089'='8089'
  -e 'NVIDIA_DRIVER_CAPABILITIES'='compute,utility,video'
  -e 'NVIDIA_VISIBLE_DEVICES'='all'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'TZ'='America/Chicago'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8089]'
  -l net.unraid.docker.icon='https://github.com/timstephens24/docker-templates/raw/master/img/channels-logo.png'
  -v '/mnt/user/media/Videos/':'/shares/DVR':'rw'
  -v '/mnt/user/appdata/channels-dvr':'/channels-dvr':'rw'
  --runtime=nvidia
  --security-opt seccomp=unconfined 'timstephens24/channels-dvr' 
b1537a56b6ef0b89df13643134b61e46ff6f00af4c26db1d8785216778a17548

The command finished successfully!

I noticed there was more in the logs that maybe I missed previously...not sure if any of this is helpful or not..

text  error  warn  system  array  login  

cont-init: info: /etc/cont-init.d/10-adduser exited 0
cont-init: info: running /etc/cont-init.d/40-chown-files
cont-init: info: /etc/cont-init.d/40-chown-files exited 0
cont-init: info: running /etc/cont-init.d/50-gid-video
cont-init: info: /etc/cont-init.d/50-gid-video exited 0
cont-init: info: running /etc/cont-init.d/99-custom-files
cont-init: info: /etc/cont-init.d/99-custom-files exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-mods: starting
s6-rc: info: service init-mods successfully started
s6-rc: info: service init-mods-package-install: starting
s6-rc: info: service init-mods-package-install successfully started
s6-rc: info: service init-mods-end: starting
s6-rc: info: service init-mods-end successfully started
s6-rc: info: service init-services: starting
s6-rc: info: service init-services successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun channels-dvr (no readiness notification)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service 99-ci-service-check: starting
s6-rc: info: service 99-ci-service-check successfully started
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    99
User gid:    100
-------------------------------------

Change in ownership detected, please be patient while we chown existing files
This could take some time
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Running Channels DVR

Can you check the ‘/mnt/user/appdata/channels-dvr’ folder and see if the owner is set to nobody:user for the folder and all the files?

Looks like everything is owned by "nobody". I suppose worse case I could just blow away the config folder and restore from backup.

@timstephens24 just wanted to give you a a heads up i removed the container and appdata folder and reinstalled it and restored from a backup and things are back up now. Not sure why but I’ll take it.

I’m not sure if it would make a difference but during the install I had changed the default container DVR folder from /shares/DVR to /media/Videos/DVR. I run some automations with other software and having consistent path structure in the containers enables atomic movies of files.

The only other minor tweak from the defaults was the timezone. Everything else was left defaults.

1 Like

Thanks, sorry I didn't have any time yesterday. I just made some changes to verify that execute permissions are set on the binary since that might have been the issue you were having.

perfect! I'll keep you posed if I run into any other issues. Thanks for the help

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.