strange radar down

[piotrva]

I had same issue - performing

sudo apt-get upgrade
sudo apt-get update

have solved the issue.

[spotter.ssol]

If file ownership doesn't matter, why do these error messages turn up in the syslog?

Dec 19 12:20:01 <snip> cron[475]: (*system*fr24feed_updater) WRONG FILE OWNER (/etc/cron.d/fr24feed_updater)
Dec 19 12:21:01 <snip> cron[475]: (*system*fr24feed_updater) WRONG FILE OWNER (/etc/cron.d/fr24feed_updater)

After changed the ownership of fr24feed_updater to root, these messages went away.
Google WRONG FILE OWNER with cron, and there's stuff about trying to stop security risks.
It all might depend on your underlying distro.
We'll have to wait for the next auto update to see ...

Same here. This error occurs because the script file "/etc/cron.d/fr24feed_updater" have ownership to pii.
But inside it calls for the script "/usr/lib/fr24/fr24feed_updater.sh" as root user.
AFAIK, an unprivileged user cannot run a script with root privilegies without "sudoing".
To correct this, I've changed the ownership of file "/etc/cron.d/fr24feed_updater" to root. Problem solved here.

[costyn]

If file ownership doesn't matter, why do these error messages turn up in the syslog?

Ok, apologies, I stand corrected. I have many years of Linux sysadmin experience, but I guess I never ran across this, or it might be a new addition to particular distributions for extra security.

[Kemistry]

Yea I noted the same thing in my apt history.log.

It's strange, because it's says dpkg encountered an error, but when I go look in /var/log/dpkg.log, it only shows the logs from when I manually (successfully) did an apt-get install (2015-12-02) or apt-get upgrade (2015-12-24):


I've edited /usr/lib/fr24/fr24feed_updater.sh to make apt-get install more verbose. Perhaps we'll learn more about it then. Although it will only install once there's a new version of fr24feed available.

It shouldn't matter who the owner of the script or the cron.d entry is. Since cron is started by root it will run anyways.

If file ownership doesn't matter, why do these error messages turn up in the syslog?

Dec 19 12:20:01 <snip> cron[475]: (*system*fr24feed_updater) WRONG FILE OWNER (/etc/cron.d/fr24feed_updater)
Dec 19 12:21:01 <snip> cron[475]: (*system*fr24feed_updater) WRONG FILE OWNER (/etc/cron.d/fr24feed_updater)

After changed the ownership of fr24feed_updater to root, these messages went away.
Google WRONG FILE OWNER with cron, and there's stuff about trying to stop security risks.
It all might depend on your underlying distro.
We'll have to wait for the next auto update to see ...

[costyn]

Yea I noted the same thing in my apt history.log.

It's strange, because it's says dpkg encountered an error, but when I go look in /var/log/dpkg.log, it only shows the logs from when I manually (successfully) did an apt-get install (2015-12-02) or apt-get upgrade (2015-12-24):

2015-12-02 01:41:35 install fr24feed:armhf <none> 1.0.14-11
2015-12-02 01:41:35 status half-installed fr24feed:armhf 1.0.14-11
2015-12-02 01:41:36 status unpacked fr24feed:armhf 1.0.14-11
2015-12-02 01:41:36 status unpacked fr24feed:armhf 1.0.14-11
2015-12-02 01:41:37 configure fr24feed:armhf 1.0.14-11 <none>
2015-12-02 01:41:37 status unpacked fr24feed:armhf 1.0.14-11
2015-12-02 01:41:37 status unpacked fr24feed:armhf 1.0.14-11
2015-12-02 01:41:37 status unpacked fr24feed:armhf 1.0.14-11
2015-12-02 01:41:37 status half-configured fr24feed:armhf 1.0.14-11
2015-12-02 01:41:39 status installed fr24feed:armhf 1.0.14-11
2015-12-24 15:00:46 upgrade fr24feed:armhf 1.0.14-11 1.0.16-7
2015-12-24 15:00:46 status half-configured fr24feed:armhf 1.0.14-11
2015-12-24 15:00:46 status unpacked fr24feed:armhf 1.0.14-11
2015-12-24 15:00:46 status half-installed fr24feed:armhf 1.0.14-11
2015-12-24 15:00:47 status half-installed fr24feed:armhf 1.0.14-11
2015-12-24 15:00:50 status unpacked fr24feed:armhf 1.0.16-7
2015-12-24 15:00:50 status unpacked fr24feed:armhf 1.0.16-7
2015-12-24 15:00:51 configure fr24feed:armhf 1.0.16-7 <none>
2015-12-24 15:00:51 status unpacked fr24feed:armhf 1.0.16-7
2015-12-24 15:00:51 status unpacked fr24feed:armhf 1.0.16-7
2015-12-24 15:00:51 status unpacked fr24feed:armhf 1.0.16-7
2015-12-24 15:00:51 status half-configured fr24feed:armhf 1.0.16-7
2015-12-24 15:00:52 status installed fr24feed:armhf 1.0.16-7

