failure:passkey is already in use by another peer.the passkey has been marked to be reset,please redownload all of your active..
haojiang - July 2, 2009 - 09:00
| Project: | BitTorrent |
| Version: | 6.x-9.2-alpha3 |
| Component: | Documentation |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
drupal6.13 , bittorrent(BitTorrent and BT_Tracker only) , cck and filefield , views ____clear installation
private tracker mode.
my bittorrent-client showed the following problem on my second uploaded *.bittorrent (i have to mention that my first uploaded *.bittorrent test is everything all right!)
failure:passkey is already in use by another peer.the passkey has been marked to be reset,please redownload all of your active torrents.see the attachment for a visual view,the above green one is my first test which is ok , but the red one which is my second test is failed.
it always asked me to redownload , but i had already download a few times , it still not worked.
could you please describe how to make the second private tracker *.bittorrent.
by the way , you should check "http://drupal.org/node/501944" , i think your install.txt must have left one step to mention.
| Attachment | Size |
|---|---|
| 1.jpg | 96.56 KB |
#1
For unknown reasons, I cannot download "1.jpg", 'cause it's link to http://drupal.org/files/issues ...
But I understood what you mean.
I have one suggestion. Do you run testing on virtual machines and do it by one user account?
If the tracker see several connections by one user from several IPs, it reset user's passkey.
#2
you're right.
thx.
but , i logout this account "admin", and delete all the upload *.torrent and download *.torrent in both machine's bittorrent-clients.
then i upload a *.torrent for a clear test using a new account "testA" on "machineA",
and download this *.torrent using account "testB" on "machineB".
everything goes all right now
however
when i login using account "admin" on machine B again, and download the same *.torrent ,
the new tracker in my bittorrent-client showedup again the failure, "failure:passkey is already in use by another peer.the passkey has been marked to be reset,please redownload all of your active.."
how could i make account "admin" available on machine B?
#3
what's more , if i am using account "userA" to download a file , and then i would like to upload a *.torrent to let the other user to download my shares ,
this failure "passkey is already in use by another peer.the passkey has been marked to be reset,please redownload all of your active..""
will show up , too
it means that a user could not download and upload at the same time , is it rare?
#4
Did you made something between these two processes?
I don't have any suggestions...
Can you provide a dump of bt_* tables?
#5
machineA and machineB are two physical different machines.
my drupal-bittorrent-website was installed on macine B.
and then do the above test.
please see the attachment, "a dump of bt_* tables", i guest you want to see my mysql_bt_* tables .
#6
I have a one suggestion...
Do you have CRON running for your bittorrent drupal installation?
Records in bt_tracker_connections table can still exist after deletion of active downloads (uploads) from client, because client doesn't send a "stop" message to client when someone delete active downloads (uploads).
If you have not CRON running, records from this table will not be deleted, because they are deleted by CRON, after specified (at admin page ("Auto-prune Interval")) time of inactivity of a connection.
P.S. you can use http://drupal.org/project/poormanscron module for this.
#7
well , suppose that corn.php really fixed this problem.
userA , who is downloading a *.torrent-releated file , still could not upload a *.torrent , am i right?.
if i am right about this question, is it rare enough ?
by the way , what is your option between drupal-default-cron.php and poormanscron?
#8
No. If it is, it's a bug.
Try to test this with cron running on.
Ability to run cron depends on using server, so you can have ability to run cron, or can have not. If you have not this ability, you can use poormanscron module to "emulate" cron, or use external cron service (google it).
#9
Please, tell me, if the issue is fixed successfully, or change it's status to fixed.
#10
i need more time to test , i still got stuck on somewhere.
#11
even after i run cron.php successfully , this failure continue ,
it seems it was not correalated with cron.
#12
tested alpha5 today , and hope that this problem would fixed on the new version
, but encounting an update problem which i found a few days before ,but not fixed yet
test on clear installation tomorrow