You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No idea why, but sometimes the getFile command response is lost in space:
[2015-01-29 17:52:32,391] DEBUG src.File.FileServer FileRequest: update 1Gfey7wVXXg1rxk751TBTxLJwhddDNfcdp content.json
[2015-01-29 17:52:32,391] DEBUG src.File.FileServer Someone trying to push a file to own site 1Gfey7wVXXg1rxk751TBTxLJwhddDNfcdp, reload local content.json first
[2015-01-29 17:52:32,507] DEBUG src.File.FileServer Update for content.json looks valid, saving...
[2015-01-29 17:52:32,512] INFO src.File.FileServer 1Gfey7..fcdp changed files: [u'messages.json']
[2015-01-29 17:52:32,513] DEBUG Peer:104.xxx:15441 sendCmd: ping
[2015-01-29 17:52:32,515] DEBUG Peer:104.xxx:15441 Sent command: ping
[2015-01-29 17:52:32,716] DEBUG Peer:104.xxx:15441 Got response to: ping
[2015-01-29 17:52:32,717] DEBUG Peer:104.xxx:15441 Ping: 0.203
[2015-01-29 17:52:32,717] DEBUG Peer:104.xxx:15441 sendCmd: getFile
[2015-01-29 17:52:32,717] DEBUG Peer:104.xxx:15441 Sent command: getFile
And its stops here, 20s later got the file from other peers, but not from this one
The socket is alive, because the ping command get the response, but the getFile response never arrives.
No idea why, but sometimes the getFile command response is lost in space:
The socket is alive, because the ping command get the response, but the getFile response never arrives.
From server side everythiing looks allright:
I think its mostly happens after my computer wakes from sleep.
Maybe the zeromq server side in not compeltely thread safe maybe its other problem.
Sooner or later i think we have to get rid of the zeromq (too much limitations), but would be nice to know whats the reason of this problem.
The text was updated successfully, but these errors were encountered: