Resolv hostname problem about lua-resty-redis

[agentzh]

@ismaelvacco This error happens when your previous redis operation failed with a fatal error (in that case, the underlying cosocket is automatically closed). The fix is simple: just always properly handle the errors of every redis opreations that could possibly fail in your own Lua code.

[jonhatalla]

I too have encountered this issue.

The issue seems to be completely related to the hostname not resolving, as interchanging the ip address of the hostname will also resolve the problem.

However in the case of aws - hostnames are preferable because we are using cname records that point to amazon's elasticache instances, which the underlying ip address is not guaranteed to be fixed.

[juniorplenty]

+1 @agentzh I think you misunderstood the OP - this is related to hostname resolution vs hard coded IP, meaning the original socket can't even be set up...

[jonhatalla]

@ismaelvacco I have a fix for this, and its very clean. My best guess is that Lua does not know how to resolve the hostname.

We are inside a VPC, we have set our vpc to use the 10.8.0.0/16 address range. In my /etc/nginx/nginx.conf, i added the following line in the nginx conf file: resolver 10.8.0.2;

The basis for that line comes from the following url:
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html#AmazonDNS
For example, the DNS Server on a 10.0.0.0/16 network is located at 10.0.0.2

[agentzh]

@jonhatalla Yes, you need to configure the "resolver" directive properly. If you handle errors properly you should see the error returned by the earlier connect() call.