ServiceStack.Redis.RedisException

731 views
Skip to first unread message

bala wagh

unread,
Jul 29, 2014, 3:35:59 AM7/29/14
to redi...@googlegroups.com

Hi All,

I am Facing this issue frequently... getting this kind of logs .. But on SAme Server log file is running and there is no any kind of connection failed log.. plz see the attachment 

ServiceStack.Redis.RedisException: could not connect to r...ServiceStack.Redis.RedisException: could not connect to redis Instance at 192.168.1.87:6379 ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.87:6379
   at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)
   at System.Net.Sockets.Socket.Connect(String host, Int32 port)
   at ServiceStack.Redis.RedisNativeClient.Connect()
   --- End of inner exception stack trace ---
   at ServiceStack.Redis.RedisNativeClient.Connect()
   at ServiceStack.Redis.RedisNativeClient.AssertConnectedSocket()
   at ServiceStack.Redis.RedisNativeClient.SendCommand(Byte[][] cmdWithBinaryArgs)
   at ServiceStack.Redis.RedisNativeClient.SendExpectLong(Byte[][] cmdWithBinaryArgs)
12:54

Log.jpg

Demis Bellot

unread,
Jul 29, 2014, 3:53:04 AM7/29/14
to redi...@googlegroups.com
This is an underlying network exception when the client can't make a TCP connection with the remote server.
You want to first make sure that you have connectivity and can establish a connection from the PC that's running the RedisClient to the redis-server. 

1) You can use redis-cli to access the above ip + port. Which you can download for windows at: https://github.com/mythz/redis-windows

2) You can also use telnet to make a raw tcp connection (installation for windows).

On the command prompt type:

telnet 192.168.1.87 6379
 
If you have a tcp connection it will connect and show you a blank screen. You can then type INFO to see the results of Redis INFO Command

3) Otherwise you can always use a TCP packet sniffer like WireShark to inspect the packets on the wire, to make sure you're getting packets returned from server.

- Demis




--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at http://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.

Message has been deleted

bala wagh

unread,
Jul 29, 2014, 8:51:07 AM7/29/14
to redi...@googlegroups.com
Thanks Demis,
But since a year i am using the Redis Server on(Windows)  and Client is with .Net services and it was working fine. But we migrated Redis Server on Ubuntu12.10..and it is going fine but from few days  I am facing this issue..
why Is it happing ...

Josiah Carlson

unread,
Jul 29, 2014, 10:53:59 AM7/29/14
to redi...@googlegroups.com
Have you tested connectivity between your Redis client and server? Maybe by using one of the tools that Demis pointed out? Part of the reason why Demis mentioned using Windows is because it seems as though your *client* is running on Windows, which is where you need to test from.

 - Josiah
Reply all
Reply to author
Forward
0 new messages