Announcement

Collapse
No announcement yet.

strange radar down

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • attigliano
    replied
    Linux is new to me, so I may say something stupid
    Is there somewhere in RaPi OS where you should grant a update script?
    I had read that I could make a update by running: apt-get update and then apt-get upgrade this didn't work.
    Then I run: sudo apt-get update and then sudo apt-get upgrade now my RaPi get updated and it had worked since
    Last edited by attigliano; 2015-12-18, 06:59.

    Leave a comment:


  • patrick1501
    replied
    Originally posted by vinnyspb View Post
    Most likely there is something wrong with auto-update script, that is scheduled to run at 07:00 local time (RPi system timezone).

    Just double checked it on Raspbian OS and it works fine, so that may be related to some other OS or different configurations.

    Could you please run this update script:



    and post the output?
    Hi,

    I had this crash during 3 consecutive days, and updated now by launching the command "sudo /usr/lib/fr24/fr24feed_updater.sh", which brought me from version 1.0.14-11 to version 1.0.16-7. I have kept the output, if you need it I can post it.
    I guess there is indeed a problem with the auto-update, as there are surely intermediate versions between the 2 mentioned above...

    Leave a comment:


  • Erik12345
    replied
    Same problem over here the last 2 days. I guess something goes wrong with the update. If i do an manual sudo /usr/lib/fr24/fr24feed_updater.sh it works.

    Checking the apt history says:

    pi@pi3 /var/log/apt $ cat history.log

    Start-Date: 2015-12-16 07:01:15
    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:16

    Start-Date: 2015-12-17 07:01:15
    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:16

    Start-Date: 2015-12-17 19:51:44
    Commandline: apt-get install -y fr24feed
    Upgrade: fr24feed:armhf (1.0.14-11, 1.0.16-7)
    End-Date: 2015-12-17 19:51:49

    Looking at the crontab entry it says:
    0 7 * * * root /usr/lib/fr24/fr24feed_updater.sh

    Should the "root" in this line not been replaced by "sudo"??

    Leave a comment:


  • pellonet
    replied
    Originally posted by vinnyspb View Post
    Thanks for the output.

    Your's one looks good to me. You don't need to manually start/stop fr24feed before running this script, it is intended to do it automatically if upgrade is required.
    In your case fr24feed is already up to date, it would be nice to see someone else's output who has issues and haven't updated yet.
    As you see I'm on 1.0.14-11 & the script fails as follows:



    Reading package lists... Done
    Installed version: 1.0.14-11
    Latest available: 1.0.16-7
    Upgrading fr24feed...
    Waiting for fr24feed to stop completely...
    Failed to get properties: Connection reset by peer
    Failed to get properties: Connection timed out
    Failed to get properties: Connection timed out
    Failed to get properties: Connection timed out
    Failed to stop fr24feed.service: Connection timed out
    Failed to get load state of fr24feed.service: Connection timed out
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages will be upgraded:
    fr24feed
    1 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
    Need to get 0 B/433 kB of archives.
    After this operation, 0 B of additional disk space will be used.
    (Reading database ... 143866 files and directories currently installed.)
    Preparing to unpack .../fr24feed_1.0.16-7_armhf.deb ...
    Failed to execute operation: Activation of org.freedesktop.systemd1 timed out
    [....] Stopping fr24feed (via systemctl): fr24feed.serviceFailed to stop fr24feed.service: Activation of org.freedesktop.systemd1 timed out
    Failed to get load state of fr24feed.service: Activation of org.freedesktop.systemd1 timed out
    failed!
    dpkg: error processing archive /var/cache/apt/archives/fr24feed_1.0.16-7_armhf.deb (--unpack):
    subprocess new pre-installation script returned error exit status 1
    Failed to execute operation: Activation of org.freedesktop.systemd1 timed out
    Errors were encountered while processing:
    /var/cache/apt/archives/fr24feed_1.0.16-7_armhf.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    Failed to restart fr24feed.service: Connection timed out
    pi@RPHS ~ $

    Leave a comment:


  • pellonet
    replied
    Originally posted by vinnyspb View Post
    Most likely there is something wrong with auto-update script, that is scheduled to run at 07:00 local time (RPi system timezone).

    Just double checked it on Raspbian OS and it works fine, so that may be related to some other OS or different configurations.

    Could you please run this update script:



    and post the output?
    Ran the script & this is the truncated output:

    Reading package lists... Done
    Installed version: 1.0.14-11
    Latest available: 1.0.16-7
    Upgrading fr24feed...
    Waiting for fr24feed to stop completely...
    Failed to get properties: Connection reset by peer
    Failed to get properties: Connection timed out
    Failed to get properties: Connection timed out
    Failed to get properties: Connection timed out
    Failed to stop fr24feed.service: Connection timed out
    Failed to get load state of fr24feed.service: Connection timed out
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages will be upgraded:
    fr24feed
    1 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
    Need to get 0 B/433 kB of archives.
    After this operation, 0 B of additional disk space will be used.
    (Reading database ... 143866 files and directories currently installed.)
    Preparing to unpack .../fr24feed_1.0.16-7_armhf.deb ...
    Failed to execute operation: Activation of org.freedesktop.systemd1 timed out
    [....] Stopping fr24feed (via systemctl): fr24feed.serviceFailed to stop fr24feed.service: Activation of org.freedesktop.systemd1 timed out
    Failed to get load state of fr24feed.service: Activation of org.freedesktop.systemd1 timed out
    failed!
    dpkg: error processing archive /var/cache/apt/archives/fr24feed_1.0.16-7_armhf.deb (--unpack):
    subprocess new pre-installation script returned error exit status 1
    Failed to execute operation: Activation of org.freedesktop.systemd1 timed out
    Errors were encountered while processing:
    /var/cache/apt/archives/fr24feed_1.0.16-7_armhf.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    Failed to restart fr24feed.service: Connection timed out
    pi@RPHS ~ $

    Leave a comment:


  • mrcarlos
    replied
    after last update yesterday, today all was working good

    Sent from my SM-N910F using Tapatalk

    Leave a comment:


  • Dundee
    replied
    After some brain-storm, I think now the problem is feeder who did not upgrade the fr24feed to latest 1.0.16-7 starting this week causing radar shutdown at 7:00am local time.
    As I just read my check log, no error is found in today's morning after I upgrade to 1.0.16-7 manually last night.

    And maybe it's a bug that the auto-update script of feeder getting older version like 1.0.14 or before doesn't work and causing error.
    Last edited by Dundee; 2015-12-17, 14:44.

    Leave a comment:


  • henkverhaar
    replied
    FYI, I had updated manually this morning, after finding fr24feed stopped for the third time in as many days - by doing a manual 'apt-get upgrade' run...

    Let's see whether this version is still running normally at 7:01 local time tomorrow morning ;-)

    Leave a comment:


  • Guest
    Guest replied
    Thanks for the output.

    Your's one looks good to me. You don't need to manually start/stop fr24feed before running this script, it is intended to do it automatically if upgrade is required.
    In your case fr24feed is already up to date, it would be nice to see someone else's output who has issues and haven't updated yet.

    Leave a comment:


  • henkverhaar
    replied
    Anyway, here's the output (with the feeder shut down manually):

    pi@raspberrypi ~ $ sudo /usr/lib/fr24/fr24feed_updater.sh
    Hit http://raspberrypi.collabora.com wheezy Release.gpg
    Get:1 http://mirrordirector.raspbian.org wheezy Release.gpg [490 B]
    Hit http://raspberrypi.collabora.com wheezy Release
    Get:2 http://mirrordirector.raspbian.org wheezy Release [14.4 kB]
    Hit http://archive.raspberrypi.org wheezy Release.gpg
    Hit http://raspberrypi.collabora.com wheezy/rpi armhf Packages
    Get:3 http://mirrordirector.raspbian.org wheezy/main armhf Packages [6908 kB]
    Hit http://archive.raspberrypi.org wheezy Release
    Hit http://repo.feed.flightradar24.com flightradar24 Release.gpg
    Hit http://archive.raspberrypi.org wheezy/main armhf Packages
    Hit http://repo.feed.flightradar24.com flightradar24 Release
    Ign http://raspberrypi.collabora.com wheezy/rpi Translation-en
    Ign http://archive.raspberrypi.org wheezy/main Translation-en
    Hit http://repo.feed.flightradar24.com flightradar24/raspberrypi-stable armhf Packages
    Ign http://repo.feed.flightradar24.com flightradar24/raspberrypi-stable Translation-en
    Get:4 http://mirrordirector.raspbian.org wheezy/contrib armhf Packages [23.6 kB]
    Get:5 http://mirrordirector.raspbian.org wheezy/non-free armhf Packages [49.3 kB]
    Get:6 http://mirrordirector.raspbian.org wheezy/rpi armhf Packages [592 B]
    Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en
    Ign http://mirrordirector.raspbian.org wheezy/main Translation-en
    Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en
    Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en
    Fetched 6997 kB in 15s (443 kB/s)
    Reading package lists... Done
    Installed version: 1.0.16-7
    Latest available: 1.0.16-7
    Latest version is already installed

    Leave a comment:


  • henkverhaar
    replied
    bot bait... sorry, cannot post the output due do not having more than 4 posts already - this one should up my post count enough to be able to do that...

    Leave a comment:


  • henkverhaar
    replied
    My Pi runs on Raspbian "under" NOOBS. Will run the update script. I assume that I have to manually shutdown the feeder (service) before running the script, right?

    Leave a comment:


  • Guest
    Guest replied
    Most likely there is something wrong with auto-update script, that is scheduled to run at 07:00 local time (RPi system timezone).

    Just double checked it on Raspbian OS and it works fine, so that may be related to some other OS or different configurations.

    Could you please run this update script:

    sudo /usr/lib/fr24/fr24feed_updater.sh
    and post the output?

    Leave a comment:


  • Dundee
    replied
    My station is still 24/7 because I have written a script to check fr24feed every 5 minutes.

    It's provided that fr24feed will be terminated at the morning after the releasing of 1.0.16-7 according to the log generated by script.

    fr24feed is down at Tue 15 Dec 07:05:01 HKT 2015, restarting...
    fr24feed is down at Wed 16 Dec 07:05:01 HKT 2015, restarting...
    Last edited by Dundee; 2015-12-17, 13:09.

    Leave a comment:


  • henkverhaar
    replied
    The only message I have around that time in /var/log/messages (in fact the only messages I have in /var/log/messages, apart from a whole slew of messages associated with a manual reboot on Dec 16) is this:

    06:25:04 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1827" x-info="(link removed due to forum posting restrictions - the link is the default one for rsyslog messages...)"] rsyslogd was HUPed

    Unfortunately, I no longer have the fr24feed log for that period...

    Leave a comment:

Working...
X