GameCreate.com

joss · Posted: Tue May 13, 2008 12:30 am Post subject: Mumble monitoring

The mumble server appears to be launched several time with this message in the Server Failures panel :

Fail Process failure (Server crashed?) 05/12/2008 16:12:13
Start GameCreate attempted to start Mumble Server. 05/12/2008 16:11:59
Stop GameCreate stopped Mumble Server. 05/12/2008 16:11:55
Fail Process failure (Server crashed?) 05/12/2008 16:11:55
Start GameCreate attempted to start Mumble Server. 05/12/2008 16:11:30
Stop GameCreate stopped Mumble Server. 05/12/2008 16:11:11

It's probably a monitoring failure becase the server is up and running.

Anyone see what's happening ?

How can I see the verbose log off gamecreate to check what's goning on ?

bye

Edit : here's my gamecreate.log :
Mon May 12 17:53:07 2008: ** Fetch system performance data **
Mon May 12 17:53:07 2008: Check failed on process 17916 (ID: 9407898)
Mon May 12 17:53:10 2008: ** Stop GameCreate Booking: ID 9407898 **
Mon May 12 17:53:10 2008: PID: 17916 does not exist
Mon May 12 17:53:10 2008: Received PING request
Mon May 12 17:53:13 2008: ** Got file, name: /home/urtserver/gamecreate/mumble/port64738.ini, size: 2599 **
Mon May 12 17:53:13 2008: ** Start GameCreate Booking: ID 9407898 **
Mon May 12 17:53:13 2008: Launching process: /home/urtserver/gamecreate/mumble/murmur.x86 -ini port64738.ini from directory /home/urtserver/gamecreate/mumble
Mon May 12 17:53:13 2008: Set process affinity mask to -1
Mon May 12 17:53:16 2008: Process 17981 was confirmed by master
Mon May 12 17:53:31 2008: ** Check Booking Performance: ID 9407898 **
Mon May 12 17:53:40 2008: Received PING request
Mon May 12 17:53:43 2008: Check failed on process 17981 (ID: 9407898)

adbot · Posted: Thu Mar 31, 2011 3:57 am

Steve · Mammoth

Try killing the process manually and starting the server again with GameCreate.

joss · Posted: Wed May 14, 2008 6:20 am Post subject:

did it same problem

Gamecreate doesn't detect it as started

Got this bug on two different machine with debian etch

bye

Steve · Mammoth

You could try running the option from the command line

-pid port%server:port%.pid

and see how that goes

joss · Posted: Sat May 17, 2008 5:12 am Post subject:

got :
~/gamecreate/mumble$ ./murmur.x86 -ini port64738.ini -pid port64738.pid
Unknown argument -pid

Steve · Mammoth

I'm still looking into this and hope to have a solution for you soon.

NssB · Posted: Thu Jul 17, 2008 6:38 pm Post subject:

Are there any further updates on this.

I have exactly the same problem on our Ubuntu Hardy build.

Regards
NssB

Deep Blue · Posted: Thu Jul 17, 2008 8:19 pm Post subject:

Hi there

I am also very interested in this as the current setup provided by GC works, but continues to spawn processes!

Please can you advise as to when this will be fixed?

Many Thanks!

Deep Blue · Posted: Mon Oct 27, 2008 11:19 pm Post subject:

Bump - Has this been resolved yet?

Steve · Mammoth

Sorry this hasn't been resolved yet.

Unfortunately I haven't been able to figure it out myself, so will see if I can get one of the devs to have a closer look for a solution.

Deep Blue · Posted: Wed Oct 29, 2008 7:54 pm Post subject:

Cheers Steve, your help is greatly appreciated Smile

RS.Pat · Posted: Mon Nov 23, 2009 7:51 pm Post subject:

I may have a problem about Mumble / Murmur too.
I want to define a SuperUser password, and mumble requires it to be done in the command line, e.g. "./murmur.x86 -ini inifile.ini -supw superuserpass"
Only problem is, this command dosent seem to start the server, it just defines the superUser password in the database. So you would have to launch the server AGAIN to make it start.
Is there any way to edit the GameCreate Command line for mumble to define the SuperUser Password AND launch the server ?

Blajsero · Posted: Thu Dec 23, 2010 6:36 am Post subject:

is there any solution (after 2 years...) for this problem?

LukLuk · Posted: Tue Dec 28, 2010 9:58 am Post subject:

Same problem here......

Blajsero · Posted: Sun Jan 02, 2011 1:15 am Post subject:

There is partial solution to run mumble in screen without minor problems. The thing is to run mumble server in verbose mode eg. with "-fg" option.

I wonder why the default command line for mumble doesn`t look like this: