Get an error while running 2 Bitmessage clients in deamon mode on one machine

[merlink01]

Exception in thread Thread-37:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 808, in __bootstrap_inner
self.run()
File "/home/merlink/Workspace/Bitmessage/mainbug/PyBitmessage/src/class_singleListener.py", line 44, in run
sock.bind((HOST, PORT))
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
error: [Errno 98] Address already in use

Could this cause an error in the client, so that the connections to other peers get lost?

If yes, we should test this port before opening it.

[AyrA]

change the incoming port in the settings of one client to another number.

[merlink01]

As far as I know, this port is only necessary if portforwarding is used, shouldn't we simply do a try,except clause here?

[AyrA]

The client still listens for connections even without port forwarding. If we just put a try block around it and it cannot listen (because of permissions or port already in use) it will silently fail an the user has no clue why his network icon never turns green.

[merlink01]

So we can use a print or log message in the except part?

[AyrA]

most users wont' see the message, if they are not constantly looking at the console.
I would prefer a dialog box. that simply tells you, that the port is already in use and can be changed in the settings if the user wishes to do so.

[PeterSurda]

I'm not going to do anything about this for the time being. I tested this a couple of weeks ago for other reasons and while the listen thread crashed, Bitmessage continued to work.