Skip to content

Device re-connection uses a New Socket and Eventually Fails #38

@GoogleCodeExporter

Description

@GoogleCodeExporter
This is  superb implementation and I have been connecting successfully to an 
RTU using Modbus TCP/IP over Ipsec for several months. 

However the following issue means that the Slave has to be restarted regularly: 

1. The connection is over Ipsec and the other end (Cisco, out of my control) 
renegotiates the connection every 20 mins
2. When the connection is re-established the Master connects with a new Socket
3. This leads to a 'climb' up the sockets and eventually the Slave freezes. 
4. on restart the address is often claimed to be in use

I think there are two issues: 
a) using a new socket each time
b) not releasing the address

I suspect b is the socket library but any help on a) or if it is a bug would be 
great. 

I am using 0.4.2 on Ubuntu 12.04 server, Python 2.7 latest



Original issue reported on code.google.com by nicholas...@gmail.com on 2 Sep 2013 at 9:30

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions