1/19/2024 0 Comments Cant see mumble chatuiGid & egid = Meta::mp.This is a plugin that contains a mumble client, using the MumbleSharp library. QFatal( "Failed to switch to uid %d ", Meta::mp. QFatal( "Failed to switch to gid %d ", Meta::mp. "special privileges to set itself up on these systems, so this behavior is highly discouraged. QCritical( "WARNING: You are launching murmurd as root on Mac OS X or Darwin. If nothing else, I would close this issue after 24 Hour But if you need a test example, I could sent you all the files that included in building the image for debugging. Finally, thanks for answering me this fast and providing such a great open-source software, and sorry for my lack of Cknowledge and could not be able to doing that much help. After I comment the uname argument, everything goes well and no issue came out, DB, SSL, Connect and all other stuff I specified in the config file are correct. But the result is that mumble-server could not be able to read/write db file(May be a premission issue). At the Dockerfile I'm using USER mumble-server, so the container won't start with user root, And uname should be ignored(Maybe it's ignored, just something else goes wrong). IMO, I don't think -fg sovled the problem. Leave host config to empty, so that mumble-server could bind to 0.0.0.0:64738, then it will work.īut here are some question i couldn't figure out:ġ.How mumble-server knows it's host machine's public ip even if it's in a container and allocated a ip only available inside the docker(172.0.0.X)? Is it request some api to get a real public ip?Ģ.Is this host argument issue a bug or intended?ģ.It seems that mumble-server didn't respect the uname's comment If Murmur is started as root, which user should it switch to? This option is ignored if Murmur isn't started with root privileges.But another problem came out: mumble-server could not bind the correct host(I've tested, for example, specify host to, mumble-server will still bind to self public ip, tested on my cloud-server and local machine, both bind to self ip), So step 4 is the solution(I inspect the image that pull from official docker hub and exec into it, then I check the config file and log, finally I found the solution) Removing while true option in the shell scriptĪfter doing these 3 steps, I successfully pass the open and load db file stage.QFatal("ServerDB: Database is not writable") ĭb->setConnectOptions(Meta::mp.qsDBOpts) Īnd in this block of I've solved this problem. QWarning("ServerDB: Opened SQLite database %s", qPrintable(fi.absoluteFilePath())) rw- 1 mumble-server mumble-server 1704 Apr 8 09:19 privkey.pemĭrwxr-xr-x 1 mumble-server mumble-server 4096 Apr 8 09:21 mumble-server Mumble versionĭb->setDatabaseName(Meta::mp.qsDatabase) įor (i = 0 (i setDatabaseName(f.fileName()) rwxr-xr-x 1 mumble-server mumble-server 135 Apr 8 09:07 presist_mumble_server.sh rw-r- 1 mumble-server mumble-server 110592 Apr 8 09:21 mumble-server.sqlite rw-rw- 1 mumble-server mumble-server 2 Apr 8 09:21 mumble-server.pid rw-rw- 1 mumble-server mumble-server 849 Apr 8 09:21 mumble-server.log rwxrwxr-x 1 mumble-server mumble-server 15812 Apr 8 09:13 mumble-server.ini rwxrwxr-x 1 mumble-server mumble-server 2808936 Apr 8 06:39 mumble-server rw- 1 mumble-server mumble-server 5593 Apr 8 09:19 fullchain.pem rw-rw-r- 1 mumble-server mumble-server 231 Apr 8 07:11 build.sh rwxrwxr-x 1 mumble-server mumble-server 744 Apr 8 09:19 Dockerfile Drwxr-xr-x 1 mumble-server mumble-server 4096 Apr 8 09:21.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |