Docker image shutting down after a few days about audioserve HOT 11 CLOSED

Are you using provided Dockerfile for alpine linux?
What exact config/ rguments are you using to run program?

To get more detailed logging (debug) you'll need to compile in debug mode (without --release, binary then will be in target/debug) and set environment variable to RUST_LOG=debug (which will log debug from all creates) or just RUST_LOG=audioserve=debug - to log only debug messages from this binary.

You can also try to strip down features you are not using - compile with --no-default-features and then --features you want. This will leave out unwanted code in case it causes problems.

When exactly the termination of container happens?

• when streaming some music?
• when working with files in collections directories (copying new, renaming etc)?
• or when audioserve is unused?

As exist status is 0 I assume it's not segfault or some other OS enforced termination.

from audioserve.

Also looking now at default logging when running in Docker container it was not ideal - although info logging is enabled for release build, it's not enabled by adding appropriate env. variable (I've fixed it in latest master).
So at least I would recommend to have ENV RUST_LOG=audioserve=info in docker file, then you can see if program terminated normally - as this message should be last one:

INFO  audioserve > Server finished

from audioserve.

I run it using this docker-compose configuration:

    audioserve:
      image: izderadicka/audioserve
      container_name: audioserve
      command: ["--allow-symlinks", "/audiobooks"]
      volumes:
        - /home/mange/services/audioserve/config:/home/audioserve/.audioserve
        - /home/mange/services/audioserve/library:/audiobooks
      env_file:
        - /home/mange/services/audioserve/config/secrets.env
      restart: unless-stopped

It happens when the service is not used.

I'll see about recompiling it and trying the debug logs for a bit, but now it's been running without issue for 4 days. I'll recompile it the next time it crashes, just before I also capture the whole output of docker inspect so I had additional clues.

from audioserve.

@Mange Any more crashes? Some logs?

from audioserve.

Seems from docker inspect that the current container was started on the 8th of august, a week after my last update. But since then it's been running (Up 2 weeks).

Log is just full of

 ERROR websock > Upgrade is not to websocket
 ERROR websock > It must be upgrade connection

so I can't give you anything from there.

from audioserve.

Thanks,
the error messages are related to the playback position sharing, which is kind of experimental now (position is sent over websocket as file is playing). If you are not using it you can disable it in client by not specifying group.

from audioserve.

I am actually trying to use it, though. 😄

from audioserve.

@Mange And is it working? Can you open another issue for these error messages? I'm also trying to use it , but getting different messages

ERROR websock                                       > Socket error Ws

I think I know why this message come from - it's when websocket is closed unexpentantly (mobile device lost connection, rev. proxy closes connection). Here it looks like client is using incorrect websocket request - or maybe it's proxy (normally you need to do some setup on rev. proxy for websockets to work).

from audioserve.

Any update? Still problem with docker image stability?

from audioserve.

from audioserve.

@Mange Thanks

from audioserve.