I’m almost sure that error is no related to your problems.
This is my output:
PiAware master process (piaware) is running with pid 685.
PiAware ADS-B client (faup1090) is running with pid 7661.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is running with pid 28699.
Local ADS-B receiver (dump1090-fa) is running with pid 7628.
dump1090-fa (pid 7628) is listening for connections on port 30005.
no program appears to be listening for connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
got 'couldn't open socket: connection refused'
dump1090 is producing data on localhost:30005.
Your feeder ID is
Could it be you can’t claim the receiver because it’s already associated with your account?
It will remember the feeder-id when upgrading to a new version.
I was wondering if any one had figured out this issue? I had to replace my router so my wireless name and password changed. I was able to get my piaware to piaware-config setup correctly, but when I restarted piaware I got the same status message:
pi@piaware:~ $ piaware-status
PiAware master process (piaware) is running with pid 761.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090) is not running.
no program appears to be listening for ES connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is connected to FlightAware.
got ‘couldn’t open socket: connection refused’
dump1090 is NOT producing data on localhost:30005.
I would appreciate any information some one could supply.