System stopped updating

[tastewar]

Running meteohub 5.1b (build 263)
Connected to an Acurite weather station.
It's been running for years, with only occasional hiccups. Been running for months with 5.1b. Nothing had changed; in fact I was on vacation when it stopped updating. I really only post my weather data to Weather Underground, and noticed that it stopped getting updated around 8:10 p.m. on August 1 (https://www.wunderground.com/dashboard/ ... 08-1/daily) When I went to the web interface, it was saying "error connect socket 127.0.0.1:5555 :Connection refused" I think on the sensor page. In any case, I did replace the batteries in the sensor, and the display unit is seeing data just fine. So the wireless comm is working OK. The Weather Station page shows Acurite 1025/1035/1525 under USB HID in the Available Devices section. Under Type of Connection, USB HID is selected. But the Device field is blank (and gray), while the "select" dropdown next to it doesn't offer any choices. I'm not sure if that's how it's supposed to be or not. Sensors page shows no data for any instrument. (last signal "never")

Here's the contents of the meteohub log since the most recent reboot:

Code: Select all

hwclock: Cannot access the Hardware Clock via any known method.
hwclock: Use the --debug option to see the details of our search for an access method.
logger (16.08.2019 19:47:49): parent process received termination signal (15).
logger (16.08.2019 19:47:49): child process received termination signal (15).
logger (31.12.1969 19:00:42): System date not properly set. Please set date and time correctly before data logging can start.
logger (16.08.2019 19:49:57): data logger (version 5.1b, build 263) started.
logger (16.08.2019 19:49:58): connect station 0 (Acurite 1025 via USB HID).
logger (16.08.2019 19:55:28): child process received timeout signal (14).
logger (16.08.2019 19:55:37): disconnect station 0 (Acurite 1025): exit
logger (16.08.2019 19:55:38): data logger stopped.
logger (16.08.2019 19:55:38): data logger (version 5.1b, build 263) started.
logger (16.08.2019 19:55:39): connect station 0 (Acurite 1025 via USB HID).
logger (16.08.2019 20:01:09): child process received timeout signal (14).
logger (16.08.2019 20:01:10): disconnect station 0 (Acurite 1025): exit
logger (16.08.2019 20:01:11): data logger stopped.
logger (16.08.2019 20:01:11): data logger (version 5.1b, build 263) started.
logger (16.08.2019 20:01:13): connect station 0 (Acurite 1025 via USB HID).
logger (16.08.2019 20:06:43): child process received timeout signal (14).
logger (16.08.2019 20:06:44): disconnect station 0 (Acurite 1025): exit
logger (16.08.2019 20:06:44): data logger stopped.
logger (16.08.2019 20:06:44): data logger (version 5.1b, build 263) started.
logger (16.08.2019 20:06:46): connect station 0 (Acurite 1025 via USB HID).

I believe the hwclock events are normal for a RasPi, and the time *does* get set successfully via NTP.

Any clue what went wrong and/or how to fix it? I thought maybe the data partition was full, but the Storage section of system info shows:

Code: Select all

Media:	SDC 11/2013 0x1810384b (32.53 rounds)
Swap:	0MB of 127MB used (0%)
System:	1164MB of 1641MB used (70%)
Data:	938MB of 5596MB used (16%)

[BigAlT]

How long has it been since you’ve replaced your micro SD card ?. They are known to fail due to the numerous read/writes required when Meteohub stores weather data. You may need to install the latest version of Meteohub available on the website ( I think it’s 4.9s ) on a new micro SD card, transfer your license to the new card and then update to 5.1b
If that solves your problem, I’d recommend you change from using the micro SD card to store data to a usb thumb drive attached to your RPi ( there are Instructions for doing this in earlier posts on the forum ).
The micro SD card failure issue is a well known & discussed problem with failures happening at unpredictable intervals which can be as short as months.

[tastewar]

I've never replaced it.

After reading your post, I ordered a replacement. FWIW, it's a "SanDisk High Endurance" card. No, not a real industrial strength card. I would like to think that if this were the problem, *something* would be logging those write errors, but I don't see anything suggesting that in any of the logs. Well, nothing obvious to me, but what do I know.

Can you (or someone) point me to directions for saving the license in such a way that I can install from scratch, and still apply the license? I do have the original paypal receipt email which appears to have likely key info in it.

Can you also point me to the instructions for moving data to a thumb drive?

[BigAlT]

To transfer your license to a new micro SD card go to the transfer webpage https://wiki.meteohub.de/Transfer and follow the directions. Make sure you save your current system Id and activation code ( found on your Meteohub maintenance page ) before starting the transfer process. Then after installing and booting your RPi with your new micro SD card your Meteohub will have a new system id. Then go to the transfer webpage ( the bottom part of the page is for the RPi ). Enter the old system id, the old activation code and the new system id. Click on the generate new activation code button and you will get a new activation code for your new system id. Make sure you save this new activation code before closing the window or you’ll loose it and have to email Boris for it. Enter the new activation code in the Maintenance Page of your Meteohub and save it. Your new Meteohub installation will now be activated.
For using a USB thumb drive for data storage follow the instructions in this article I found ( translated from German ) on the web.

Meteohub on Raspberry Pi - data on USB stick
AUGUST 15, 2015MATTHIAS MANHARTCOMPUTERS AND DEVICES , RASPBERRY , WEATHER
For my Davis Vantage weather station I use the software Meteohub ( link ) to save the measurement data and to visualize it on my website. Some time ago I switched from hardware NSLU2 to Raspberry 2.

At fairly regular intervals of 2-3 weeks, I discovered erroneous entries in the raw data (eg weather \ 201408 \ raw) in the Meteohub log.

raw_error

It could even happen that the Raspberry did not want to start after a reboot of the SD card. I soon backed up all the files in the "public" directory every day, and yet I had to rebuild the card every few weeks.

I decided to move the data from Meteohub from the SD card to a USB stick.Below I describe how I proceeded.

I expressly point out that I decline any liability if this process does not work out.

Background:

Raspberry Pi (model B or 2) with SD card ( also works on 3b but not 3b+ or above )
Meteohub installed and fully in operation (in my version 5.0j)
Backup created (maintenance - backup application data)
All files in the directory "public" (network share) saved externally (except directory "upload")
Data collection stopped (maintenance - pause data collection process)
Weather station suspended from the Raspberry Pi
Action:

Insert USB stick into the Raspberry Pi (I am using a 32GB stick from HP (FDU32GBHPV165W-EF))
Access Meteohub with the terminal program putty (Username: root, Password: meteohub)
Check if the USB stick has been detected: fdisk -l

63A43D2B-610F-44AA-A80B-B773F6BB4276.png (34.19 KiB) Viewed 6543 times

Here, the USB stick (example with 4GB capacity) appears under / dev / sda with a partition / dev / sda1. The current data partition of Meteohub can be seen under / dev / mmcblk0p4.
Now the USB stick is prepared for use with Meteohub:
- fdisk /dev/sda
- d (delete partition)
- n (create new primary partition, confirm all default settings)
- w (save partition data and leave fdisk)
Formatting the USB stick with the file system EXT4: mkfs.ext4 / dev / sda1
The file / etc / fstab now has to be adjusted so that the new data is saved on the USB stick:
- nano / etc / fstab
- Insert a # at the beginning of the line / dev / mmcblk0p4
- Insert new line directly afterwards:
/ dev / sda1 / data ext4 defaults, noatime 0 0
(Empty area with tab key, zeros at the end of the line)
- CTRL + x (leaving nano)
- y (save file)
The fstab file now looks like this:

AED3AF0A-A3F0-4E87-893C-7B8ABCD64156.png (30.64 KiB) Viewed 6543 times

Reboot Raspberry Pi: reboot
Reconnect to Meteohub via putty
Check if the USB stick has been loaded correctly: mount

3400612D-E36F-4C8F-B491-28BBFBEC0494.png (37.85 KiB) Viewed 6543 times

The USB stick is loaded:
/ dev / sda1 on / data type ext4 (rw, noatime, data = ordered)
Now copy all files including the data backup over the network to the directory "public"
In the web interface of Meteohub choose to restore the data (Maintenance - load application data)
Switch off Raspberry Pi (Maintenance - Switch off Meteohub system)
Reconnect the weather station
Turn on Raspberry Pi
Check in the web interface, if everything runs correctly
The starting point of these adjustments was this contribution at www.forum-raspberrypi.de
If the commands don’t run make sure to use the letter spacing on the images which are attached.

[BigAlT]

There is also the possibility that there is a problem with the USB connection between your weather station console and your RPi. Have you tried rebooting your console and or your RPi and seeing if that solves the problem ?. I’ve had the same error message on several occasions and it was caused by a communication problem between my console and the RPi. Rebooting either or both of the units always solved the problem. Since you’ve rebooted your RPi several times, try rebooting your console and then rebooting the RPi.
It appears that Boris is no longer supporting Meteohub ( it’s using the Raspbian Wheezy OS which is no longer supported and would require a rewrite to be compatible with the current Raspbian OS Buster ).
If nothing fixes your problems and you want a free program that runs fine on An RPi using Buster. Weewx works great. It uploads to WU and supports most Accurite Weather Stations. It takes a while to figure out how to install & configure it but once running is great.