PF client dead after upgrade

TD8205

New Member
Just upgraded my client to the new version 5.0.148 using the wget and then sudo dpkg -i commands and it installed successfully. However, now nothing loads at http://192.168.1.180:30053. RPi-Monitor Avionics recognizes the new version, but says there is no connection to PF. Please help!
 

Attachments

  • Screenshot_20210218-023122-01.jpeg
    Screenshot_20210218-023122-01.jpeg
    285.9 KB · Views: 11

Lee Armstrong

Administrator
Staff member
Hello,

Thanks for reporting this. Can you give us some more information on the Pi you are using. Does anything appears in the logs at all? They should be in /var/log/pfclient/*
 

TD8205

New Member
This is on a Pi 4B with 4 GB RAM. It is running the PiAware 4.0 system image and also has ADS-B Exchange scripts installed for feeding that service. I'm relatively new to all of this so if you could give me the commands necessary to run to pull the relevant logs I'd be glad to.
 

Lee Armstrong

Administrator
Staff member
As a quick start. Did you try rebooting the pi after to see if it comes back? I’m not familiar with the monitoring tool you are using there.

The logs are all files in /var/log/pfclient. You should be able to use an SFTP client to get them off the Pi.
 

TD8205

New Member
No resolution after rebooting the Pi. I'd love to pull the appropriate logs for you, but I'm FAR from a Linux or command line expert. See my screen shot for what I mean. What command can I run to show you the relevant logs?

Screenshot_20210219-022820-01.jpeg
 

nsmits

New Member
I think I'm experiencing the same issue; only in my case with a new installation.

[email protected]:~ $ sudo systemctl status pfclient.service
pfclient.service - LSB: planefinder.net ads-b decoder
Loaded: loaded (/etc/init.d/pfclient; generated)
Active: active (exited) since Thu 2021-02-18 22:50:21 CET; 9h ago
Docs: man:systemd-sysv-generator(8)
Process: 481 ExecStart=/etc/init.d/pfclient start (code=exited, status=0/SUCCESS)

feb 18 22:50:20 flightradar systemd[1]: Starting LSB: planefinder.net ads-b decoder...
feb 18 22:50:21 flightradar pfclient[481]: Starting pfclient: pfclient.
feb 18 22:50:21 flightradar systemd[1]: Started LSB: planefinder.net ads-b decoder.


[email protected]:/var/log/pfclient $ tail -30 pfclient-log_1613676276.log
2021-02-18 21:01:38.424200 [V] NTP sync succeeded with settings:
2021-02-18 21:01:38.424262 [V] Stratum: 2
2021-02-18 21:01:38.424289 [V] System clock time: 1613682098.4242
2021-02-18 21:01:38.424310 [V] Corrected clock time: 1613682098.4159
2021-02-18 21:01:38.424329 [V] NTP offset: -0.0083s
2021-02-18 21:50:21.544942 [-] pfclient (5.0.148 armhf) started with the following options:
2021-02-18 21:50:21.559142 [-] connection_type = 1
2021-02-18 21:50:21.559185 [-] tcp_address = 127.0.0.1
2021-02-18 21:50:21.559203 [-] tcp_port = 30005
2021-02-18 21:50:21.559220 [-] data_format = 1
2021-02-18 21:50:21.559235 [-] aircraft_timeout = 30
2021-02-18 21:50:21.559251 [-] select_timeout = 10
2021-02-18 21:50:21.559266 [-] web_server_port = 30053
2021-02-18 21:50:21.559290 [-] user_latitude = ***
2021-02-18 21:50:21.559307 [-] user_longitude = ****
2021-02-18 21:50:21.560326 [V] Failed to open connection to socket: Connection refused (errno: 111)
2021-02-18 21:50:21.560415 [-] Failed TCP connection to all provided addresses for: 127.0.0.1:30005
2021-02-18 21:50:21.571413 [V] Performing NTP sync (3.planefinder.pool.ntp.org)...
2021-02-18 21:50:21.573627 [V] Failed to resolve remote socket address 3.planefinder.pool.ntp.org 123: Temporary failure in name resolution (errno: -3)
2021-02-18 21:50:21.573684 [V] Failed to connect to NTP pool, retrying...
2021-02-18 21:50:22.573819 [V] Performing NTP sync (0.planefinder.pool.ntp.org)...
2021-02-18 21:50:22.574320 [V] Failed to resolve remote socket address 0.planefinder.pool.ntp.org 123: Temporary failure in name resolution (errno: -3)
2021-02-18 21:50:22.574352 [V] Failed to connect to NTP pool, retrying...
2021-02-18 21:50:23.574451 [V] Performing NTP sync (1.planefinder.pool.ntp.org)...
2021-02-18 21:50:23.574867 [V] Failed to resolve remote socket address 1.planefinder.pool.ntp.org 123: Temporary failure in name resolution (errno: -3)
2021-02-18 21:50:23.574893 [V] Failed to connect to NTP pool, retrying...
2021-02-18 21:50:24.575018 [V] Performing NTP sync (2.planefinder.pool.ntp.org)...
2021-02-18 21:50:24.575562 [V] Failed to resolve remote socket address 2.planefinder.pool.ntp.org 123: Temporary failure in name resolution (errno: -3)
2021-02-18 21:50:24.575597 [V] Failed to connect to NTP pool, retrying...
2021-02-18 21:50:26.560803 [-] TCP connection established: 127.0.0.1:30005
 

Nigelr

New Member
I've had the same problem updating two RPi3bs. It did run for about one minute (viewed the new map display) and then stops. Tried sudo systemctl restart pfclient and that gets it running again but only for ca. 60 secs. I've checked the log and it looks fine although no lines showing that any data is being sent. I've contacted Support so hopefully I will hear back soon.
 

Lee Armstrong

Administrator
Staff member
Also something worth trying (with the client service stopped).

Run the client manually. Am hoping it will report more data. Use the following command on the Pi.

Code:
pfclient -z /etc/pfclient-config.json
 

Nigelr

New Member
Hi Lee

I've reinstalled version 4.2.70 and that is running fine. Isn't that the previous version?

My PF Radar Receiver also attempted an upgrade but that failed too...see attached message from the log

Many thanks

Nigel

PF client update.jpg
 

nsmits

New Member
In my case I’m getting a segmentation fault. It running for +- 30 seconds and then it’s giving that message.
 

Lee Armstrong

Administrator
Staff member
Yes I was trying to ascertain if 4.2.70 had the issue on that Pi.

We've not had an issue with this on PF Radar units, I have just sent an upgrade for your PFR to 5.0.148.

I have just done a fresh build of the .deb for 5.0.148 so would be good if you could redownload that on the Pi, try running manually and we can try and see what is causing the segfault.

The command to run manually is:

Code:
pfclient -z /etc/pfclient-config.json
 

nsmits

New Member
I’ve reinstalled pfclient and run it with gdb
Code:
[New Thread 0xb35ff460 (LWP 23890)]
[Thread 0xb35ff460 (LWP 23890) exited]
[New Thread 0xb35ff460 (LWP 23983)]

Thread 32 "pfclient" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb35ff460 (LWP 23983)]
dictionary_get (d=0x0, [email protected]=0xef09c "flightpaths", [email protected]=0x0)
    at /var/pfclient/PFClient-NG/pfclient/pfclient/vendor/iniparser/dictionary.c:185
185     /var/pfclient/PFClient-NG/pfclient/pfclient/vendor/iniparser/dictionary.c: Bestand of map bestaat niet.
(gdb)
 

Lee Armstrong

Administrator
Staff member
Ah perfect thank you ever so much @nsmits , I was just documenting the steps actually to get someone to try running it with GDB!

For now we have rolled back the website to 4.2.70 but that really helps. If I get a build next week ready are you willing to test it out for us?

Thanks!

Lee
 

Lee Armstrong

Administrator
Staff member
@nsmits Are you able to get a backtrace with GDB? Should be a simple case of typing "bt" and hitting return.

Sorry if I am teaching you to suck eggs there!
 

Nigelr

New Member
Thanks Lee

PF Radar Client is now updated and working fine

For the Pi..how do you stop the client before issuing the command to run manually?

Thanks
 

Lee Armstrong

Administrator
Staff member
Also what would be really handy is a copy of your config. Don't post it here as it contains sensitive information.

The config file is located at /etc/pfclient-config.json

Email it over to [email protected] and mark it for my attention and it will find it's way to me!
 

Lee Armstrong

Administrator
Staff member
Thanks Lee

PF Radar Client is now updated and working fine

For the Pi..how do you stop the client before issuing the command to run manually?

Thanks
Thanks Nigel, I think we have a good lead actually with some debug information. Run 4.2.70 for now and I might get you to test an updated 5.0 version next week if that is ok as I know your Pi had issues with it too?
 
Top