I would suggest you have a proper plan on how to cope with a read only rpi
- or maybe even just run the rpi and weewx in a standard configuration
until you know how everything works - especially if you do not have a RTC
installed.  Also make sure that you are not running the latest NTP software
which I believe has some form of buffering similar to fake hwclock - but
not quite as bad!!  I saw someone mention this in a recent thread in this
forum.

On 29 January 2018 at 13:14, Praveen Chandrasekaran <[email protected]>
wrote:

> No idea if it was empty or not. I am not backing it up to an external USB
> ( I know that is very bad!) so I am not sure what would be it contents in
> case of abrupt power down and power up. My setup is only since 2 weeks and
> I am still learning. Need to do some backup plan.
>
> On Monday, 29 January 2018 16:39:55 UTC+5:30, Andrew Milner wrote:
>>
>> The log of the start-up is what is needed.
>>
>> You say the database was empty when you started weewx??  Is that
>> correct??  If it was totally empty then I don't think weewx tries to fill
>> in any gaps - as there are no gaps!! Tom can say if weewx reads history
>> records when weewx starts and the database is empty.
>>
>>
>>
>> On Monday, 29 January 2018 12:40:23 UTC+2, Praveen Chandrasekaran wrote:
>>
>>> One additional detail - my pi is read only mode. On abrupt power down
>>> the latest SQL database may not have been stored. Not sure if that messed
>>> up anything though I believe the pi should have still rebuilt the records.
>>>
>>> Right now I am using ntp with fake hw clock removed, I am planning to
>>> put in a RTC soon.
>>>
>>> Will dig more in the log sometime and also post the log here.
>>>
>>> On Monday, 29 January 2018 15:01:56 UTC+5:30, Andrew Milner wrote:
>>>>
>>>> The log would have shed light on any problems.
>>>> You should not have needed to use any utility at all - what made you
>>>> decide to use wee_database??.
>>>> If you had done nothing weewx would have retrieved records from the
>>>> logger from after the last archive record in its database automatically -
>>>> this sometimes takes some time.  On a RPi you should either add a RTC
>>>> module or completely disable the fake hw clock to ensure weewx does not
>>>> start until it has got a correct time from the NTP servers to ensure
>>>> correct automatic operations which are reliant on accurate timestamps (such
>>>> as recovery from a power outage).
>>>>
>>>> The log is always the key - and without a log everything becomes
>>>> guesswork and speculation whilst with the log we can be talking actual
>>>> facts!!!!
>>>>
>>>>
>>>>
>>>> On Monday, 29 January 2018 09:57:59 UTC+2, Praveen Chandrasekaran wrote:
>>>>
>>>>> Thanks. Will post with all details from next time. For now I did a
>>>>> wee_device --dump and that populated the sql database after which I could
>>>>> update WU with wunderfixer (the summary still has not got updated in WU as
>>>>> per updated records, I can see updated records in graphs and table - I
>>>>> believe that is an issue at WU end and I have filed a bug report with them
>>>>> for the same). Not sure why weewx did not populate the sql on its own
>>>>> though without forcing through wee_device --dump.
>>>>>
>>>>> On Sunday, 28 January 2018 23:22:40 UTC+5:30, Tom Keffer wrote:
>>>>>>
>>>>>> This should happen automatically, but it's hard to say what the
>>>>>> problem is without a log. See *Help! Posting to weeWX
>>>>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user>*.
>>>>>>
>>>>>> -tk
>>>>>>
>>>>>> On Sun, Jan 28, 2018 at 10:15 AM, Praveen Chandrasekaran <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> For some reason my pi went down yesterday morning for 5 hours. I
>>>>>>> tried rebuilding database using wee_database but to no avail. How do I
>>>>>>> import data from data logger to weewx so that I can use wunderfixer 
>>>>>>> then to
>>>>>>> publish again to wu?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Praveen
>>>>>>>
>>>>>>> --
>>>>>>> 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 a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/XYmglRBbWrg/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

Reply via email to