Ticket #744 (new task)
shared files appear not shared to some peers
| Reported by: | J+ | Owned by: | quinox |
|---|---|---|---|
| Priority: | normal | Milestone: | Release 1.2.17 |
| Component: | nicotine | Version: | SVN |
| Keywords: | Cc: |
Description
Some peers are having problems when trying to download files from me. The file appears "not shared". It's a mysterious error that can't be solved by simply using the software in a different way, and it seems to be part of a larger communication problem that occurs between my client and those of the peers that suffer the problem.
Some general information i've been able to collect so far:
- The peers that get a "file not shared" error are a minority (4 so far); most peers are able to download without problems.
- Rescanning or rebuilding the shares file does not solve the problem, nor does removing the cache databases from the ~/.nicotine directory in order to rebuild them.
- It has nothing to do with buddy-only shares, because the affected files so far were shared to everyone and the problematic peers include both buddies and non-buddies.
- When peers experience the problem, the affected files don't appear in my uploads list.
- Bark, a user with Nicotine+ 1.2.15, reports that he doesn't have the problem.
- SirDutch? cannot download from me because of this problem, but I can download from him.
I've also collaborated with one of the problematic peers (PRasda) in an experiment to reveal some more information. PRasda is using Soulseek 157 ns 13e and generally doesn't experience problems in downloading.
- PRasda accepts upload from users in their buddy list, and I'm in their buddy list. I tried to upload to PRasda. PRasda didn't see the files in their download list. In my upload list, i get the error "connection closed by peer", and after a while the entries disappear automagically.
- I suggested that PRasda would try to download from roboto3785, because I knew he's using Nicotine+ too. PRasda got the same "file not shared" error. I've asked roboto3785 what version of N+ he's using but he didn't respond yet. PRasda will also keep me updated on other users that they get this error from, so more info will follow.
- I tried to download from roboto3785 myself, which worked out fine.
Versions and stuff: N+ trunk rev1468 Python 2.6.6 (x64) from MacPorts? py26-gtk from MacPorts? version 2.22.0 +X11 Mac OS X 10.6.7
Attachments
Change History
comment:2 Changed 2 years ago by anonymous
The mail I got of this ticket has the correct line endings, so all is well.
There is a problem with the new virtual shares and file located deeper than 2 layers. So /virtual/dir/file.mp3 works but /virtual/dir/subdir/file.mp3 doesn't work. I hope to have this fixed by tomorrow
comment:3 follow-up: ↓ 4 Changed 2 years ago by quinox
I fixed the bug of the virtual share with r1469, does that help? (a rescan is most certainly required)
comment:4 in reply to: ↑ 3 Changed 2 years ago by J+
I'm currently not at home, but I'll try as soon as possible and report again when I've seen the result.
comment:6 Changed 2 years ago by anonymous
Thank you very much quinox for continuosly improving Nicitine+. I also udated to version 1.2.17svn version in Ubuntu (using the .deb installation file) some time ago and got the same problem as described and fixed in this ticket. It was quite a big hassle to find out what was wrong until I found this ticket. I first thought it was something wrong with the network settings in the computer, the router, moblock etc and I had to do a lot of testing and asking my friends to check if my fix experiments had helped. In case the installation file is not already updated with this fix I suggest that you do it as soon as possible.Otherwise there could be a risk thatthose who update may find that the sharing do not work and stop using Nicotine / Soulseek before they find this fix. A filesharing client where the sharing do not work has a serious problem and need an emergency fix.

I'm sorry to see that some of my line endings disappeared. I can't edit the post anymore, but if the post is unreadable i'll repeat the text with proper line endings in a new comment.