Archived

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

yipikaye

segfault libc-2.11.2

Recommended Posts

Hi,

The server seems to have been running fine until i've changed the port from 8080. It works but then after a few hours it crashes with the following errors? Any ideas whats going on?


[24456909.686116] utserver[18735]: segfault at 30 ip b7e742dc sp b6c7af04 error 4 in libc-2.11.2.so[b7e00000+140000]
[24478132.073589] utserver[21979]: segfault at 240 ip b7db52dc sp b6bbbf04 error 4 in libc-2.11.2.so[b7d41000+140000]

Thanks

Share this post


Link to post
Share on other sites

The same with me:

Jan 2 21:29:43 dbn-pc kernel: [306216.954373] utserver[6425]: segfault at 210 ip b766f2dc sp b6475f04 error 4 in libc-2.11.2.so[b75fb000+140000]

Jan 3 08:12:59 dbn-pc kernel: [ 1478.092263] utserver[1113]: segfault at f0 ip b77292dc sp b66abf04 error 4 in libc-2.11.2.so[b76b5000+140000]

Jan 3 10:01:20 dbn-pc kernel: [ 7978.360631] utserver[1568]: segfault at 2d0 ip b75f12dc sp b63f7f04 error 4 in libc-2.11.2.so[b757d000+140000]

root@dbn-pc:~# uname -a

Linux dbn-pc 2.6.32-5-686 #1 SMP Fri Dec 10 16:12:40 UTC 2010 i686 GNU/Linux

Debian Squeeze

Share this post


Link to post
Share on other sites

Same here:

Jan 2 12:24:38 kernel: [1899451.126373] utserver[12790]: segfault at cf0 ip 00e2190c sp b664ef04 error 4 in $

Jan 3 02:45:03 kernel: [1951075.300812] utserver[15852]: segfault at 330 ip 0018490c sp b66b8f04 error 4 in $

Jan 3 06:02:13 kernel: [1962906.116960] utserver[17403]: segfault at f0 ip 00d1e90c sp b679cf04 error 4 in l$

Jan 3 11:32:13 kernel: [1982705.852873] utserver[17993]: segfault at 60 ip 00ad190c sp b66eaf04 error 4 in l$

running:

2.6.31-22-generic #69-Ubuntu SMP Wed Nov 24 08:51:08 UTC 2010 i686 GNU/Linux

Port: 8080 - nothing changed from defaults

Share this post


Link to post
Share on other sites

Yep, I don't think its port related anymore. I changed the port back and have also tried the WebUI v0.380 WIP but its still occuring. I think there must be a bug in the build.

Do you find it occurs when you have disk thrashing?

Debian 5.0.7 - 2.6.26-2-686 #1 SMP Tue Mar 9 17:35:51 UTC 2010 i686 GNU/Linux

Share this post


Link to post
Share on other sites
Yep, I don't think its port related anymore. I changed the port back and have also tried the WebUI v0.380 WIP but its still occuring. I think there must be a bug in the build.

Do you find it occurs when you have disk thrashing?

Debian 5.0.7 - 2.6.26-2-686 #1 SMP Tue Mar 9 17:35:51 UTC 2010 i686 GNU/Linux

I'd like to identify any common configuration parameters, operating system, OS deployment (e.g., native, VM, jail), hardware configuration among you that are seeing this fault.

Every release is run in a high-demand environment for at least 4 days as part of acceptance testing. The tests I'm running for every release are not encountering this problem, so I'd like to know under what conditions this problem occurs so I can reproduce it to fix it, and regression test for it in the future.

Share this post


Link to post
Share on other sites

Hi mcdonald,

Running on Physical Hardware. Only common thing i can see so far is we are all running debian based Linux with the following C Libraries.

dpkg -l |grep "C Library"

ii libc-bin 2.11.2-6 Embedded GNU C Library: Binaries

ii libc-dev-bin 2.11.2-6 Embedded GNU C Library: Development binaries

ii libc6 2.11.2-6 Embedded GNU C Library: Shared libraries

ii libc6-dev 2.11.2-6 Embedded GNU C Library: Development Libraries and Header Files