I've edited /usr/lib/fr24/fr24feed_updater.sh to make apt-get install more verbose. Perhaps we'll learn more about it then. Although it will only install once there's a new version of fr24feed available.

It shouldn't matter who the owner of the script or the cron.d entry is. Since cron is started by root it will run anyways.

[atairlines]

sudo apt-get update & sudo apt-get upgrade - as suggested by Pellonet earlier did it for me. No problem this morning. Probably not a permanent solution, but counting on FR24 to come up with something.

The sudo apt-get update & sudo apt-get upgrade worked for me as well. Did not stop last 2 mornings...

[Kpin]

Well that explains why my RPi (T-YSWG2) has been down since the 14th! I didn't notice until I came across this topic, running a whole system update (fingers crossed no issues arise, will not have time to fix it).

sudo apt-get update & sudo apt-get upgrade - as suggested by Pellonet earlier did it for me. No problem this morning. Probably not a permanent solution, but counting on FR24 to come up with something.

[atairlines]

Thanks atairlines.
Can you please confirm that for you BOTH /etc/cron.d/fr24feed_updater AND /usr/lib/fr24/fr24feed_updater.sh are owned by root and not by pi?

I noticed that after I run the update/upgrade, the onwer of both /etc/cron.d/fr24feed_updater AND /usr/lib/fr24/fr24feed_updater.sh became pi... I changed to root already.

[YSWG]

Well that explains why my RPi (T-YSWG2) has been down since the 14th! I didn't notice until I came across this topic, running a whole system update (fingers crossed no issues arise, will not have time to fix it).

[pellonet]

Thanks atairlines.
Can you please confirm that for you BOTH /etc/cron.d/fr24feed_updater AND /usr/lib/fr24/fr24feed_updater.sh are owned by root and not by pi?

In my previously failed auto-updates which I cured with a manual update/upgrade:

/etc/cron.d/fr24feed_updater - owned by pi
/usr/lib/fr24/fr24feed_updater.sh - owned by pi

Last login: Sat Dec 19 02:44:13 2015 from 192.168.1.66
pi@RPHS ~ $ ls -l /etc/cron.d
total 4
-rw-r--r-- 1 pi pi 50 Dec 14 08:17 fr24feed_updater
pi@RPHS ~ $ ls -l /usr/lib/fr24
total 248
-rwxr-xr-x 1 pi pi 161689 Dec 14 13:15 dump1090
-rwxr-xr-x 1 pi pi    819 Dec 14 08:17 fr24feed_updater.sh
lrwxrwxrwx 1 pi pi     14 Dec 14 13:15 librtlsdr.so -> librtlsdr.so.0
lrwxrwxrwx 1 pi pi     19 Dec 14 13:15 librtlsdr.so.0 -> librtlsdr.so.0.5git
-rwxr-xr-x 1 pi pi  81340 Dec 14 13:15 librtlsdr.so.0.5git
drwxr-xr-x 3 pi pi   4096 Dec 17 18:36 public_html
pi@RPHS ~ $

[Kemistry]

Thanks atairlines.
Can you please confirm that for you BOTH /etc/cron.d/fr24feed_updater AND /usr/lib/fr24/fr24feed_updater.sh are owned by root and not by pi?

[atairlines]

