Package Details: flightradar24 1.0.48-3

Git Clone URL: https://aur.archlinux.org/flightradar24.git (read-only, click to copy)
Package Base: flightradar24
Description: Feeder software for Flightradar24.com (fr24feed)
Upstream URL: https://www.flightradar24.com/share-your-data
Licenses: custom
Submitter: yuvadm
Maintainer: rsa
Last Packager: rsa
Votes: 10
Popularity: 0.070045
First Submitted: 2014-03-13 15:31 (UTC)
Last Updated: 2024-07-29 01:30 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

meijin commented on 2024-11-03 07:03 (UTC)

any updates?

rsa commented on 2024-09-09 14:49 (UTC)

@meijin I was traveling when you submitted the last messages, sorry for the delay. I'm trying to fix this issue locally and will publish an update as soon as I figure out. Thanks!

meijin commented on 2024-08-17 09:35 (UTC)

@rsa any update on that problem?

meijin commented on 2024-08-01 07:14 (UTC)

@rsa the package is unusable for now and I had to downgrade to the -2 version

meijin commented on 2024-07-29 03:42 (UTC)

After your latest changes, it fails to read the config file:

Apr 25 17:44:07 alarm fr24feed[135453]: fr24key is not set or is empty

But the key is in the /etc/fr24feed.ini file

rsa commented on 2024-07-29 01:32 (UTC) (edited on 2024-07-29 01:34 (UTC) by rsa)

In 1.0.48-3, I tightened the systemd sandbox as much as possible (you can check with systemd-analyze security fr24feed.service), disallowing access I noticed the software doesn't need to function. Please let me know if something stops working for you.

rsa commented on 2024-07-26 10:28 (UTC)

The error below has been fixed in 1.0.48-2 by means of moving the descriptor file from /dev/shm (where it had no write access) to /run/flightradar24

rsa commented on 2024-07-22 22:53 (UTC)

The binary can't run as a non-root user, it starts to spill the following message in the logs:

write_locked - missing monitor file pointer

Longer snippet of the logs:

Jul 23 00:46:34 kraken fr24feed[62837]: [time][i]Synchronizing time via NTP
Jul 23 00:46:34 kraken fr24feed[62837]: [time][i]Time synchronized correctly, offset -0.024 seconds
Jul 23 00:46:34 kraken fr24feed[62837]: [main][i]Feed Network client started
Jul 23 00:46:34 kraken fr24feed[62837]: [feed][i]Downloading configuration
Jul 23 00:46:34 kraken fr24feed[62837]: [feed][d]Fetching configuration
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][i]configuring decoder
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][c]Max range AIR: 300.0nm
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][c]Max range GND: 80.0nm
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][i]configuration changed
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][i]defined 3 servers
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][c]Timestamps: optional
Jul 23 00:46:35 kraken fr24feed[62837]: [I] Stopping ReceiverACSender threads for feed
Jul 23 00:46:35 kraken fr24feed[62837]: [I] Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218>
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][n]ESSB548@185.218.24.22:8099/UDP
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][n]connecting
Jul 23 00:46:35 kraken fr24feed[62837]: [I] Network thread connecting to 185.218.24.22:8099 for feed ESSB548
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [I] [stats]Stats thread started
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][n]connected via UDP (fd 19)
Jul 23 00:46:35 kraken fr24feed[62837]: [feed][n]working
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:35 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:37 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:39 kraken fr24feed[62837]: [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090  --raw --m>
Jul 23 00:46:39 kraken fr24feed[62837]: [reader][i]Connected to the receiver, configuring
Jul 23 00:46:39 kraken fr24feed[62837]: [reader][i]Configured, processing messages
Jul 23 00:46:39 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:39 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:39 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:39 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:39 kraken fr24feed[62837]: [E] write_locked - missing monitor file pointer
Jul 23 00:46:39 kraken fr24feed[62837]: [reader][i]Connection terminated

It works without this error message if I remove the User= entry in the service file. Tested on different machines, had the same issue.

jimmyxu commented on 2024-02-15 02:22 (UTC)

I've added a service file and listed dump978 in optdepends.

1 2 3 4 5 Next › Last »