ii libc6-i686 2.11.2-6 Embedded GNU C Library: Shared libraries [i686 optimized]

ii locales 2.11.2-6 Embedded GNU C Library: National Language (locale) data [suppo

I'm running Debian Lenny with all latest patches.

Share this post


Link to post
Share on other sites
ii libc-bin 2.11.2-6 Embedded GNU C Library: Binaries

ii libc6 2.11.2-6 Embedded GNU C Library: Shared libraries

The stress test machines have 2.12.1-0ubuntu10 version of libraries. The releases are built on Ubuntu, and those releases are unit, system, and stress tested. A Debian build is built on a VM running Debian, and run through unit and short-term system testing, but not long-term stress testing.

Share this post


Link to post
Share on other sites

Hi mcdonald,

Debian Lenny is the current stable release. Would it be too much trouble to get you to run up a lenny VM and test?

Thanks.

** Edit **

I've found that the segfault also occurs when there are no torrents running.

Share this post


Link to post
Share on other sites

Running on Physical Hardware. Only common thing i can see so far is we are all running debian based Linux with the following C Libraries.

dpkg -l |grep "C Library"

ii libc-bin 2.11.2-6 Embedded GNU C Library: Binaries

ii libc-dev-bin 2.11.2-6 Embedded GNU C Library: Development binaries

ii libc6 2.11.2-6 Embedded GNU C Library: Shared libraries

ii libc6-dev 2.11.2-6 Embedded GNU C Library: Development Libraries and Header Files

ii libc6-i686 2.11.2-6 Embedded GNU C Library: Shared libraries [i686 optimized]

ii locales 2.11.2-6 Embedded GNU C Library: National Language (locale) data [suppo

I'm running Debian Lenny with all latest patches.

Hello,

Sorry to throw a spanner in the works but it doesn't look like it's debian related. I'm having the same problem and running Gentoo. I also can't find a pattern with the crashing. It can happen while downloading, seeding only, using the web interface, not using the web interface (at night while asleep), etc. It can also happen any time from 5 minutes to 24 hours after starting.


utserver[3102]: segfault at 780 ip b76f9aa2 sp b667ef18 error 4 in libc-2.12.1.so[b7685000+141000]
utserver[3963]: segfault at 9c0 ip b776aaa2 sp b66eff18 error 4 in libc-2.12.1.so[b76f6000+141000]

System info:

- utserver build 0.3-23418

- glibc-2.12.1

- gcc-4.4.3

- kernel 2.6.36-gentoo-r5 (custom built)

- physical machine (Intel P4)

- torrent data written on USB hard drive (EHCI / ext3)

Anything else I can do to provide more crash info?

Share this post


Link to post
Share on other sites
Debian Lenny is the current stable release. Would it be too much trouble to get you to run up a lenny VM and test?

I've found that the segfault also occurs when there are no torrents running.

I just launched a Debian Lenny VM and am running the server under the debugger. I'm running the server without any torrents since it is simpler and takes less of my time and you said it's possible to see a SEGV with no torrents. I'll let it sit for a day or so to see if this setup shows the problem. If not, I'll try some torrents.

Share this post


Link to post
Share on other sites
Sorry to throw a spanner in the works but it doesn't look like it's debian related...

I likewise will confirm. I have seen the same segfault on an OpenSUSE 11.3 system.

Dec 30 23:43:51 server2 kernel: [12623.132047] utserver[2071]: segfault at 780 ip b76bfb8c sp b663ff04 error 4 in libc-2.11.2.so[b7648000+164000]
Jan 1 07:38:51 server2 kernel: [127523.082659] utserver[9992]: segfault at a50 ip b7679b8c sp b65f9f04 error 4 in libc-2.11.2.so[b7602000+164000]
Jan 1 14:35:40 server2 kernel: [152532.320880] utserver[562]: segfault at 450 ip b768fb8c sp b660ff04 error 4 in libc-2.11.2.so[b7618000+164000]
Jan 1 15:06:01 server2 kernel: [154352.786928] utserver[4552]: segfault at 90 ip b7674b8c sp b65f4f04 error 4 in libc-2.11.2.so[b75fd000+164000]

System info:

- OpenSUSE 11.3 (i386)

- utserver build 0.3-23418

- glibc-2.11.2

- gcc-4.5

- kernel 2.6.34.7-0.7-default

- physical machine (Intel Pentium® 4 CPU 2.40GHz HT, 2GB DDR)

- Storage Drives: LVM SATA (4TB (2x2TB) XFS)

Since I have rebooted the system (kernel update), I have not seen another segfault...

Update: Config file parameters...

cat /etc/opt/utorrent/server/utserver.conf
ut_webui_port: 8080
dir_active: /mnt/data/Torrents/Incomplete/
dir_completed: /mnt/data/Torrents/Complete/
dir_torrent_files: /var/opt/utorrent/server/torrents/
dir_autoload: /mnt/data/autoload/
dir_autoload_delete: true
#token_auth_enable: false

:cool:

Share this post


Link to post
Share on other sites

The daemon stayed up all night (no http access or torrents running). I have just rebooted as suggested above as the server had an uptime of over 300 days :) Ill let you know how it goes.

I have set the configuration via the gui. Is there a way to export it? I tried to cat the settings.dat but its not easily readable

Thanks.

Share this post


Link to post
Share on other sites

Same here

Jan  2 02:30:49 serverubuntu kernel: [210815.982936] utserver[1044]: segfault at ab0 ip 008aa5dc sp b63aef04 error 4 in libc-2.12.1.so[835000+157000]
Jan 2 20:15:21 serverubuntu kernel: [274688.895772] utserver[32302]: segfault at 300 ip 009305dc sp b63edf04 error 4 in libc-2.12.1.so[8bb000+157000]
Jan 4 14:00:38 serverubuntu kernel: [ 790.217833] utserver[1069]: segfault at 90 ip 00c7b5dc sp b6414f04 error 4 in libc-2.12.1.so[c06000+157000]
Jan 4 18:09:11 serverubuntu kernel: [ 3288.766867] utserver[1773]: segfault at 390 ip 001855dc sp b64f5f04 error 4 in libc-2.12.1.so[110000+157000]

It hasn't happened before but I think it may have started happening after I installed an update for libc or something that looked like it. Not sure though.

Ubuntu Linux 10.10

Linux 2.6.35-24-generic-pae on i686

EDIT: is there any way in linux (ubuntu server) to restart µTorrent after it terminates from a segfault, so I won't have to do it myself after hours of 'downtime'?

Share this post


Link to post
Share on other sites
EDIT: is there any way in linux (ubuntu server) to restart µTorrent after it terminates from a segfault, so I won't have to do it myself after hours of 'downtime'?

You might want to try monit http://mmonit.com/monit/

There was a package available for my system, I just needed to configure the control file, tell it to look for includes in /etc/monit.d/ and then added a file for utserver. Here's my current file to monitor the service. It could probably be tweaked, your post reminded me of reading about this program, so this is my first try at using it. Alter paths as you need for your local setup.

cat /etc/monit.d/utserver
check process utserver with pidfile /var/run/utserver/utserver.pid
start program "/etc/init.d/utserver start"
stop program "/etc/init.d/utserver stop"
if failed port 8080 type tcp then restart
if 5 restarts within 5 cycles then timeout

Hope this is useful!

PS: Some useful info here to config the program. http://mmonit.com/monit/documentation/monit.html I found I needed something similar to the example config here to allow access to the monitoring webui: http://mmonit.com/monit/documentation/monit.html#monit_httpd_authentication

:cool:

Share this post


Link to post
Share on other sites

What parameters are you setting in your configuration file?

All my settings were configured via the gui (no utserver.conf). Is there a way to dump them out?

Most options are still default, except I use port 8888. I also haven't messed with the "advanced" settings.

Share this post


Link to post
Share on other sites
EDIT: is there any way in linux (ubuntu server) to restart µTorrent after it terminates from a segfault' date=' so I won't have to do it myself after hours of 'downtime'?[/quote']

