StackExchange.Redis Cannot Connect to Mono on Mac OS X

Question

I am trying to run a very simple Redis client on Mono on Mac OS X with the following options:

var configOptions = new ConfigurationOptions() { EndPoints = { { "localhost", 6379 }, }, ResolveDns = true, KeepAlive = 180 }; StringWriter sw = new StringWriter(); ConnectionMultiplexer.Connect(configOptions, tw); 

Unable to connect. Here is the trace:

 localhost:6379,keepAlive=180,resolveDns=True Using DNS to resolve 'localhost'... 'localhost' => 127.0.0.1 1 unique nodes specified Requesting tie-break from 127.0.0.1:6379 > __Booksleeve_TieBreak... Allowing endpoints 00:00:01 to respond... 127.0.0.1:6379 faulted: UnableToResolvePhysicalConnection on PING 127.0.0.1:6379 failed to nominate (Faulted) > UnableToResolvePhysicalConnection on GET No masters detected 127.0.0.1:6379: Standalone v2.0.0, master; keep-alive: 00:03:00; int: Connecting; sub: Connecting; not in use: DidNotRespond 127.0.0.1:6379: int ops=0, qu=0, qs=0, qc=1, wr=0, async=1, socks=2; sub ops=0, qu=0, qs=0, qc=0, wr=0, socks=1 Circular op-count snapshot; int: 0 (0.00 ops/s; spans 10s); sub: 0 (0.00 ops/s; spans 10s) Sync timeouts: 0; fire and forget: 0; last heartbeat: -1s ago Starting heartbeat... 

I tried with and without ResolveDNS and directly specified the IP address. I tried several ports. The server is up and running on redis-cli.

StackExchange.Redis version = "1.0.289" targetFramework = "net45"

Redis-64 2.8.9

Update

StackExchange.Redis version = "1.0.297" targetFramework = "net45", same problem, but different log

local: 6666, Keepalive = 180, resolveDns = True

 Using DNS to resolve 'localhost'... 'localhost' => 127.0.0.1 1 unique nodes specified Requesting tie-break from 127.0.0.1:6666 > __Booksleeve_TieBreak... Allowing endpoints 00:00:05 to respond... 127.0.0.1:6666 faulted: UnableToResolvePhysicalConnection on PING 127.0.0.1:6666 failed to nominate (Faulted) > UnableToResolvePhysicalConnection on GET No masters detected 127.0.0.1:6666: Standalone v2.0.0, master; keep-alive: 00:03:00; int: Connecting; sub: Connecting; not in use: DidNotRespond 127.0.0.1:6666: int ops=0, qu=0, qs=0, qc=1, wr=0, async=1, socks=2; sub ops=0, qu=0, qs=0, qc=0, wr=0, socks=1 Circular op-count snapshot; int: 0 (0.00 ops/s; spans 10s); sub: 0 (0.00 ops/s; spans 10s) Sync timeouts: 0; fire and forget: 0; last heartbeat: -1s ago resetting failing connections to retry... retrying; attempts left: 2... 1 unique nodes specified Requesting tie-break from 127.0.0.1:6666 > __Booksleeve_TieBreak... Allowing endpoints 00:00:05 to respond... 127.0.0.1:6666 returned, but incorrectly 127.0.0.1:6666 failed to nominate (Faulted) > UnableToResolvePhysicalConnection on GET No masters detected 127.0.0.1:6666: Standalone v2.0.0, master; keep-alive: 00:03:00; int: Disconnected; sub: Connecting; not in use: DidNotRespond 127.0.0.1:6666: int ops=0, qu=0, qs=0, qc=1, wr=0, async=5, socks=3; sub ops=0, qu=0, qs=0, qc=0, wr=0, socks=2 Circular op-count snapshot; int: 0 (0.00 ops/s; spans 10s); sub: 0 (0.00 ops/s; spans 10s) Sync timeouts: 0; fire and forget: 0; last heartbeat: -1s ago resetting failing connections to retry... retrying; attempts left: 1... 1 unique nodes specified Requesting tie-break from 127.0.0.1:6666 > __Booksleeve_TieBreak... Allowing endpoints 00:00:05 to respond... 127.0.0.1:6666 returned, but incorrectly 127.0.0.1:6666 failed to nominate (Faulted) > UnableToResolvePhysicalConnection on GET No masters detected 127.0.0.1:6666: Standalone v2.0.0, master; keep-alive: 00:03:00; int: Disconnected; sub: Connecting; not in use: DidNotRespond 127.0.0.1:6666: int ops=0, qu=0, qs=0, qc=1, wr=0, async=8, socks=4; sub ops=0, qu=0, qs=0, qc=0, wr=0, socks=3 Circular op-count snapshot; int: 0 (0.00 ops/s; spans 10s); sub: 0 (0.00 ops/s; spans 10s) Sync timeouts: 0; fire and forget: 0; last heartbeat: -1s ago 

Answer 1

I had the same problem as when using the nuget package. I cloned the StackExchange.Redis repository and created a new DLL with the bash command turned on for mono:

 ./monobuild.bash 

Link to the resulting DLL, and it worked flawlessly on OSX with the exact code that you posed in the question.

Answer 2

As already noted, StackExchange.Redis has problems connecting to the server in mono, and you need to create a custom assembly from the source, focusing on Mono. Therefore, I created the nuget package from the monoblock library using monobuild.bash. You can use it as a direct replacement of the original StackExchange.Redis with mono.

https://www.nuget.org/packages/StackExchange.Redis.Mono/

Since we use the package in our server application, I will update it regularly.