Jump to content

Segfault in utserver for linux.


shredluc

Recommended Posts

Hey all,

Note that i have renamed the utserver executable to utorrent.

OS information:

$ uname -a
Linux AlphaProxima 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24 00:25:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/redhat-release
CentOS release 6.3 (Final)

utorrent version information:


$./utorrent -usage
./utorrent: /lib64/libcrypto.so.0.9.8: no version information available (required by ./utorrent)
./utorrent: /lib64/libssl.so.0.9.8: no version information available (required by ./utorrent)
server started - using locale en_US.UTF-8
300B (27079) 2012-04-17 19:51:48 -0700
Usage: utserver -settingspath -logfile -configfile -pidfile -daemon -usage
settingspath - location of settings directory
logfile - location and name of log file
configfile - location and name of configuration file
pidfile - location and name of file to contain process ID
daemon - run process as a daemon
usage - print this message and exit
server exited with 0

Here is the segfault as it shows up in messages:


Sep 20 08:32:53 AlphaProxima kernel: utorrent[10593]: segfault at 7f7e25ca6dc1 ip 00000000004429df sp 00007f7e64a74b30 error 4 in utorrent[400000+f9000]
Sep 20 08:37:13 AlphaProxima kernel: utorrent[10673]: segfault at 7fb185ca6dc1 ip 00000000004429df sp 00007fb1c2579b30 error 4 in utorrent[400000+f9000]
Sep 20 08:38:50 AlphaProxima kernel: utorrent[10722]: segfault at 7fdebdca6dc1 ip 00000000004429df sp 00007fdefcbdbb30 error 4 in utorrent[400000+f9000]
Sep 20 08:40:32 AlphaProxima kernel: utorrent[10758]: segfault at 7f2d55ca6dc1 ip 00000000004429df sp 00007f2d92e18b30 error 4 in utorrent[400000+f9000]
Sep 20 12:08:53 AlphaProxima kernel: utorrent[10782]: segfault at 7fd379cab9a1 ip 00000000004429df sp 00007fd3bdaf4b30 error 4 in utorrent[400000+f9000]
Sep 20 12:24:47 AlphaProxima kernel: utorrent[12524]: segfault at 7fdc79d56ac1 ip 00000000004429df sp 00007fdcb2340b30 error 4 in utorrent[400000+f9000]
Sep 20 12:24:58 AlphaProxima kernel: utorrent[12535]: segfault at 7fa2973c5ac1 ip 00000000004429df sp 00007fa2cf56bb30 error 4 in utorrent[400000+f9000]

The segfault seems to be fixed temporarily by deleting the resume.dat and resume.date.old files. It runs for a while , usually no less than 10 minutes to a couple of hours and then crashes. IT will then proceed to segfault within seconds on each restart until the resume files are removed. It then reverts to working for longer. I'm stumped. Anyone see anything like this before?

Thanks!

Link to comment
Share on other sites

  • 1 month later...

After about a month of using utserver 27079 I'm experiencing these segfaults too. Googled for a bit and found that this bug was present on previous versions as well.

Ubuntu 12.04

Linux rin 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

server started - using locale en_US.UTF-8
300B (27079) 2012-04-17 19:51:48 -0700

Nov  8 18:01:34 rin kernel: [81983.621047] utserver[10081]: segfault at 613130 ip 0007fd617e0b530 sp 00007fff83682e08 error 4 in libc-2.15.so[7fd617d69000+1b5000]
Nov 8 18:02:58 rin kernel: [82067.855004] utserver[21320]: segfault at 9c012f60 ip 00007f7ca8094530 sp 00007fffa4ea7668 error 4 in libc-2.15.so[7f7ca7ff2000+1b5000]
Nov 8 18:05:36 rin kernel: [82225.359267] utserver[21374]: segfault at ac0151b0 ip 00007f10ba236530 sp 00007fffef114cf8 error 4 in libc-2.15.so[7f10ba194000+1b5000]
Nov 8 18:06:29 rin kernel: [82278.185016] utserver[21398]: segfault at b4059d30 ip 00007febc159f530 sp 00007fffe1e4a918 error 4 in libc-2.15.so[7febc14fd000+1b5000]

In one of the crashes I saw these printed to the console by utserver:

File not found during integrity check: .//webcache.dat
File not found during integrity check: .//webcache.dat.new
File not found during integrity check: .//webcache.dat.old

Hope this canbe fixed soon.

Link to comment
Share on other sites

Well it was happening when i would load a particual torrent file. I figure it was some kind of parsing error in utorrent that was causing the crash. As you can see, never got a response from anyone. My solution which is no solution at all, is any time it crashes like this, i try a different torrent. Doesn't happen very often, maybe 1 out of 100 torrents. Good Luck!

Link to comment
Share on other sites

Hey,

Thanks for pointing that out, it may have something to do with the crashes in my case as well, though I'm not sure yet: tried manually re-adding the torrents that were currently running but there was no crash this time.

Anyway, I guess I will be switching to deluge.

Greetings.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...