You might want to try monit http://mmonit.com/monit/

There was a package available for my system, I just needed to configure the control file, tell it to look for includes in /etc/monit.d/ and then added a file for utserver. Here's my current file to monitor the service. It could probably be tweaked, your post reminded me of reading about this program, so this is my first try at using it. Alter paths as you need for your local setup.

cat /etc/monit.d/utserver
check process utserver with pidfile /var/run/utserver/utserver.pid
start program "/etc/init.d/utserver start"
stop program "/etc/init.d/utserver stop"
if failed port 8080 type tcp then restart
if 5 restarts within 5 cycles then timeout

Hope this is useful!

PS: Some useful info here to config the program. http://mmonit.com/monit/documentation/monit.html I found I needed something similar to the example config here to allow access to the monitoring webui: http://mmonit.com/monit/documentation/monit.html#monit_httpd_authentication

:cool:

Thanks, that at least makes it a lot easier.

Share this post


Link to post
Share on other sites

Hi... I have been having this issue as well, over the past few days. It does NOT just effect Debian based distros, debian based distros are just the most popular :P

Arch Linux here, running on a Xen VPS, fully updated.

[24258.502844] utserver[549]: segfault at 8a0 ip 00000000f762817c sp 00000000f63f6f04 error 4 in libc-2.12.so[f75b2000+145000]

