Hello,
A few days ago I decided to install mumble and create a mumble-server on my computer. So far the network requirements have been met, I have forwarded the necessary ports, etc… etc… The only problem is mumble-server. As soon as I install it, if I restart my computer and run the terminal command
$ murmurd
The servers starts and the database (murmur.sqlite) and log (murmur.log) files are created. As for the ini file, I am able to specify an ini file found in my /home/MYUSERNAME directory, it will use that ini file. The server will be up, and me and my friends will be able to use it. I can kill the server and restart it without a problem.
As soon as my computer is restarted, if i run the murmurd command this appears, whereas before nothing appeared unless i forced the server to stay attached to the terminal.
murmurd
murmurd: failed to open logfile murmur.log: no logging will be done
<W>2011-04-10 10:13:02.696 Initializing settings from /home/rodrigo/.murmurd/murmur.ini (basepath /home/rodrigo/.murmurd)
<W>2011-04-10 10:13:02.696 OpenSSL: OpenSSL 1.0.0c 2 Dec 2010
<W>2011-04-10 10:13:02.700 SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email
<F>2011-04-10 10:13:02.701 ServerDB: Failed initialization: unable to open database file Error opening database
The .log and the .sqlite are still there, untouched, the permissions are exactly the same.
If I specify the ini file that I used before
murmurd -ini mumble-server.ini
<F>2011-04-10 10:14:51.778 Specified ini file mumble-server.ini could not be opened
And of course the server doesn’t start. If I uninstall mumble-server and I reinstall it AND restart, it will be working again but yet again, as soon as I restart my computer after using the server this errors will happen.
I have installed it via zypper, via the download 1-Click-Install on opensuse and I have even installed the unstable version found here:. And so far, the same error happens all the time.
Thanks in advance for your help.
Is it possible that it is set to run as a service and it is already running? ie maybe no need to restart after boot. It sounds to me like an instance is already running and has the files locked.
Thanks for your input.
The problem still exists, after booting the process is not active, the server is down (without launching murmurd) and the error messages are still the same if I try to launch. I am really not sure what the problem is.
Hello, I had the same Problem when I configured a murmur server on my Notebook running openSUSE 13.2. I realised that starting the daemon as superuser makes it work.
I still get the following message:
On 2015-07-12 02:16, ArthurDent wrote:
>
> Hello, I had the same Problem when I configured a murmur server on my
Did you notice that you are hanging at the end of a 4 year old thread?
Anyway, it doesn’t look to me the same problem as the original poster
reported. Not the same error message. I think you should start a new
thread with full details.
Yes I did. But since it is one of the first google hits, when searching for solutions with murmur I decided to add my solution as well. Also because it works with the mumble-server package from the standard repository and doesn’t need the static binary.
My error message without sudo was:
Unable to open locale de-DE in ICU, error code 4
murmurd: failed to open logfile murmur.log: no logging will be done
<W>2015-07-12 15:15:39.199 Initializing settings from /home/saschahome/.murmurd/murmur.ini (basepath /home/saschahome/.murmurd)
<W>2015-07-12 15:15:39.200 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"
<W>2015-07-12 15:15:39.200 OpenSSL: OpenSSL 1.0.1k-fips 8 Jan 2015
<F>2015-07-12 15:15:39.464 ServerDB: Failed initialization: unable to open database file Error opening database
The error message in my previous post is just what was left after executing it with sudo.
Like robin_listas, I do not think it is a good idea to hang your different problem at the end of such an old thread. Almost nobody (except the very attentive ones) will notice such a post. Thus your audience will be minimal.
I would also advice you to start a new thread with a fresh title. That will be the best advertisement you can get here.
On 2015-07-12 15:56, hcvv wrote:
>
> Like robin_listas, I do not think it is a good idea to hang your
> different problem at the end of such an old thread. Almost nobody
> (except the very attentive ones) will notice such a post. Thus your
> audience will be minimal.
>
> I would also advice you to start a new thread with a fresh title. That
> will be the best advertisement you can get here.
Seems he is posting a solution, though, not a problem. Maybe this is the
right place, after all. :-?
On 2015-07-13 09:36, ArthurDent wrote:
>
> Ok, I guess I learned my lesson: Never extend old Threads with
> additional Solutions, because people get heavily confused xD.
> …Sorry…
We got confused, yes
You simply had to clearly say that it is a solution, not a problem
