This is a read-only archive of the Mumble forums.

This website archives and makes accessible historical state. It receives no updates or corrections. It is provided only to keep the information accessible as-is, under their old address.

For up-to-date information please refer to the Mumble website and its linked documentation and other resources. For support please refer to one of our other community/support channels.

Jump to content

Murmur segfault


pavelhoral
 Share

Recommended Posts

Hi,

my Murmur installation just crashed leaving this in system logs:

./syslog.1:May 27 05:50:57 serverName kernel: [12766167.330968] murmur.x86[18085]: segfault at 38c ip 80cadd4 sp ffa24e50 error 4 in murmur.x86[8048000+b1b000]
./messages:May 27 05:50:57 serverName kernel: [12766167.330968] murmur.x86[18085]: segfault at 38c ip 80cadd4 sp ffa24e50 error 4 in murmur.x86[8048000+b1b000]
./kern.log:May 27 05:50:57 serverName kernel: [12766167.330968] murmur.x86[18085]: segfault at 38c ip 80cadd4 sp ffa24e50 error 4 in murmur.x86[8048000+b1b000]

 

Version info (from murmur log file):

Murmur 1.2.2 (Compiled Feb  9 2010 17:44:13) running on X11: Linux 2.6.26-bpo.1-xen-amd64

 

Murmur log tail (IP prefixes are replaced with XXX.XXX.XXX):

<W>2010-05-27 04:52:22.561 1 => Starting voice thread
<W>2010-05-27 04:52:22.597 1 => <620:lukkes(12)> Authenticated
<W>2010-05-27 04:59:50.505 1 => <621:(-1)> New connection: XXX.XXX.XXX.75:38349
<W>2010-05-27 04:59:50.656 1 => <621:(-1)> Client version 1.2.0 (Win: 1.2.0)
<W>2010-05-27 04:59:50.679 1 => <621:dedcz(43)> Authenticated
<W>2010-05-27 05:03:55.712 1 => <621:dedcz(43)> Connection closed: The remote host closed the connection [1]
<W>2010-05-27 05:05:43.179 1 => <622:(-1)> New connection: XXX.XXX.XXX.75:38659
<W>2010-05-27 05:05:43.421 1 => <622:(-1)> Client version 1.2.0 (Win: 1.2.0)
<W>2010-05-27 05:05:43.443 1 => <622:dedcz(43)> Authenticated
<W>2010-05-27 05:24:24.516 1 => <620:lukkes(12)> Timeout
<W>2010-05-27 05:24:24.523 1 => <620:lukkes(12)> Connection closed:  [-1]
<W>2010-05-27 05:24:25.815 1 => <623:(-1)> New connection: XXX.XXX.XXX.42:64427
<W>2010-05-27 05:24:25.891 1 => <623:(-1)> Client version 1.2.2 (Win: 1.2.2)
<W>2010-05-27 05:24:25.912 1 => <623:lukkes(12)> Authenticated
<W>2010-05-27 05:42:27.446 1 => <623:lukkes(12)> Connection closed: The remote host closed the connection [1]
<W>2010-05-27 05:42:29.533 1 => <624:(-1)> New connection: XXX.XXX.XXX.42:62521
<W>2010-05-27 05:42:29.601 1 => <624:(-1)> Client version 1.2.2 (Win: 1.2.2)
<W>2010-05-27 05:42:29.627 1 => <624:lukkes(12)> Authenticated
<W>2010-05-27 05:42:39.798 1 => <624:lukkes(12)> Connection closed: The remote host closed the connection [1]
<W>2010-05-27 05:42:58.782 1 => <625:(-1)> New connection: XXX.XXX.XXX.42:62551
<W>2010-05-27 05:42:58.853 1 => <625:(-1)> Client version 1.2.2 (Win: 1.2.2)
<W>2010-05-27 05:42:58.879 1 => <625:lukkes(12)> Authenticated
<W>2010-05-27 05:43:13.560 1 => <622:dedcz(43)> Connection closed: The remote host closed the connection [1]
<W>2010-05-27 05:45:55.245 1 => <626:(-1)> New connection: XXX.XXX.XXX.75:38887
<W>2010-05-27 05:45:55.775 1 => <626:(-1)> Client version 1.2.0 (Win: 1.2.0)
<W>2010-05-27 05:45:55.797 1 => <626:dedcz(43)> Authenticated
<W>2010-05-27 05:48:46.207 1 => <625:lukkes(12)> Connection closed: The remote host closed the connection [1]
<W>2010-05-27 05:48:48.119 1 => <627:(-1)> New connection: XXX.XXX.XXX.42:61013
<W>2010-05-27 05:48:48.189 1 => <627:(-1)> Client version 1.2.2 (Win: 1.2.2)
<W>2010-05-27 05:48:48.225 1 => <627:lukkes(12)> Authenticated
<W>2010-05-27 05:50:21.303 1 => <627:lukkes(12)> Connection closed: The remote host closed the connection [1]
<W>2010-05-27 05:50:23.361 1 => <628:(-1)> New connection: XXX.XXX.XXX.42:63381
<W>2010-05-27 05:50:23.438 1 => <628:(-1)> Client version 1.2.2 (Win: 1.2.2)
<W>2010-05-27 05:50:23.469 1 => <628:lukkes(12)> Authenticated
<W>2010-05-27 05:50:57.617 1 => <626:dedcz(43)> Connection closed: The remote host closed the connection [1]

 

I have Ice allowed for localhost, which is accessed from PHP, but Apache's access.log does not contain anything from the time Murmur crashes. So I assume it must be the Murmur/Mumble communication itself. Maybe attempt to hack? I don't like segfaults. Any suggestions what I should do (I am not advanced in application debugging)?


Pavel

Link to comment
Share on other sites

 Share

×
×
  • Create New...