[Mldonkey-bugs] [bugs #9138] /kernel: pid xxxx (mlnet-real), uid 1002: exited on signal xx (core dumped)

[spiralvoice]

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a multi-networks file-sharing client.

/**************************************************************************/
[bugs #9138] Latest Modifications:

Changes by: 
                spiralvoice <address@hidden>
'Date: 
                Fre 01.10.2004 at 13:09 (Europe/Berlin)

------------------ Additional Follow-up Comments ----------------------------
Use ulimit






/**************************************************************************/
[bugs #9138] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=9138>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: 0
On: Fre 28.05.2004 at 08:58

Category:  Core
Severity:  5 - Average
Item Group:  Program malfunction
Resolution:  None
Privacy:  Public
Assigned to:  None
Status:  Open
Release:  2-5-21
Release:  2.5.-21
Platform Version:  FreeBSD
Binaries Origin:  CVS / Self compiled
CPU type:  Intel x86


Summary:  /kernel: pid xxxx (mlnet-real), uid 1002: exited on signal xx (core 
dumped)

Original Submission:  From time to time I get one of the two messages after 
mlnet-real died:

/kernel: pid xxxx (mlnet-real), uid 1002: exited on signal 10 (core dumped)

/kernel: pid xxxx (mlnet-real), uid 1002: exited on signal 11 (core dumped)

You will find FreeBSD version and memory information in the attached file. 
MLDonkey was built using the ports system.

Follow-up Comments
------------------


-------------------------------------------------------
Date: Fre 01.10.2004 at 13:09       By: spiralvoice <spiralvoice>
Use ulimit

-------------------------------------------------------
Date: Mit 29.09.2004 at 11:42       By: Kay <raXion>
I have enabled this networks: Overnet, Donkey, Bittorrent, Fastrack and FileTP. 
But I got 5 core-dumps during the last 2 days, all after 3 to 4 hours after 
starting the mlnet-core.

susi# grep mlnet /var/log/messages
Sep 28 20:50:50 susi kernel: pid 84537 (mlnet-real), uid 1005: exited on signal 
11 (core dumped)
Sep 28 23:53:42 susi kernel: pid 86825 (mlnet-real), uid 1005: exited on signal 
11 (core dumped)
Sep 29 03:09:14 susi kernel: pid 88172 (mlnet-real), uid 1005: exited on signal 
11 (core dumped)
Sep 29 07:43:14 susi kernel: pid 90167 (mlnet-real), uid 1005: exited on signal 
11 (core dumped)
Sep 29 11:47:49 susi kernel: pid 92414 (mlnet-real), uid 1005: exited on signal 
11 (core dumped)
susi#

How do I check those RAM-limits?

-------------------------------------------------------
Date: Don 19.08.2004 at 12:56       By: spiralvoice <spiralvoice>
Please pay also attention to the RAM limits for the MLDonkey process imposed by 
ulimit.

-------------------------------------------------------
Date: Don 19.08.2004 at 12:03       By: Kay <raXion>
Today I updated to 2.5.28.

-------------------------------------------------------
Date: Die 17.08.2004 at 11:15       By: Kay <raXion>
I changed ulimit settings according to 
http://support.zeus.com/faq/zlb/v1/entries/os/freebsd.html . I have 
autoconf-2.59 installed ... I also disabled both Gnutella-Networks.

-------------------------------------------------------
Date: Son 15.08.2004 at 15:51       By: spiralvoice <spiralvoice>
Please check ulimit settings for mlnet, they tend to be pretty tight on 
FreeBSD, also install autoconf-2.59 to compile the core.

-------------------------------------------------------
Date: Mit 11.08.2004 at 16:43       By: Kay <raXion>
I would like to, but this depends on bugs #9795 for me.

-------------------------------------------------------
Date: Die 10.08.2004 at 11:04       By: spiralvoice <spiralvoice>
Please check with current CVS versions, also please check whether there is a 
small ulimit for MLDonkey regarding memory.

-------------------------------------------------------
Date: Die 27.07.2004 at 13:00       By: 0 <None>
I have 1536 MB of RAM installed and there is always free memory available.

I also have all networks enabled, including Gnutella. I will disable Gnutella 
and check if got a core dump again.

-------------------------------------------------------
Date: Don 22.07.2004 at 23:25       By: spiralvoice <spiralvoice>
Please check whether MLDonkey uses too much RAM and dies when no free RAM is 
available anymore. What networks are enabled and used? Some of them have known 
memory leaks (Gnutella for example), take a look at the other bug reports.

-------------------------------------------------------
Date: Don 01.07.2004 at 12:16       By: 0 <None>
Today I ran Memtest v3.0 from Boot-CD and the standard test run (took about 90 
minutes) didn't report any errors.

So what next? It seems to me my memory is good.

-------------------------------------------------------
Date: Don 17.06.2004 at 12:27       By: 0 <None>
CPU fan is working.
I ran `memtest all 4 -l` (/usr/ports/sysutils/memtest) but received no errors.
I will try memtest86 from boot CD later.

Also my memory speed settings are set to conservative "normal", which is the 
slowest possible setting.

-------------------------------------------------------
Date: Sam 05.06.2004 at 07:19       By: 0 <None>
Try this for memory test:
http://www.memtest86.com/
Is CPU fan working?

-------------------------------------------------------
Date: Don 03.06.2004 at 22:09       By: 0 <None>
Good to hear that. My CPU is not overclocked, but maybe I should try some more 
conservative memory speed settings. It's set to the default "normal", I think, 
but I will check this ...

-------------------------------------------------------
Date: Mit 02.06.2004 at 21:05       By: Artifex Maximus <artifex>
This signals mostly related to bad memory or overclocking. I use the same OS 
but on a good old Celeron 300A without any probs.

FreeBSD 4.10-PRERELEASE #0: Wed May 19 02:40:19 CEST 2004
    address@hidden:/usr/obj/usr/src/sys/pass
CPU: Pentium II/Pentium II Xeon/Celeron (298.73-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x660  Stepping = 0
  
Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
real memory  = 301989888 (294912K bytes)
avail memory = 290680832 (283868K bytes)

34785  ??  SNs  972:43.46 /usr/local/bin/mlnet-real ...

-------------------------------------------------------
Date: Mon 31.05.2004 at 22:08       By: 0 <None>
I've attached the output of `grep mlnet-real` /var/log/messages` as 
mlnet-dies.txt. It seems that mlnet-real dies at least once a day. Currently we 
have a total of 35 files in download, in sum 20 GB.


-------------------------------------------------------
Date: Sam 29.05.2004 at 18:07       By: spiralvoice <spiralvoice>
Do you know under which circumstances the core dies? How long did the core run?




CC List
-------

CC Address                          | Comment
------------------------------------+-----------------------------
raxion                              | 



File Attachments
-------------------

-------------------------------------------------------
Date: Mon 31.05.2004 at 22:08  Name: mlnet-dies[1].txt  Size: 2,28KB   By: None
Output of `grep mlnet-real`.
http://savannah.nongnu.org/bugs/download.php?item_id=9138&amp;item_file_id=1360

-------------------------------------------------------
Date: Fre 28.05.2004 at 08:58  Name: part_of_my_messages.txt  Size: 1,05KB   
By: None
An excerpt of my /var/log/messages
http://savannah.nongnu.org/bugs/download.php?item_id=9138&amp;item_file_id=1348






For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=9138>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/