strange radar down

[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).

[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.

[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]

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...

[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.

[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]

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.

[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.

[piotrva]

I had same issue - performing

sudo apt-get upgrade
sudo apt-get update

have solved the issue.