[Pianod] New error just crept up

[Jimmy Pop]

I am running 148, also as a test, I tested pianobar, and it works
perfectly, so the DNS resolution of pandora servers is working.
Also I issued a tls key update before trying to log in, and pianobar
is using the same tls key.

On Jul 16, 2013, at 8:42 AM, Peter Li <chinasaurli at gmail.com> wrote:

> I replied from my phone, may take a while to get through.  Wasn't that helpful anyway...
>
> I'm a bit confused; would have expected an error from getaddrinfo not getaddr.  Also this sounds like an E_AGAIN error message but in my experience getaddrinfo throws a different error if it is trying to resolve names before the network stack is ready.  So not sure why this would crop up.
>
> I'll look into it later today.  What version of the code are you running?
> Perette will be more helpful.
> P
>
>
>
> On 07/16/2013 08:10 AM, Jimmy Pop wrote:
>> I have been using pianod for a while now, and now all of the sudden I have this error output on the control port
>>
>> 133 Logging in to server
>> 502 getaddr failed.
>> 410 Temporary failure, future completion status unknown: getaddr failed
>> What would be causing this error?
>
> _______________________________________________
> Pianod mailing list
> Pianod at lists.deviousfish.com
> http://lists.deviousfish.com/listinfo.cgi/pianod-deviousfish.com