Murmur doesn't start

[sebastiendarocha]

After the first launch who creates the mumble-server.ini. The server didn't, the logs gave :

mumble_1 | Starting mumble-server service mumble_1 | murmurd: failed to open logfile /data/mumble-server.log: no logging will be done mumble_1 | <W>2018-05-17 10:10:36.928 Initializing settings from /data/mumble-server.ini (basepath /data) mumble_1 | <W>2018-05-17 10:10:36.929 Meta: TLS cipher preference is "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:AES256-SHA:AES128-SHA" mumble_1 | <W>2018-05-17 10:10:36.929 OpenSSL: OpenSSL 1.0.2g-fips 1 Mar 2016 mumble_1 | <F>2018-05-17 10:10:36.976 ServerDB: Failed initialization: unable to open database file Error opening database

It doesn't have rights to modify the /data/ folder, I had to do a chmod 108:111 /path/to/config/mumble-server to make it work (108 and 111 are the uid/gid of mumble-server on the docker image)

After a restart of the container, murmur worked fine

[Tofdu31]

Hi, I have a same problem. But i don't undestand your solution

Would you have a more explicit solution

Thank

[sebastiendarocha]

Hi, If you mounted the configuration volume on /path/to/config/mumble-server on your host (as it's written on the doc, but you have probably chosen another mount point ;-) )

On your host, issue this command to change the user of your mount point:

chmod 108:111 /path/to/config/mumble-server

Then restart your container, you should boot.

[mobiuscog]

@sebastiendarocha I think you meant chown rather than chmod. This is the correct solution though, and fixes the problem 👍