Skip to content
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

riven 500 | Internal error #35

Closed
vuongtt92 opened this issue Aug 23, 2024 · 5 comments
Closed

riven 500 | Internal error #35

vuongtt92 opened this issue Aug 23, 2024 · 5 comments

Comments

@vuongtt92
Copy link

Describe the bug
hi, I'm trying to setup DMB with riven enabled. The front end has started sucessfully, I've gone through the initial setup but immediately after that it shows "500 | Internal error".
By checking the log, I see that the backend is trying to restart constantly but unsuccessful, the last error in the log is

24-08-22 11:37:52 | :x: ERROR     | program.validate_database - Database connection failed. Is the database running? 
24-08-22 11:46:59 |  CRITICAL  | main.<module> - Server has been stopped

Could anyone help? Thank you
here's my compose, could you pls. take a look to see what's wrong with it?
version: "3.8"

services:
  DMB:
    container_name: DMB
    image: iampuid0/dmb:latest
    stdin_open: true # docker run -i
    tty: true        # docker run -t    
    volumes:
      - /volume2/docker/dmb/config:/config
      ## Location for logs
      - /volume2/docker/dmb/log:/log
      - /volume2/docker/dmb/cache:/cache
      ## Location for Zurg RealDebrid active configuration
      - /volume2/docker/dmb/zurg/rd:/zurg/RD
      ## Location for rclone mount to host
      - /volume2/media/dmb/zurg/mnt:/data:shared 
      ## Location for Riven backend data
      - /volume2/docker/dmb/riven/data:/riven/backend/data
      ## Location for Riven symlinks
      - /volume2/media/dmb/riven/mnt:/mnt
    environment:
      - TZ=Asia/Saigon
      ## Zurg Required Settings
      - ZURG_ENABLED=true      
      - RD_API_KEY=Z7VDOS2OIEKH5DI3XXX
      ## Zurg Optional Settings
      - ZURG_UPDATE=true
        ## Rclone Required Settings
      - RCLONE_MOUNT_NAME=DMB
      ## Rclone Optional Settings - See rclone docs for full list
      - ORIGIN=http://192.168.124.22:3000 # See Riven documentation for more details
      ## Riven Optional Settings
      - RIVEN_ENABLED=true
      - RIVEN_BACKEND_UPDATE=true
      - RIVEN_FRONTEND_UPDATE=true
      ## Special Features
      - DMB_LOG_LEVEL=DEBUG  # Master log level for all program logs in DMB
      - COLOR_LOG_ENABLED=true
    network_mode: bridge  
    ports:
      - "3000:3000"
    devices:
      - /dev/fuse:/dev/fuse:rwm
    cap_add:
      - SYS_ADMIN     
    security_opt:
      - apparmor:unconfined    
      - no-new-privileges

To Reproduce
Access http://192.168.124.22:3000 and see the 500 | Internal error

Expected behavior

To be able to go to settings and setup riven via the Web UI.

Please complete the following information:

  • OS: DSM Synology SA6400
  • Version: 7.1
  • Supporting Applications: Docker (via Portainer)
@I-am-PUID-0
Copy link
Owner

I believe this may be related to Riven removing support for sqlite. As such, this should be resolved w/ Version [4.0.0]. If not, please feel free to reopen the issue.

@vuongtt92
Copy link
Author

hi, I've tried with the version 4.0.0 and the problem persists, please help to reopen the issue

@I-am-PUID-0
Copy link
Owner

Ok. Can you provide the complete debug log - from start to error?

As an aside, did you see the new required mount point?

      ## Location for PostgreSQL database if using Riven
      - /home/username/docker/DMB/PostgreSQL/data:/postgres_data

@I-am-PUID-0 I-am-PUID-0 reopened this Aug 29, 2024
@I-am-PUID-0
Copy link
Owner

I am closing this due to inactivity. Please let me know if the issue persists.

@skeet70
Copy link
Contributor

skeet70 commented Sep 27, 2024

I'm on the latest image today, and I'm getting the same issue. I can see in the logs that postgres is and is still running. I have the postgres mount point config you listed there in my compose. Here's the log (not debug), what should I run for the debug log?
failed-riven-backend.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants