Just remember that you were getting voltage issues at one time. Those voltage issues could have damaged the rpi in some way or the sd card in some way. Putting a new supply in pace has stopped the low voltage issues - but will not have repaired any previous damage to rpi or sd card.
I would uggest a new good quality sd card, a fresh installation, a RTC addition if you do not have one, and a powered usb hub. When you reinstall weewx run with the standard seasons skin for a few days until you are sure everything seems ok and then start changing your skins and doing your addons. I would also refrain from using the weewx rpi for other activities such as home automation for a while - you do not want to stress the RPi!!!!!! On Sunday, 3 March 2019 10:08:25 UTC+2, gizm0 wrote: > > I checked with command vcgencmd_get_throttled if raspi has been under > voltage or is under voltage it says everything is ok. Also I checked from > dmesg, if there were any write errors or similar and there was no errors at > all. > > # /opt/vc/bin/vcgencmd get_throttled > throttled=0x0 > > I guess I have to reinstall everything. > > > On Sunday, March 3, 2019 at 2:04:10 AM UTC+2, Thomas Keffer wrote: >> >> Through the years, we've learned that these mysterious RPi failures are >> almost always due to one of two things: >> >> 1. An inadequate power supply; or >> 2. A failing SD card. >> >> I suspect the problem is #1. >> >> -tk >> >> On Sat, Mar 2, 2019 at 1:30 PM gizm0 <[email protected]> wrote: >> >>> Thanks that explains the wee_device. Now wee_device command works 100%, >>> but starting daemon is still failing and I cannot find any reason for that. >>> The only reason which i can find is that in log it says "ee_device[1880]: >>> fousb: found station on USB bus= device=". I don't understand why there is >>> no BUS or Device defined. >>> >>> Anyways here is what wee_device command no displays when i change >>> setting: >>> ~# wee_device --set-interval=15 >>> Using configuration file /etc/weewx/weewx.conf >>> Using FineOffsetUSB driver version 1.9 (weewx.drivers.fousb) >>> Interval is 15 >>> Set interval to 15 minutes (y/n)? y >>> Interval is now 15 >>> >>> >>> On Saturday, March 2, 2019 at 10:57:18 PM UTC+2, Thomas Keffer wrote: >>>> >>>> It is >>>> >>>> * wee_device --set-interval=15* >>>> >>>> not >>>> >>>> * wee_device --set-interval 15* >>>> >>>> With the latter form, it's thinking that "15" is the name of your >>>> configuration file. >>>> >>>> -tk >>>> >>>> On Sat, Mar 2, 2019 at 12:48 PM gizm0 <[email protected]> wrote: >>>> >>>>> Thank you for your reply. As you can see from the previous message >>>>> where i attached the config the debug is set to 1. >>>>> >>>>> The system worked until 13:49 then it refused to start the service. So >>>>> that's why there is working record on 13:40 timestamp. >>>>> >>>>> Weewx is running off site where it has worked with the same setup from >>>>> last september. At least during last 1 month I have not touched anything. >>>>> The only thing that system has done is upgrade packages automatically on >>>>> 9.2.2019. >>>>> >>>>> Same hardware has been running the setup from last September. The only >>>>> thing that I changed is that I bought 3months ago original Raspberry pi >>>>> power supply ( >>>>> https://cdon.fi/kodin-elektroniikka/raspberry-pi-3-micro-usb-power-supply-p40237610). >>>>> >>>>> Before that raspberry pi reported low voltage errors and that's why I >>>>> bought better supply. >>>>> >>>>> Here is screenshot when i try to manually start the service, set >>>>> device setting and check device status: >>>>> >>>>> [image: raspi2_weewx_02032019.jpg] >>>>> >>>>> >>>>> On Saturday, March 2, 2019 at 9:35:06 PM UTC+2, vince wrote: >>>>>> >>>>>> On Saturday, March 2, 2019 at 11:04:26 AM UTC-8, gizm0 wrote: >>>>>>> >>>>>>> Sorry about that, but the weewx is not starting process so there is >>>>>>> no activities after it has tried to start. Anyways here is the full >>>>>>> log. >>>>>>> Notice that weewx stopped to work around 13:49 and after that i have >>>>>>> tried >>>>>>> to manually start the service as you can see from the log. >>>>>>> >>>>>>> >>>>>> Next time you do so, please set debug = 1 in your weewx.conf file so >>>>>> we see more verbose logs. >>>>>> >>>>>> I grepped the file to show only lines with 'weewx' on them, and I >>>>>> don't see any places where it actually stopped. Lots of startups, but >>>>>> no >>>>>> stops. I also see a lot of places where it 'did' save records to the >>>>>> database, at least briefly (most recently 13:40:35) so it worked at >>>>>> least >>>>>> for a while, but it's impossible to know what you touched or when after >>>>>> then. >>>>>> >>>>>> Just to eliminate the possibility, did you change any hardware ? >>>>>> Are you powering things with a 'good' power supply ? That can mess up >>>>>> a >>>>>> raspi pretty consistently ? >>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "weewx-user" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "weewx-user" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
