Share

nget

Tracker: Bugs

5 Killed when retrieving headers - ID: 810446
Last Update: Comment added ( phar0s )

I get the following error when selecting huge newsgroups:

[pharos@callisto friends]$ nget -g
alt.binaries.boneless -r 'friends_s4'
make_connection(1,newszilla.xs4all.nl,nntp,0xbfffe3b0,512)
Connecting to 194.109.133.20:119
h >> 200 dreader4.news.xs4all.nl NNRP Service Ready -
newsmaster@xs4all.nl (posting ok).
h << GROUP alt.binaries.boneless
h >> 211 600001 29408733 30008733 alt.binaries.boneless
Flushing headers 22891575-23276095(384521): 384520
(384515,16682)
Retrieving headers 29408733-30008733 :
443207/599996/600001 73% 67620B/s 10m56sKilled

Smaller groups have no problems. The news server is a
Diablo newsserver on BSD. Client is a Red Hat 7.2 with
nget 0.24.1. I have emptied the local cache directory.


Pharos ( phar0s ) - 2003-09-22 07:44

5

Closed

None

Nobody/Anonymous

None

None

Public


Comments ( 2 )

Date: 2003-10-04 16:25
Sender: phar0s

Logged In: YES
user_id=587870

Ulimit was on default values. Seems to work fine since i
doubled the ram on my server. I have been downloading
without errors for a week now.


Date: 2003-09-25 23:40
Sender: donutProject Admin

Logged In: YES
user_id=65253

So is it simply exhausting your memory and getting killed by
the OOM (out-of-memory) killer? How much ram/swap do you
have? Do you have any ulimit set for max memory per process?


Attached File

No Files Currently Attached

Changes ( 2 )

Field Old Value Date By
status_id Open 2003-10-04 16:25 phar0s
close_date - 2003-10-04 16:25 phar0s