Robin Unless you have a good reason I would recommend a fresh install of stretch since you are already deep in the proverbial anyway
The only rpi I have still on wheezy is one no longer in live production use - all my others (for weewx, touch display and soil moisture sensors) are now on Jessie and one is on stretch for my sprinkler watering!! But yes, you sound as bad as me for following good advice!!!!!! Andrew PS - OK - I'll stop looking around, but I suspect the likely cause is a wheezy/weewx mismatch rather than weewx itself On Sunday, 4 March 2018 16:59:45 UTC+2, Robin wrote: > Andrew, > > Correct, I am running Wheezy. > > Please stop trying to solve this (for now). > > I decided to update to 3.8 and all hell has broken loose. Typically I > ignored all the good advice to backup the SD card. Now pulling my hair out > (not much left to work with). > > Gone back to old conf file and made a couple of hacks to get it running. > > Robin > > 3.6.1 was working fine - *if > <https://en.wiktionary.org/wiki/if#English> it > <https://en.wiktionary.org/wiki/it#English> ain’t > <https://en.wiktionary.org/wiki/ain%27t#English> broke > <https://en.wiktionary.org/wiki/broke#English>, don’t > <https://en.wiktionary.org/wiki/don%27t#English> fix > <https://en.wiktionary.org/wiki/fix#English> it > <https://en.wiktionary.org/wiki/it#English>* > > > *sigh........* > On Sunday, 4 March 2018 15:43:19 UTC+2, Andrew Milner wrote: >> >> getting closer ..... >> >> Having checked 5 different RPis ..... Jessie and Stretch respond like I >> posted originally >> >> Wheezy responds like yours, and does not appear to accept the -p option >> >> whether there is any significance in this I do not know!!! It could be >> that the proc info is different in wheezy >> >> >> >> >> >> On Sunday, 4 March 2018 15:27:56 UTC+2, Andrew Milner wrote: >> >>> then i'm well baffled as so am i - running raspbian, yet my uptime -p >>> command gave a very different result to yours!! I also use the bootstrap >>> skin >>> >>> the answer must lie in your skin/weewx.conf or the log ..... >>> >>> have you tried gary's suggestion yet?? >>> >>> >>> >>> >>> On Sunday, 4 March 2018 14:48:16 UTC+2, Robin wrote: >>> >>>> I'm running a Raspberry Pi. >>>> >>>> >>>> On Sunday, 4 March 2018 11:12:43 UTC+2, Andrew Milner wrote: >>>>> >>>>> are you on a MAC by any chance?? seems like weewx has implemented >>>>> pretty much the method outlined here for os uptime: >>>>> >>>>> http://planzero.org/blog/2012/01/26/system_uptime_in_python,_a_better_way >>>>> >>>>> >>>>> >>>>> On Sunday, 4 March 2018 11:07:39 UTC+2, Andrew Milner wrote: >>>>> >>>>>> the format must vary with the operating system then as mine says >>>>>> up 1 week, 3 hours, 51 minutes!! >>>>>> >>>>>> not too sure why your uptime should give be giving any info about >>>>>> users or load averages though!! >>>>>> >>>>>> >>>>>> >>>>>> On Sunday, 4 March 2018 10:14:51 UTC+2, Robin wrote: >>>>>> >>>>>>> up 16 days, 18:57, 1 user, load average: 0.14, 0.19, 0.21 >>>>>>> >>>>>>> On Sunday, 4 March 2018 09:30:10 UTC+2, Andrew Milner wrote: >>>>>>>> >>>>>>>> if you do uptime -p what result do you get?? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Sunday, 4 March 2018 09:15:11 UTC+2, Andrew Milner wrote: >>>>>>>> >>>>>>>>> and the log?? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sunday, 4 March 2018 08:40:23 UTC+2, Robin wrote: >>>>>>>>> >>>>>>>>>> OK the page is now updating (not the images, I'm only interested >>>>>>>>>> in the uptime). >>>>>>>>>> >>>>>>>>>> http://www.weather.molyvos.eu/Bootstrap/ >>>>>>>>>> >>>>>>>>>> It still shows >>>>>>>>>> >>>>>>>>>> Station uptime: 0 days, 0 Hours, 0 minutes >>>>>>>>>> Server uptime: 0 days, 0 Hours, 6 minutes >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sunday, 4 March 2018 08:27:31 UTC+2, Robin wrote: >>>>>>>>>>> >>>>>>>>>>> Andrew, >>>>>>>>>>> >>>>>>>>>>> my bad, just noticed that myself and was about to post. I will >>>>>>>>>>> get /bootstrap/index running again and see what happens >>>>>>>>>>> >>>>>>>>>>> Robin >>>>>>>>>>> >>>>>>>>>>> On Sunday, 4 March 2018 08:11:47 UTC+2, Andrew Milner wrote: >>>>>>>>>>>> >>>>>>>>>>>> the bootstrap skin has totally the wrong date and time of lasdt >>>>>>>>>>>> update though!!!!! It is saying November 2015 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Sunday, 4 March 2018 08:07:30 UTC+2, Robin wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Gary, >>>>>>>>>>>>> >>>>>>>>>>>>> I don't think it is the template or skin config as I also have >>>>>>>>>>>>> a Bootstrap skin running. >>>>>>>>>>>>> >>>>>>>>>>>>> http://www.weather.molyvos.eu/Bootstrap/index.html >>>>>>>>>>>>> >>>>>>>>>>>>> Since I did a Weewx stop/start it now shows >>>>>>>>>>>>> >>>>>>>>>>>>> Weewx uptime: 0 days, 0 hours, 0 minutes >>>>>>>>>>>>> Server uptime: 0 days, 0 hours, 6 minutes >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Saturday, 3 March 2018 20:41:38 UTC+2, gjr80 wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> $station.uptime by itself should format just fine, though it >>>>>>>>>>>>>> will/may depend on the contents of skin.conf. In your case it >>>>>>>>>>>>>> appears to be >>>>>>>>>>>>>> formatting as it should. Given we are talking about a custom >>>>>>>>>>>>>> page (ie not >>>>>>>>>>>>>> one included in a default weeWX install) it would be worth >>>>>>>>>>>>>> posting the >>>>>>>>>>>>>> template file (.tmpl) and skin config file being used. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Gary >>>>>>>>>>>>>> >>>>>>>>>>>>> -- 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.