[gary@gary1 ~]$ sudo /etc/rc.d/utorrent-server start
Password:
:: Starting utorrent-server [FAIL]

I am running this on a high speed network with a lot of torrents in it. It crashes after only an hour so of being started, and appears to need a reboot to work correctly after that. Incredibly annoying (but beta software, etc).

Let me know if there is anything else I need to post.

Share this post


Link to post
Share on other sites
Let me know if there is anything else I need to post.

I've been running utserver on a Debian Lenny VM since yesterday and no crashes (no torrents either, but one user reported they saw a crash when no torrents were active).

How about if everyone seeing this problem does the following:

1. set the logmask setting in the configuration files to 0xFFFFFFFF

2. set the -logfile option to generate a log file (specify a location large enough to handle a large log file)

3. run utserver (as daemon or not)

4. wait for a crash

5. look at (near the end of) the log file for anything interesting and post it if so

Maybe we will see some common internal activities occurring immediately before the crash.

I will work on a new release so that utserver incorporates any recent fixes in the main code line.

Share this post


Link to post
Share on other sites

Here is the log output after the crash occurs:

[19:19:17]  70.x.x.x:port(<torrent title>): Connecting: source: I
[19:19:23] [2002:d073:x::x:x]:port [uTP](<torrent title>): Disconnect: Peer error: offline (timed out)
[19:19:26] 208.191.x.x:port(<torrent title>): Connecting: source: I
[19:19:26] 208.191.x.x:port(<torrent title>): Disconnect: Peer error: Connection refused
[19:19:27] 70.133.x.x:port [uTP](<torrent title>): [µTorrent 2.2 (44.8)]: Disconnect: Timed out
[19:19:28] 70.133.x.x:port(<torrent title>): Connecting: source: I
[19:19:35] 208.115.x.x:port(<torrent title>): Connecting: source: TI
[19:19:35] 208.x.x.x:port(<torrent title>): Disconnect: Connection closed
[19:19:37] 70.x.x.x:port(<torrent title>): Disconnect: Peer error: offline (timed out)
[19:19:44] 86.x.x.x:port [uTP](<torrent title>): Connecting: source: TI

uTorrent is still running after this, however I cannot access the web UI. I was hoping it would fully crash so I could grab a core dump, but no such luck.

edit: dmesg output this time is slightly different, but doubtfully related

[69501.304966] possible SYN flooding on port 47712. Sending cookies. (oops)
[69569.598851] utserver[9102]: segfault at c0 ip 00000000f767017c sp 00000000f643ef04 error 4 in libc-2.12.so[f75fa000+145000]
[69648.719290] UDP: bad checksum. From 213.157.xxx.xxx:35841 to 98.129.xxx.xxx:47712 ulen 75

edit 2: after running tail on the logfile, it is still running (actively transferring files). but the WebUI is inaccessible. I don't think this is what normally happens (when I check after the segfault, every other time the process is not running).

Share this post


Link to post
Share on other sites

Hi,

