Page 6 of 6 FirstFirst ... 456
Results 51 to 54 of 54

Thread: strange radar down

  1. #51
    Flight attendant
    Join Date
    Mar 2012
    Posts
    71
    Quote Originally Posted by costyn View Post
    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?
    Code:
    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 ...

  2. #52
    Passenger
    Join Date
    Dec 2015
    Posts
    2
    Quote Originally Posted by Kemistry View Post
    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.

  3. #53
    Passenger
    Join Date
    Feb 2015
    Location
    SSOL
    Posts
    44
    Quote Originally Posted by Kemistry View Post
    If file ownership doesn't matter, why do these error messages turn up in the syslog?
    Code:
    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.

  4. #54
    Passenger
    Join Date
    Feb 2017
    Posts
    3
    I had same issue - performing
    Code:
    sudo apt-get upgrade
    sudo apt-get update
    have solved the issue.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •