Skip to content

PortFusion 1.2.0: Network.Socket.ByteString.recv: failed (Unknown error) #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tt2012 opened this issue Jun 20, 2012 · 5 comments
Closed

Comments

@tt2012
Copy link

tt2012 commented Jun 20, 2012

Hi again,

I've tested the new version (1.2.0) of Port Fusion this week.
Everything works fine the first 1,2 hours, but after some point in time Port Fusion no longer works.
I've written the console output to some text files in order to have some kind of logs.

Here's what I've found interesting.
Output on the (external) system within the DMZ:
CORSIS PortFusion ( ]-[ayabusa 1.2.0 ) (c) 2012 Cetin Sert. All rights reserved. Windows - x86 [Thu Jun 14 07:28:06 2012] Listen :^: (IPv4,1080)
...
...
Accept :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xx.xxx.xx.xx:xxxxx)
Establish ::: FusionLink (Just xxx.xx.xxx.x:xxxxx) (Just xxxx) (Just xx.xxx.xx.xx:xxxxx)
Accept :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xxx.xx.xxx.x:xxxxx)
Receive ((:-<-:) xxxx) :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xxx.xx.xxx.x:xxxxx)
Terminate ::: FusionLink (Just xxx.xx.xxx.x:xxxxx) (Just xxxx) (Just xx.xxx.xx.xx:xxxxx)
Close :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xxx.xx.xxx.x:xxxxx)
Close :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xx.xxx.xx.xx:xxxxx)
Accept :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xx.xxx.xx.xx:xxxxx)
Establish ::: FusionLink (Just xxx.xx.xxx.x:xxxxx) (Just xxxx) (Just xx.xxx.xx.xx:xxxxx)
Accept :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xxx.xx.xxx.x:xxxxx)
Receive ((:-<-:) xxxx) :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xxx.xx.xxx.x:xxxxx)
Terminate ::: FusionLink (Just xxx.xx.xxx.x:xxxxx) (Just xxxx) (Just xx.xxx.xx.xx:xxxxx)
Close :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xxx.xx.xxx.x:xxxxx)
Close :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xx.xxx.xx.xx:xxxxx)
Accept :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xx.xxx.xx.xx:xxxx)
Establish ::: FusionLink (Just xxx.xx.xxx.x:xxxxx) (Just xxxx) (Just xx.xxx.xx.xx:xxxx)
Terminate ::: FusionLink (Just xxx.xx.xxx.x:xxxxx) (Just xxxx) (Just xx.xxx.xx.xx:xxxx)
Close :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xxx.xx.xxx.x:xxxxx)
Close :.: PeerLink (Just xxx.xx.xx.xxx:xxxx) (Just xx.xxx.xx.xx:xxxx)
Watch :^: (IPv6(+4?),5001)
Drop :^: (IPv6(+4?),5001)
Close :.: PeerLink (Just 0.0.0.0:5001) Nothing

I guess the issue is somehow related to the Watch & Drop message on the last three lines. Why it shows IPv6, when we have started PortFusion with (IPv4,1080)?
The output before these lines are fine. Strange is in addition that the last PeerLink has all the "0" in the address.

Here's the output for the internal system:
Open :.: PeerLink (Just xxx.x.x.x:xxxxx) (Just xxx.x.x.x:xxxx)
Establish ::: FusionLink (Just xxx.xx.xx.xxx:xxxx) (Just 63658) (Just xxx.x.x.x:xxxx)
Terminate ::: FusionLink (Just xxx.xx.xx.xxx:xxxx) (Just 63658) (Just xxx.x.x.x:xxxx)
Close :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Close :.: PeerLink (Just xxx.x.x.x:xxxxx) (Just xxx.x.x.x:xxxx)
Close :.: PeerLink (Just x.x.x.x:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Network.Socket.ByteString.recv: failed (Unknown error)
Open :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Send ((:-<-:) xxxx) :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Close :.: PeerLink (Just x.x.x.x:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Network.Socket.ByteString.recv: failed (Unknown error)
Open :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Send ((:-<-:) xxxx) :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Close :.: PeerLink (Just x.x.x.x:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Network.Socket.ByteString.recv: failed (Unknown error)
Open :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Send ((:-<-:) xxxx) :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Close :.: PeerLink (Just x.x.x.x:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Network.Socket.ByteString.recv: failed (Unknown error)
Open :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Send ((:-<-:) xxxx) :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Close :.: PeerLink (Just x.x.x.x:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Network.Socket.ByteString.recv: failed (Unknown error)
Open :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Send ((:-<-:) xxxx) :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Close :.: PeerLink (Just x.x.x.x:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Network.Socket.ByteString.recv: failed (Unknown error)
Open :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)
Send ((:-<-:) xxxx) :.: PeerLink (Just xx.xx.xxx.xxx:xxxxx) (Just xxx.xx.xx.xxx:xxxx)

Here you find lots of Network.Socket.ByteString.recv: failed messages.

Can you check this issue, please?

Thanks and best regards

@tt2012
Copy link
Author

tt2012 commented Jun 27, 2012

Hey guys,

no update from your side?

@abijoshi
Copy link

Hello,
Waiting for reply here?

Thanks,
abjoshi

@CetinSert
Copy link
Member

Sorry for the late reply. I am almost ready with a new bugfix release. Could you test a 64-bit Windows binary?

@CetinSert
Copy link
Member

Closed, 1.2.1 due by 2012-08-20 will include a fix tested rigorously with tools like ab (ApacheBench) and httpperf on GNU/Linux. Connection initialization times on GNU/Linux are also going to improve several orders of magnitude due to switching to the data splice loop used on other operating systems as well.

@CetinSert
Copy link
Member

1.2.1 has been released.

Please see the change log.

@ghost ghost assigned CetinSert Aug 26, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants