lancachenet / monolithic

A monolithic lancache service capable of caching all CDNs in a single instance
https://hub.docker.com/r/lancachenet/monolithic
Other
725 stars 73 forks source link

(LXC) Stuck at "Starting Supervisord" #165

Closed gpago closed 1 year ago

gpago commented 1 year ago

Describe the issue you are having

I'm running Lancache on an Ubuntu 20.04 LXC, with Proxmox 7.3 being the hypervisor. It's been running fine for the last 1.5-2years, and updating between minor Proxmox versions was never an issue. But ~2weeks ago, I updated a few packages on the host and after restarting, Lancache would just get stuck at "Starting Supervisord". I looked at the processes with strace and I can see the nginx cache loader going through seemingly reading every cached file.

I know this seems more a compatibility issue, but I thought I'd try to see if anyone else has/had this issue. Thank you in advance!

How are you running the container(s)

version: '2'
services:
  dns:
    image: lancachenet/lancache-dns:latest
    env_file: .env
    restart: unless-stopped
    ports:
      - ${DNS_BIND_IP}:53:53/udp
      - ${DNS_BIND_IP}:53:53/tcp
  monolithic:
    image: lancachenet/monolithic:latest
    env_file: .env
    restart: unless-stopped
    ports:
      - 80:80/tcp
      - 443:443/tcp
    volumes:
      - ${CACHE_ROOT}/cache:/data/cache
      - ${CACHE_ROOT}/logs:/data/logs

DNS Configuration

DNS is handled by Adguard Home which uses Lancache as its upstream.

Output of container(s)

...
monolithic_1  | Checking nginx config
monolithic_1  | nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
monolithic_1  | nginx: configuration file /etc/nginx/nginx.conf test is successful
monolithic_1  | Config check successful
monolithic_1  | Starting Supervisord
jakobbouchard commented 1 year ago

I am having the same issue trying to set it up on TrueNAS SCALE using the TrueCharts image.

jakobbouchard commented 1 year ago

Interestingly, it seems to be working on my side now, even with it being "stuck"

gpago commented 1 year ago

After a few more restarts and container re-creations, I have observed the same behavior. Even if it appears stuck, after waiting for a bit, it seems to be working. I'm closing the issue and chucking it up to growing amount of data, use of an HDD, and relatively low specs machine.