[Pianod] New error just crept up

[Perette Barella]

Sorry for the delay, I've been on a bicycle adventure for a few weeks.

In the event of network problems, pianod stores the user credentials and retries periodically until the network comes up.  At least on OS X, it recovers correctly.  I took the ethernet offline and started up, yielding the dreaded getaddr failed:

133 Logging in to server
502 getaddr failed.

When I brought the ethernet up, on the next pianod retry (once a minute):

133 Logging in to server
133 Pandora credentials changed.
136 Privileges: user
135 Station list has changed
134 Mix has been changed

Of course, by then the start script had already completed so any subsequent commands (like picking stations or starting music) failed and didn't get run, but I was able to pick a station and start playback.  This is not ideal, but I don't have any good ideas for improving it either.

So I'll point to the Linux network libraries (getaddrinfo) and ask why isn't reflecting the network coming up and/or why it's troubled by running as 'nobody'?  Is this true of all Linuxes (Linae?) or is this a quirk on the Pi?

Perette





On 2013年07月17日, at 13:30, Peter Li wrote:

> Looking like this is actually going to be a problem for running pianod as a service that starts at boot.  Not sure why it wasn't an issue before, but I guess just as well we started looking at it.  Perette, do you have thoughts about how pianod should behave if it is instructed by the start script to log in and start playing immediately but it doesn't have network yet?