Closed jimboman77 closed 10 years ago
It would help, if you could provide additional information like:
1) ur OS 2) PC config (cpu, memory) 3) Usenet provider 4) what poster do you usually use to upload stuff that works fine for you 5) 300 mb - is it a single rar size? What's generally the total size of you uploads per session(like 50Gb or more?) 6) if ur provider is astraweb, do you use eu or us server? 7) did you happen to notice how much memory sanguinews use during the upload process?
cheers
@jimboman77 I was unable to reproduce the bug with multiple 300MB files, so it would be helpful, if you've answered the questions provided by @Semela in the post above.
1.)VPS thats got 512MB of ram and shared CPU that grants me low disk I/O priority.
2.)Debian 7
3.)Usenetbucket EDIT: should be "THECUBENET", not "usenetbucket"
4.)newsmangler + stunnel
5.)No not a single rar, just a directory with binary files in them + par2 files
7.)Dunno how much memory was used. Dunno how I'd be able to check on a VPS.
I will try uploading on a home machine later on to see if the problem is related to the way the program handles restrictions imposed by a VPS.
So I just noticed from looking at one of the uploads that I did that parts 1-21 all uploaded fine but the next 200 after that I had missing parts everywhere. Verbose mode mentioned a lot of faliures/retries. I'm thinking maybe it has something to do with threading or something like that? Tried it on another server with another provider and noticed the same phenomenon, the first few dozen parts upload fine, but then it starts breaking everywhere.
@jimboman77 one more thing. Are we talking about the same version? The latest version is 0.48.2. You could see the build version by opening sanguinews.rb - version variable will be at the top. Also, does your VPS has any SWAP? I'll try reproducing this issue on a box with limited RAM.
Yes using most up to date version. Dunno if VPS has SWAP, how do I check? One thing that may also be affecting the bug is the number of connections. Its set to 5 on newsmangler vs 10 on sanguinews
You can check available memory and swap with:
free -m
I've tested sanguinews with variable number of connections and haven't seen a problem so far, so I doubt that this could be an issue in your case, but you could try to set this parameter to 5 and tell me, how it goes.
Ok, yes I have 256MB of swap on 512MB of ram
The recent releases introduce various checks and stability control for low-end machines. Please reopen the issue if problem still present.
Steps to recreate this issue:
All my uploads so far have had a ton of missing parts. So many missing parts that it has rendered this program practically useless as in its current form. Is there nothing like a pairity check to ensure the content did not get lost along the way?