This morning my RPI failed for the 5th day at 7:00 local time.
The /var/log/apt/history.log shows the following:

Start-Date: 2015-12-16 07:01:00
Commandline: apt-get install -y fr24feed
Upgrade: fr24feed:armhf (1.0.14-11, 1.0.16-7)
Error: Sub-process /usr/bin/dpkg returned an error code (2)
End-Date: 2015-12-16 07:01:07

Start-Date: 2015-12-17 07:01:13
Commandline: apt-get install -y fr24feed
Upgrade: fr24feed:armhf (1.0.14-11, 1.0.16-7)
Error: Sub-process /usr/bin/dpkg returned an error code (2)
End-Date: 2015-12-17 07:01:13

Start-Date: 2015-12-18 07:01:54
Commandline: apt-get install -y fr24feed
Upgrade: fr24feed:armhf (1.0.14-11, 1.0.16-7)
Error: Sub-process /usr/bin/dpkg returned an error code (2)
End-Date: 2015-12-18 07:01:55

Start-Date: 2015-12-19 07:01:00
Commandline: apt-get install -y fr24feed
Upgrade: fr24feed:armhf (1.0.14-11, 1.0.16-7)
Error: Sub-process /usr/bin/dpkg returned an error code (2)
End-Date: 2015-12-19 07:01:00

The owner of fr24feed_updater in my RPI was root already, so I change nothing.
I have just run the "sudo apt-get update" and "sudo apt-get upgrade" commands. Let's see what happens tomorrow morning.

[Kemistry]

Sorry Kpin, but my questions in post #38 were not proposing a solution. After I had done the manual update, it is hard to debug the problem and I was only asking others to see if they found a similar situation (ie wrong file owner in log files) that may have caused the problem. If a feeder does not understand linux it is usually better to wait till others discuss it and then till a solution is posted.
I have found a number of sites that say that /etc/cron.d scripts must be owned by root and that specifying the user as root within the crontab may not be enough (probably depends on your distro).
I think patrick1501 may have found the same crontab file ownership (pi/pi) that I found but I am unclear if he was able to correct it and fix his updating. If he has done a manual update (like me) we won’t know until the next update comes through. Without changing ownerships, the cron process still gives lots of error messages (WRONG FILE OWNER) in the syslog file which may be a symptom of cron failure for the updater.
Please only try the following if you have NOT done a manual update and are Linux confident because I am not sure that it solves the problem.
I think it is safe to try one or both of (1) changing ownership of crontab file and (2) the script file it trys to execute at 7:00 local time:

sudo chown root:root /etc/cron.d/fr24feed_updater
sudo chown root:root /usr/lib/fr24/fr24feed_updater.sh

I hope this does not cause any other problems but if you understand Linux it can be reversed if it does not work.
Good luck - please post any results.

Oops - I forgot to mention that a sudo reboot (or touch of cron.d) is necessary to activate the cron changes.

[mjrigby]

My RasPi setup suffered the same symptoms in that the FR24 feed failed every morning since 15th December at around 7:00 UTC.

Having read some of the advice in this thread, yesterday after the fourth successive daily failure I manually ran the fr24feed_updater script.

This appears to have been successful and the running version went from 1.0.14-11 to 1.0.16-7.

This morning the FR24 feed survived the 07:00 UTC period, so it appears that this has fixed the problem.

Martin

[patrick1501]

How can I know?

I got my RPi only to feed FR24 and use it for nothing else. I have no knowledge fof Linux except for the few commands in the FR2 installation guide. If things do not work, I'm lost.
The FR24 RPI combo is promoted as plug and play, and while I highly appreciate all the knowledge the is shared by users on the forum, I'm often unable to follow the lingo.

I understand that others cannot be asked to provide a beginners course to Linux, but when some specific action is suggested it would help to have the exact commands needed.

Thanks

Type the following command:

ls -al /etc/cron.d/fr24feed_updater

it will give you an output like this one:

-rw-r--r-- 1 pi pi 50 Dec 14 09:17 /etc/cron.d/fr24feed_updater

The "pi pi" info on this line means that the file is owned by the user "pi" of the group "pi".

Patrick