reboot seems to fix it for a while. but then it starts crashing again. I have a basic setup with no conf file at the moment so i cannot set the logmask but i am now recording the log file.

Another quick question, should i manually set the disk cache to 3GB or should i leave the caching to the linux kernel. Currently the system is using about 300MB of memory and has about 3.7GB of cached memory.

Share this post


Link to post
Share on other sites

I am having the exact same issue as these guys. uTorrent randomly segfaults. I thought it was my browser on the page constantly refreshing but even with nothing viewing the http page it still crashes. Sometimes after a day ... sometimes after an hour. It seems the more busy utorrent is the more this issue comes up.

chris@solosoft:~$ dpkg -l |grep "C Library"

ii libc-bin 2.11.2-7 Embedded GNU C Library: Binaries

ii libc-dev-bin 2.11.2-7 Embedded GNU C Library: Development binaries

ii libc6 2.11.2-7 Embedded GNU C Library: Shared libraries

ii libc6-dev 2.11.2-7 Embedded GNU C Library: Development Libraries and Header Files

ii libc6-i686 2.11.2-7 Embedded GNU C Library: Shared libraries [i686 optimized]

ii locales 2.11.2-7 Embedded GNU C Library: National Language (locale) data [support]

chris@solosoft:~$ linuxinfo

Linux solosoft.org 2.6.36-guk #1 SMP Wed Dec 29 21:28:09 EST 2010

Two Intel Pentium III (Katmai) 451MHz processors, 1804.38 total bogomips, 1015M RAM

System library 2.11.2

I never once had any issues with it untill debian did a libc update. Im thinking that the libc is incompatable. Running monit to monitor the service and restart it is definitely a temp fix but sometimes I have some pretty big torrents and @ 450MHz it takes awhile to check them after a hard stop like that.

Hopefully we can get this fixed :) utorrent for linux works excellent on my local network. I would hate to have to figure something else out.

Share this post


Link to post
Share on other sites

Just to add another to the pile. Same occurrence on CentOS 5.5 (i386). C Libraries listed below, which are significantly older than the others above, albeit current for CentOS.

glibc-headers-2.5-49.el5_5.7 Sat 30 Oct 2010 11:34:39 AM PDT

glibc-devel-2.5-49.el5_5.7 Sat 30 Oct 2010 11:34:39 AM PDT

glibc-2.5-49.el5_5.7 Sat 30 Oct 2010 11:34:32 AM PDT

glibc-common-2.5-49.el5_5.7 Sat 30 Oct 2010 11:34:17 AM PDT

I'm currently running strace on the process, will report back when it crashes again.

Share this post


Link to post
Share on other sites

Here's the final output of strace when it crashed. If you need the entire log, or want me to run traces in different ways, let me know. Below was run as daemon only, no other switches.

It ran for 22 minutes and 46 seconds before segfaulting. Freshly rebooted standalone server.

time(NULL)                              = 1294697645
ioctl(8, FIONREAD, [0]) = 0
gettimeofday({1294697645, 280120}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1294697645, 280147773}) = 0
futex(0xb5329c40, FUTEX_WAIT_PRIVATE, 2923, {59, 999972227}) = 0
futex(0xb5329c24, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x81043e8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x81043e8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x81043e8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x81043e8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x81043e8, FUTEX_WAKE_PRIVATE, 1) = 0
time(NULL) = 1294697646
ioctl(8, FIONREAD, [0]) = 0
gettimeofday({1294697646, 280142}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1294697646, 280169388}) = 0
futex(0xb5329c40, FUTEX_WAIT_PRIVATE, 2925, {59, 999972612}) = 0
futex(0xb5329c24, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x81043e8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x81043e8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x81043e8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x81043e8, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x81043e8, FUTEX_WAKE_PRIVATE, 1) = 0
time(NULL) = 1294697647
ioctl(8, FIONREAD, [0]) = 0
gettimeofday({1294697647, 280107}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1294697647, 280134924}) = 0
futex(0xb5329c40, FUTEX_WAIT_PRIVATE, 2927, {59, 999972076} <unfinished ...>
+++ killed by SIGSEGV +++

Share this post


Link to post
Share on other sites