Murmur and MySQL

[faraon3]

I'm reposting this from the old forums, I hope thats alright, but I'm stuck. I have murmur up and running on my server using MySQL database. I SSH into my server to start murmur with the command "nohup ./murmur.x86 &" and all is well, I can connect to my server, and others can too. The problem I'm having is that approximately an hour after I close my SSH session, if a user tries to connect, murmur shuts down with the following entry left in the log file:

2010-02-13 02:38:10.482 Lost connection to SQL Database: Reconnect: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) QMYSQL: Unable to connect

This happens with version 1.2.1 and 1.2.2. Any ideas why this may happen or how to solve it?

Thanks in advance.

[kissaki]

After one hour?

That's strange.

murmur will start as a small daemon anyway, you don't need to add &.

Should be the same for nohup.

Nothing definite here…

[faraon3]

Thanks for the info, I'll play around some more and see if I can't get anymore information.

[kissaki]

Do you start you MySQL Server from your ssh session?

Manually or via /etc/init.d startscript so it runs independently?

Maybe something is closed with the ssh session ending.

Do you disconnect your ssh session or just close your terminal which somehow doesn't do that?

[frymaster127]

it's definately 1 hour after you close your connection, not just 1 hour after murmur starts?

what happens if you run murmur from a screen session?

how busy is your murmur? If busy, i'm wondering if it's related to http://mumble.sourceforge.net/FAQ#I.27m_running_many_virtual_servers_or_have_many_users_connected.2C_and_the_server_becomes_unstable