digitalec / deemon

Monitor specified artists for new releases
GNU General Public License v3.0
174 stars 15 forks source link

Container starts but then stops and disapears #94

Closed jimmisavage closed 1 year ago

jimmisavage commented 1 year ago

Hi, I'm trying to run this in docker on my synology.

docker run --name deemon \ --rm \ -v /volume1/docker/deemon/config:/config \ -v /volume2/music:/downloads \ -v /volume1/docker/deemix/config:/deemix \ ghcr.io/digitalec/deemon:latest \ python3 -m deemon refresh

Here's my log: 2023-07-12 14:17:04 [DEBUG] deemon.cli: deemon 2.19.3 2023-07-12 14:17:04 [DEBUG] deemon.cli: command: "refresh" 2023-07-12 14:17:04 [DEBUG] deemon.cli: Python 3.8.10 2023-07-12 14:17:04 [DEBUG] deemon.cli: Linux-4.4.180+-x86_64-with-glibc2.29 2023-07-12 14:17:04 [DEBUG] deemon.cli: deemon appdata is located at /root/.config/deemon 2023-07-12 14:17:04 [DEBUG] deemon.core.config: Loading configuration, please wait... 2023-07-12 14:17:04 [DEBUG] deemon.core.db: Database version 3.7 2023-07-12 14:17:04 [DEBUG] deemon.core.config: Loaded config for profile 1 (default) 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > check_update: 1 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > debug_mode: False 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > release_channel: stable 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > query_limit: 5 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > smart_search: True 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > rollback_view_limit: 10 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > prompt_duplicates: False 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > prompt_no_matches: True 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > fast_api: True 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > fast_api_threads: 25 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > exclusions/enable_exclusions: True 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > exclusions/patterns: [] 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > exclusions/keywords: [] 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > new_releases/release_max_age: 0 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > new_releases/include_unofficial: False 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > new_releases/include_compilations: False 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > new_releases/include_featured_in: False 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > global/bitrate: 320 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > global/alerts: True 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > global/record_type: album 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > global/download_path: 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > global/email: **** 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > deemix/path: 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > deemix/arl: **** 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > deemix/check_account_status: True 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > deemix/halt_download_on_error: False 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > smtp_settings/server: **** 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > smtp_settings/port: **** 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > smtp_settings/starttls: False 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > smtp_settings/username: **** 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > smtp_settings/password: **** 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > smtp_settings/from_addr: **** 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > plex/base_url: 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > plex/ssl_verify: True 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > plex/token: 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > plex/library: 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > profile_id: 1 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > tid: 0 2023-07-12 14:17:04 [DEBUG] deemon.core.config: > profile_name: default 2023-07-12 14:17:04 [INFO] deemon.cli: :: Starting database refresh 2023-07-12 14:17:04 [DEBUG] deemon.core.api: Using GW API, max_threads set to 25 2023-07-12 14:17:04 [INFO] deemon.core.api: Verifying ARL, please wait... 2023-07-12 14:17:06 [DEBUG] deemon.core.api: Deezer account type is "Hi-Fi" 2023-07-12 14:17:06 [WARNING] deemon.cmd.refresh: No artists found to refresh

After that the container closes and disapears.

Is this normal behaviour or am I doing something wrong?

digitalec commented 1 year ago

That's expected behavior. The command you ran (deemon refresh) should be used in a cronjob to automatically refresh releases.

You'll want to use the monitor command first to setup monitoring of artists first.

Please refer to the documentation on the many different ways you can setup monitoring.

jimmisavage commented 1 year ago

Thanks for the reply. I'm really confused and possibly out of my depth. So I run the following: docker run --name deemon --rm -v /volume1/docker/deemon/config:/config -v /volume2/music:/downloads -v /volume1/docker/deemix/config:/deemix ghcr.io/digitalec/deemon:latest python3 -m deemon monitor

and i get a lovely email sayng its been set up and how to add artists - I was kind of expecting it to automatically monitor artisist i monitor in Deemix but is this not the case?

Then setting up a daily refresh... how do I do that? I'm sorry but i can't figure out what the documentation is telling me. Can this be done in task scheduler on synology?

digitalec commented 1 year ago

So that entire docker run command starts up the container, and the very last line python -m deemon... is running deemon in the container.

If you store your music in Artist/Album hierarchy and want to monitor all of them, you could run python -m deemon monitor --import /downloads. That will attempt to gather a list of artist names and monitor them going forward.

To get release notification emails, make sure you've configured the email server settings in config.json.

Deemon also uses your deemix config, so make sure that's configured as you want it for filename output and such. Deemon gathers a queue of new releases and sends them to deemix.

We have a Discord server running with around 100 people in it if you need help getting your instance setup. I don't use Synology but some in there do. Some also use unraid to run it so it is possible.