With More than 3 Clients All Connections Fail - MacOS Sierra 10.12

[silvether]

When 3 or more clients are created in Demonsaw under MacOS Sierra 10.12, router connections cannot be made and all clients fail to connect.

Console logs show the following:

library:libsystem_dnssd.dylib

dnssd_clientstub deliver_request: socketpair failed 24 (Too many open files) 

Reproduction Steps:

1. Open Demonsaw and and create a client of any name
2. Create two more Demonsaw users, again of any name
3. Click the "Restart Clients/Routers" button and note that one or more of the client connections now indicate a connection issue.

Further attempts to restart the clients individually or all at once allow intermittent connectivity, with only one client actually being able to connect but eventually failing.

• silv

[eijah]

You need to increase the Mac number of sockets.  Apparently osx is crippling you :/ go apple...
On Oct 7, 2016 12:38 PM, silvether notifications@github.com wrote:When 3 or more clients are created in Demonsaw under MacOS Sierra 10.12, router connections cannot be made and all clients fail to connect.

Console logs show the following:

library:libsystem_dnssd.dylib

dnssd_clientstub deliver_request: socketpair failed 24 (Too many open files)

Reproduction Steps:

Open Demonsaw and and create a client of any name Create two more Demonsaw users, again of any nameClick the "Restart Clients/Routers" button and note that one or more of the client connections now indicate a connection issue.

Further attempts to restart the clients individually or all at once allow intermittent connectivity, with only one client actually being able to connect but eventually failing.

silv

—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

[silvether]

Will all MacOS users have to manually increase socket limits to work around this? I would still consider this a Demonsaw bug given that it doesn't run within default system wide settings out of the box. I have brought MacOS to its knees with many other intensive(file descriptors/tcp) apps and have not hit socket limitations. OSX default settings are not unreasonable and have been more than sufficient for currently available applications.

Roughly how many sockets are needed for Demonsaw to start and maintain a single idle client with no further interaction within the UI? Is Demonsaw being efficient in how it cleans up after itself/addresses resources?

If tweaking the socket limits will be required, we should hone in on an appropriate value that all users will be required to set before using Demonsaw and outline it in docs.

Happy to test.

UPDATE:

I will be comparing file limits in *Nix vs. MacOS and will set them to similar values. We can find a good value for MacOS that way.

[eijah]

No other OS has this restriction, for some reason Apple has decided it’s in the best interest of its customers to restrict them in this way. :/

DS uses 2 sockets per transfer router + # of logical cores for each client. More message routers & other options will increase sockets too.

There is nothing I can do in DS 3.x to fix this on OSX. DS 4 will use fewer sockets overall as transfer routers will not be in their own state machines.

-E

From: silvether [mailto:notifications@github.com]
Sent: Friday, October 7, 2016 4:50 PM
To: demonsaw/Issues Issues@noreply.github.com
Cc: Eijah eijah@demonsaw.com; Comment comment@noreply.github.com
Subject: Re: [demonsaw/Issues] With More than 3 Clients All Connections Fail - MacOS Sierra 10.12 (#30)

Will all MacOS users have to manually increase socket limits to work around this? I would still consider this a Demonsaw bug given that it doesn't run within default system wide settings out of the box. I have brought MacOS to its knees with many other intensive(file descriptors/tcp) apps and have not hit socket limitations. OSX default settings are not unreasonable and have been more than sufficient for currently available applications.

Roughly how many sockets are needed for Demonsaw to start and maintain a single idle client with no further interaction within the UI? Is Demonsaw being efficient in how it cleans up after itself/addresses resources?

If tweaking the socket limits will be required, we should hone in on an appropriate value that all users will be required to set before using Demonsaw and outline it in docs.

Happy to test.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #30 (comment) , or mute the thread https://github.com/notifications/unsubscribe-auth/AK-G6qtJ1Kbn-CtVkRiTr3AKDTSh-TDLks5qxrCUgaJpZM4KRYrM . https://github.com/notifications/beacon/AK-G6n9PANXtwpxpAWNGPzd0dT0jKWRbks5qxrCUgaJpZM4KRYrM.gif

[silvether]

Yeah, MacOS is pinned at about 12k it looks. :/

kern.maxfiles: 12288
kern.maxfilesperproc: 10240

I will test what number needs to be set for Demonsaw to allow 3+ clients and see if we can add it to docs. Even if there are only a few OSX users rocking Demonsaw atn it might help a few people until DS4.

I will close this and test further when I have time.

[silvether]

Still an issue. Not a limitation of the OS, but an issue of efficiency in code.