twemproxy does not startup if it cannot resolve hostnames about twemproxy HOT 4 CLOSED

@yashh ran into this issue

from twemproxy.

Eg of a sample failure

[Sat Feb 9 16:20:43 2013] nc.c:177 nutcracker-0.2.2 started on pid 15339
[Sat Feb 9 16:20:43 2013] nc.c:181 run, rabbit run / dig that hole, forget the sun / and when at last the work is done / don't sit down / it's time to dig another one
[Sat Feb 9 16:20:43 2013] nc_util.c:481 address resolution of node '"abc' service '11211' failed: Name or service not known
[Sat Feb 9 16:20:43 2013] nc_conf.c:490 conf: directive "servers" has an invalid value
[Sat Feb 9 16:20:43 2013] nc.c:187 done, rabbit done

from twemproxy.

There's another issue to where there's a limit to hostname length which presents a problem. In my environment hostnames are quite long, e.g. project-staging.fl8zqq.cfg.use1.cache.amazonaws.com which results in them getting cut off.

[Tue May 5 18:39:33 2015] nc.c:168 nutcracker-0.1.16 started on pid 20063
[Tue May 5 18:39:33 2015] nc.c:172 run, rabbit run / dig that hole, forget the sun / and when at last the work is done / don't sit down / it's time to dig another one
[Tue May 5 18:39:33 2015] nc_util.c:481 address resolution of node 'project-staging.fl8zqq.cfg.use1.cache.amazon' service '11211' failed: Name or service not known
[Tue May 5 18:39:33 2015] nc_conf.c:482 conf: directive "servers" has an invalid value
[Tue May 5 18:39:33 2015] nc.c:178 done, rabbit done

from twemproxy.

fixed with this change: #355 (comment)
duplicate of issue: #355

from twemproxy.