Welcome to the Cumulus Support forum.

Latest Cumulus MX release v3.4.0 (build 3064) - 19 February 2020.
    Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014

    See the Wiki for downloading either version.

    LOG ERROR

    Discussion of version 3 of Cumulus, which runs on Windows, Linux, and OS X. All Cumulus MX queries in here, please.

    Moderator: mcrossley

    Post Reply
    andrea_iw2ntf
    Posts: 7
    Joined: Fri 17 Aug 2018 8:11 pm
    Weather Station: Davis VP2
    Operating System: Raspbian
    Location: Gaggiano - MI - ITA
    Contact:

    LOG ERROR

    Post by andrea_iw2ntf » Mon 12 Aug 2019 4:24 pm

    Hello everyone!

    I created a new image, with the new Raspy 10 BUSTER, however it seems there is a problem in the management of the log.
    Version: Raspbian Buster Lite V. 20/06/2019 (and 10/07/2019) & Cumulus MX Release 3.0.0 b3050
    This involves problems with graphics, and NOAA file management.

    When the raspberry is restarted, a NUL line is created.
    The line is very long, after the NUL series a data string appears. But cumulus goes wrong. Test done with raspy Pi0W and Pi2b.

    This happens to me because every night, I restart the raspberry. Or if I restart it to do tests.

    Pay attention that before the restart, the command is launched

    sudo /home/pi/CumulusMX/cumulusmx.sh -q
    sudo shutdown -r now


    this to avoid a sudden closure of cumulus.

    What do you suggest ????

    Thank you!

    andrea iw2ntf
    You do not have the required permissions to view the files attached to this post.

    ExperiMentor
    Posts: 133
    Joined: Tue 24 Nov 2015 11:30 pm
    Weather Station: Fine Offset & Davis Vantage Vue
    Operating System: Windows 10; Raspbian Buster
    Location: Switzerland

    Re: LOG ERROR

    Post by ExperiMentor » Sat 24 Aug 2019 6:26 pm

    I'm using a similar setup - RPi Zero W, CumulusMX and a scheduled daily reboot at 0253

    I recently changed From Stretch to Buster, and from an earlier CumulusMX build to 3050,

    I have no such similar problem. In these examples, the RPi rebooted between the lines shown
    With the old system:

    Code: Select all

    07/08/19,02:51,18.4,78,14.5,0.0,0.0,0,0.0,0.0,1026.7,954.3,26.6,45,0.0,18.4,18.4,0.0,0,0.00,0.00,19.8,0,0.0,0,0.0,0.0
    07/08/19,03:01,18.5,79,14.8,0.0,0.7,0,0.0,0.0,1026.5,954.3,26.6,45,0.7,18.5,18.5,0.0,0,0.00,0.00,20.0,0,0.0,270,0.0,0.0
    
    and with the new:

    Code: Select all

    23/08/19,02:50,13.6,94,12.7,0.2,1.6,357,0.0,0.0,1039.1,1021.5,24.9,52,0.0,13.6,13.6,0.0,0,0.00,0.00,14.4,0,0.0,0,0.0,0.0
    23/08/19,03:00,13.7,94,12.8,0.0,0.0,0,0.0,0.0,1039.0,1021.5,24.9,51,0.0,13.7,13.7,0.0,0,0.00,0.00,14.5,0,0.0,0,0.0,0.0
    
    I don't know what your shutdown script (cumulusmx.sh) contains. It's not part of the distribution - so must be something you've added and may be the cause of your problem?

    All I do is run the standard reboot command

    Code: Select all

    sudo reboot
    from my crontab without stopping CumulusMX first. I believe this properly closes all running programs (or at least it tells them to close - but will still reboot if something has crashed).

    Post Reply