[Pianod] New error just crept up

Peter Li chinasaurli at gmail.com
Tue Jul 16 16:27:07 PDT 2013


Okay, 148 seems to work for me.  But from looking at the code I would 
guess that you are trying to have pianod start playing right when the 
computer boots?

Ultimately this seems to trace down to WaitressConnect, where 
WAITRESS_RET_GETADDR_ERR gets returned if getaddrinfo fails.  In my 
experience this usually happens because getaddrinfo was run before the 
network stack was ready, which happens if you try to run the program 
before the network services have started.  I don't understand why this 
would have cropped up now and not before though.  It was an issue in 
wsgw previously, but there it was easy to have the program try 
getaddrinfo again later.

Are you trying to run pianod right at boot?
IMO libwaitress should probably be changed to report the actual 
getaddrinfo error code?  If getaddrinfo fails due to the network stack 
not being ready then it typically gives EAI_NONAME.
P


On 07/16/2013 12:37 PM, Jimmy Pop wrote:
> This may or may not be helpful,
> in waitress.c
>
> const char *WaitressErrorToStr (WaitressReturn_t wRet) {
> switch (wRet) {
> ........
> case WAITRESS_RET_GETADDR_ERR:
> return "getaddr failed.";
> break;
>
> it gets called from
>
> *wRet = BarPianoHttpRequest (&app->waith, &req);
> if (*wRet != WAITRESS_RET_OK) {
> send_response_code(app->service, E_NETWORK_FAILURE, WaitressErrorToStr 
> (*wRet));
> if (req.responseData != NULL) {
> free (req.responseData);
> }
> PianoDestroyRequest (&req);
> return 0;
> }
>
> in support.c
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deviousfish.com/pipermail/pianod-deviousfish.com/attachments/20130716/5d9d6f04/attachment-0003.htm>


More information about the Pianod mailing list