[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Mldonkey-bugs] [bugs #8580] Writing into file in incoming directory
|
From: |
spiralvoice |
|
Subject: |
[Mldonkey-bugs] [bugs #8580] Writing into file in incoming directory |
|
Date: |
Tue, 10 Aug 2004 10:58:11 -0400 |
|
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7) Gecko/20040616 |
This mail is an automated notification from the bugs tracker
of the project: mldonkey, a multi-networks file-sharing client.
/**************************************************************************/
[bugs #8580] Latest Modifications:
Changes by:
spiralvoice <address@hidden>
'Date:
Tue 08/10/2004 at 14:54 (Europe/Berlin)
------------------ Additional Follow-up Comments ----------------------------
Please try CVS 2-5-27 and report if the bugs is solved
/**************************************************************************/
[bugs #8580] Full Item Snapshot:
URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8580>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: Artifex Maximus
On: Thu 04/15/2004 at 13:04
Category: Core
Severity: 5 - Average
Item Group: Program malfunction
Resolution: None
Assigned to: None
Status: Open
Release: 2-5-16
Release: +Spiralvoice patch k
Platform Version: FreeBSD
Binaries Origin: CVS / Self compiled
CPU type: Intel x86
Summary: Writing into file in incoming directory
Original Submission: I start to download a file. It's slowly finished,
automatically moved to incoming and I received a notification mail. Great. Now
comes the strange part. I download this file to my workstation. After that on
the server in the _incoming_ directory the mldonkey write anything (I don't
know what) into that file. The md4 value changed of course but on my
workstation the file's md4 is correct. What happen? Why MLD write to this file
_after_ committed? Strange...
bye
Follow-up Comments
------------------
-------------------------------------------------------
Date: Tue 08/10/2004 at 14:54 By: spiralvoice
Please try CVS 2-5-27 and report if the bugs is solved
-------------------------------------------------------
Date: Tue 08/10/2004 at 08:29 By: mldonkey
The out-of-memory error is very hard to use, the only thing that could be
useful to do would be to crash the program immediatly before it does any wrong
to the files.
By the way, how do you start mldonkey ? Is it started as a daemon. Indeed, if
it started like that, it is possible that ocaml writes the "Fatal error"
message on stderr, without knowing that the daemon has closed this descriptor
and re-uses it for other files.
-------------------------------------------------------
Date: Tue 08/10/2004 at 03:47 By: m-o-w
Upgraded the machine to 256MB last week, and started mlnet with ulimit of 150MB.
Started mlnet on 2004-08-06 1:30. It went down 2004-08-08 19:19 which I see
from the timestamp of the file it wrote its "Fatal error: out of memory" into
when it did so.
This was a file in a shared folder, not incoming. Still -16q.
grep memory /mld/b0rken_file -a
Ï*_Àxà|w;S1,
ð±îùÇj¬üíyúõìüüK?,9k¡í£^b²L»§<2gM,address@hidden(bæK`¸E+G¹PÅzË-NÛø´õi}²Ü¡¦½?5]õw]=,E9TÀ²EnPJËaÙKúþ¿°Í3J×
,Àh×È,*
M*)D&¼röÕU ,bFatal
error: out of memory.
-------------------------------------------------------
Date: Fri 07/23/2004 at 01:14 By: m-o-w
Does any other user use ulimit to restrict memory usage?
To trigger this problem, you could set the limit to a low value like 30M, that
should kill mlnet quite fast.
I'm a bit reluctant to test right now because mlnet -16q is running since
2004-7-17 and even went down from ~80MB to about 30MB when a big file was
finished, just now it went up to 53MB though.
In -16m, the problem was still there as you can see below. Did you remove any
Printf.printf commands since then?
By the way, a grep -r "Fatal error: out of memory" * in the source tree shows
this error message is not in the mlnet source, but in ocaml itself:
e.g.
Binary file patches/local/lib/ocaml/libcamlrun.a matches
-------------------------------------------------------
Date: Thu 07/22/2004 at 23:58 By: spiralvoice
AFAICS there are no more Printf.printf commands left so I can't really say
which part of the code is responsible. Do users of others OS's have the same
problem? Here (x86 Linux) it never occured.
-------------------------------------------------------
Date: Wed 06/09/2004 at 16:03 By: m-o-w
With 2.5-16m:
When mldonkey just went down reaching the ulimit, I found this:
-rw-r--r-- 1 mow users 28 Jun 9 17:25 downloads.ini.tmp
# cat downloads.ini.tmp
Fatal error: out of memory.
#
-------------------------------------------------------
Date: Mon 05/10/2004 at 14:02 By: artifex
FreeBSD 4.x-STABLE, ocaml 3.07pl2
./configure
--build=i386-artifex-freebsd4.9
--prefix=/usr/local
--enable-local-prefix=/usr/local
--disable-shared
--enable-pthread
--enable-batch
--enable-checks
--enable-multinet
--disable-newgui
--disable-gui
--enable-bittorrent
--enable-donkey
--disable-audiogalaxy
--disable-opennap
--disable-gnutella
--disable-gnutella2
--disable-directconnect
--disable-soulseek
--disable-openft
--disable-cymes
--disable-fasttrack
gmake depend
gmake
bye
-------------------------------------------------------
Date: Sun 05/09/2004 at 18:12 By: m-o-w
I didn't. That was the mlnet from the mldonkey-2.5-16l.static.i386-Linux.rar
archive you provided.
-------------------------------------------------------
Date: Sun 05/09/2004 at 15:29 By: spiralvoice
How did you compile MLDonkey?
-------------------------------------------------------
Date: Sat 05/08/2004 at 19:53 By: m-o-w
The problem is even worse than just what the patch addresses according to its
description.
To work around my memory problems (see bug#7967) I set ulimits. Now in the last
two days I got two files that suddenly got a current timestamp. This did not
happen in the weeks before.
I ran a fc on the second file because I happened to have an unchanged copy
still lying around, and guess what:
Q:mldonkeyincoming>fc "filename*.*" f:*.*
Vergleichen der Dateien gehteuchnixan und F:gehteuchnixan
***** gehteuchnixan
wäÃ+♦$V‗É^ãÁqudé¸ù♀¯r▲<⌂/«░╔0ëë└j‗¨S_→-~╠▲#b£#>ï´Ý↔
½D╔╔6( ■▓²LØ♣5?2☺┘ìµ3 ║Y
☺ _‗╔ôÌïnøOoG{§9S;┬6usöF╔+
Ã|æºæº_‼╦0╠‼░#Mt¿4dìÓeÝЪ,1#█VÕÞîqWxá┘U1Ù¢‼ó¶§┼Fatal
error: out of memory.
ÙOºÈÚÃé↔Ij}TR♀Ü☻ìOñ_ê¬s▲
ı+◄ªYIÓ♀♦êå¸:þ╔Æ┤▒∟♣►må↓┤↓Üê¨Ðäô▓ba×╝►┌¶ú`rñóa-C
Ñ╬address@hidden╝ß→♂©ËW¿^úÉÍ[¾⌂UÕi!9↓♂♫∟∟¹â▲¹Ü"├¸oY=Ñ╩▒<◄³*#2å♫7µ÷mÊé=ÌrÞ╔@÷â☺
«¨Ü░0È║³|½àÓú°êÌK→Ê↕4↓ Ï└Û╣
***** F:gehteuchnixan
wäÃ+♦$V‗É^ãÁqudé¸ù♀¯r▲<⌂/«░╔0ëë└j‗¨S_→-~╠▲#b£#>ï´Ý↔
½D╔╔6( ■▓²LØ♣5?2☺┘ìµ3 ║Y
☺ _‗╔ôÌïnøOoG{§9S;┬6usöF╔+
Ã|æºæº_‼╦0╠‼░#Mt¿4dìÓeÝЪ,1#█VÕÞîqWxá┘U1Ù¢‼ó¶§┼♦SL☻↑ñ½ßúæâxHqEºO♣ľ☺ë^ßÜGs.ÙOºÈÚ
Ãé↔Ij}TR♀Ü☻ìOñ_ê¬s▲
ı+◄ªYIÓ♀♦êå¸:þ╔Æ┤▒∟♣►må↓┤↓
ê¨Ðäô▓ba×╝►┌¶ú`rñóa-C
Ñ╬address@hidden╝ß→♂©ËW¿^úÉÍ[¾⌂UÕi!9↓♂♫∟∟¹â▲¹Ü"├¸oY=Ñ╩▒<◄³*#2å♫7µ÷mÊé=ÌrÞ╔@÷â☺
«¨Ü░0È║³|½àÓú°êÌK→Ê↕4↓ Ï└Û╣
*****
So when mlnet got to the ulimit, it wrote "Fatal error: out of memory." into
the file.
I guess it's just murphy that I got this twice the last two days and never
before, this message probably got written into some not-yet-fully-downloaded
file which then got reloaded in the next chunk check.
So there are probably some more rogue printfs in there which wait to bite our
asses.
-------------------------------------------------------
Date: Mon 04/26/2004 at 16:14 By: artifex
I applied the patch and start to test. Any report will go to the patch section.
bye
-------------------------------------------------------
Date: Fri 04/23/2004 at 21:45 By: spiralvoice
Please try patch 2965 and report if it helps
-------------------------------------------------------
Date: Sun 04/18/2004 at 09:42 By: artifex
I take a look into the source and set min_users_on_server back to zero and
therefore MLD never try to remove any server. Problem is gone but this is just
a temporary solution, I think.
BTW, I try -18 and it collects sources but don't start to download. I switched
back to -16l and stuffs started to come. :)
bye
-------------------------------------------------------
Date: Sat 04/17/2004 at 07:03 By: artifex
It's happen again with another file. After that I upgraded my MLD to -18 and
hope the problem is gone. BTW, I attached an image what happen with my file.
It's looks like the log file goes into the file.
bye
File Attachments
-------------------
-------------------------------------------------------
Date: Sat 04/17/2004 at 07:03 Name: 16hp_err_2.png Size: 20.02KB By: artifex
Image with the problematic part of file
http://savannah.nongnu.org/bugs/download.php?item_id=8580&item_file_id=1200
For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8580>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [Mldonkey-bugs] [bugs #8580] Writing into file in incoming directory,
spiralvoice <=