RE: [weewx-user] Re: $station.uptime

[Andrew Milner]

We  have a few paracetomols to help you 
out!!!

Go on – a few deep breaths and a fresh sd card and a new install ...

As long as you are on a fresh sd card you should be ok as you rebuild.
But yes, a list of the addons is a prerequisite and a good excuse for a few 
beers as you exercise the memory cells 



Sent from Mail for Windows 10

From: Robin
Sent: 04 March 2018 18:00
To: weewx-user
Subject: [weewx-user] Re: $station.uptime

Andrew,

I'm going to sit in the 'stupid' corner for a while!

A fresh install is going to take courage. I have a lot of bits and bobs that I 
have added in, some of which I can only just remember! My knowledge and skill 
level give me major worries that I won't get everything back together again.

I think I need to start with building a list of my added 'stuff' and then 
making a plan to get it all back into a new install.

I already have a headache.

Robin
-- 
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/oNaUk2ENIzc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com.
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Robin]

Andrew,

I'm going to sit in the 'stupid' corner for a while!

A fresh install is going to take courage. I have a lot of bits and bobs 
that I have added in, some of which I can only just remember! My knowledge 
and skill level give me major worries that I won't get everything back 
together again.

I think I need to start with building a list of my added 'stuff' and then 
making a plan to get it all back into a new install.

I already have a headache.

Robin

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Andrew Milner]

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 
>  it 
>  ain’t 
>  broke 
> , don’t 
>  fix 
>  it 
> *
>
>
> *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:
>>
>>>

[weewx-user] Re: $station.uptime

[Robin]

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  it 
 ain’t 
 broke 
, don’t 
 fix 
 it 
*


*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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://g

[weewx-user] Re: $station.uptime

[Andrew Milner]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Andrew Milner]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Robin]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Andrew Milner]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Andrew Milner]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Robin]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Andrew Milner]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: $station.uptime

[Andrew Milner]

sorry gary - we seem to have crossposted!!



On Sunday, 4 March 2018 09:28:19 UTC+2, Andrew Milner wrote:

> if you search for uptime in /bin/weewx/station.py you will see how weewx 
> and server uptimes are derived!!
>
> may offer some clues
>
>
>
> On Sunday, 4 March 2018 09:18:41 UTC+2, Erwin Heger wrote:
>
>> The data from this example webpage are all totally outdated, all from 
>> 2015.
>>
>> Did you switch the database or is it all static?
>>
>> Better put the uptime-variable into a live page than driving us nuts with 
>> something, that doesn’t work at all.
>>
>>
>>> 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
>>>
>>>
>>> E
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: $station.uptime

[Andrew Milner]

if you search for uptime in /bin/weewx/station.py you will see how weewx 
and server uptimes are derived!!

may offer some clues



On Sunday, 4 March 2018 09:18:41 UTC+2, Erwin Heger wrote:

> The data from this example webpage are all totally outdated, all from 2015.
>
> Did you switch the database or is it all static?
>
> Better put the uptime-variable into a live page than driving us nuts with 
> something, that doesn’t work at all.
>
>
>> 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
>>
>>
>> E
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[gjr80]

You might want to upgrade to a later weeWX version, at least 3.7.0, as there 
have been a number of changes to bin/weewx/station.py (the module that handles 
station uptime and server uptime) since your 3.6.1 version. I had a quick look 
at station.py just now and cannot see any one change that would obviously fix 
your issue but the changes have been substantial. You could probably just 
download the current station.py from the weeWX github repo master branch and 
replace your current station.py. Something like:

$ wget https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/station.py

should download the current file. If you do take this approach make sure you 
keep the old file in case you need to revert. WeeWX will need to be restarted 
after such a change.

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: $station.uptime

[m...@erwinheger.de]

The data from this example webpage are all totally outdated, all from 2015.

Did you switch the database or is it all static?

Better put the uptime-variable into a live page than driving us nuts with 
something, that doesn’t work at all.

> 
> 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
> 
> 
E

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Andrew Milner]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Robin]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Robin]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Andrew Milner]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Robin]

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[gjr80]

$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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Andrew Milner]

One other reason is that the about page is not, for some reason, being 
regenerated every report cycle - or is not being copied/ftpd every cycle.  
Is it perhaps included in the 'copy once only' list??

As gary says, looking at the site may help and the logs certainly would be 
valuable and should be informative.



On Saturday, 3 March 2018 15:02:34 UTC+2, gjr80 wrote:

> Hi,
>
> Is your site visible from the Internet, if so could you provide a link? 
> The algorithm for calculating station uptime is fairly basic, the only real 
> way to confuse it and display what you describe would be if weeWX was 
> continually being restarted. That would ceratainly show in the log. Even if 
> weeWX was starting with a system time that is too far in the past it would 
> be a one-off event and again it would be evident in the log.
>
> I trust you have restarted weeWX? Would be interesting to see a log from 
> weeWX startup covering about 15-20 minutes.
>
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime

[Andrew Milner]

Maybe time is standing still ...

Seriously though - do the other variables like system time change with only 
station uptime appearing to be stuck in a spacetime distortion??



On Saturday, 3 March 2018 10:45:48 UTC+2, Robin wrote:

> I have this feeling in my water that I am missing something really simple 
> here, BUT...
>
> Why does my station uptime not change? It shows "Weewx uptime: 0 days, 0 
> hours, 6 minutes" permanently!
>
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

[Thomas Keffer]

I suppose we could include a check in the templates that if uptime is None,
don't render the days, hours, and seconds at all.

-tk

On Sun, Oct 30, 2016 at 11:36 PM, gjr80  wrote:

> Hi,
>
> I wouldn't go so far as to say this is expected behaviour (well it is
> expected in as much as the code is doing what it ought to), but if you
> think a little about wee_reports I think the result is logical.
> wee_reports is a standalone utility that runs a weewx report cycle as per
> the [StdReport] stanza in weewx.conf. wee_reports has no idea whether
> weewx is running or not; sure wee_reports uses a pile of weewx API calls
> but it doesn't interact with any running instances of weewx. So as far as
> wee_reports is concerned the concept of how long weewx has been running
> for is meaningless, and in fact wee_reports does not even have the
> 'knowledge' to work it out. So in looking at wee_reports in that context,
> the fact that it returns '0 days, 0 hours, 0 seconds' makes sense (well it
> actually returns None but the weewx formatting applied means it is
> displayed as 0 days, 0 hours, 0 seconds).
>
> Gary
>
>
> On Monday, 31 October 2016 13:43:56 UTC+10, erbenton07 wrote:
>>
>> I've seen this again since I posted, but this time I paid more attention.
>> It only happens if you use wee_reports to get a fast update.  'systemctl
>> reload weewx' doesn't alter the time displayed but wee_reports generates an
>> uptime of 0. After the next normal iteration of weewx update generation the
>> time reverts back to normal values. Probably wee_reports isnt generating an
>> uptime value? Anyway - its minor.
>>
> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

[gjr80]

Hi,

I wouldn't go so far as to say this is expected behaviour (well it is 
expected in as much as the code is doing what it ought to), but if you 
think a little about wee_reports I think the result is logical. wee_reports 
is a standalone utility that runs a weewx report cycle as per the 
[StdReport] stanza in weewx.conf. wee_reports has no idea whether weewx is 
running or not; sure wee_reports uses a pile of weewx API calls but it 
doesn't interact with any running instances of weewx. So as far as 
wee_reports is concerned the concept of how long weewx has been running for 
is meaningless, and in fact wee_reports does not even have the 'knowledge' 
to work it out. So in looking at wee_reports in that context, the fact that 
it returns '0 days, 0 hours, 0 seconds' makes sense (well it actually 
returns None but the weewx formatting applied means it is displayed as 0 
days, 0 hours, 0 seconds).

Gary

On Monday, 31 October 2016 13:43:56 UTC+10, erbenton07 wrote:
>
> I've seen this again since I posted, but this time I paid more attention. 
> It only happens if you use wee_reports to get a fast update.  'systemctl 
> reload weewx' doesn't alter the time displayed but wee_reports generates an 
> uptime of 0. After the next normal iteration of weewx update generation the 
> time reverts back to normal values. Probably wee_reports isnt generating an 
> uptime value? Anyway - its minor.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

[erbenton07]

I've seen this again since I posted, but this time I paid more attention. 
It only happens if you use wee_reports to get a fast update.  'systemctl 
reload weewx' doesn't alter the time displayed but wee_reports generates an 
uptime of 0. After the next normal iteration of weewx update generation the 
time reverts back to normal values. Probably wee_reports isnt generating an 
uptime value? Anyway - its minor.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

[Steve]

You can also use wee_reports to see your 'quick' changes in the templates 
etc immediately (not waiting for the next report cycle) without reloading 
or restarting weewx.

http://www.weewx.com/docs/utilities.htm#wee_reports_utility

Regards,

Steve.

On Friday, 14 October 2016 20:18:31 UTC+11, erbenton07 wrote:
>
> weewx 3.4.0 under OpenSuse linux 13.1 on x86_64
>
> If you do "systemctl reload weewx" then $station.uptime is reset to 0.
> This should only be reset if weewx is restarted. Sometimes quick changes 
> in index.html.tmpl are needed and weewx "reload" is used to tell weewx to 
> re-read the file. This is (or should be) a different paradigm than shutting 
> down and restarting weewx with a command line "systemctl restart weewx" 
> otherwise whats the point in having a reload option vs  restart 
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

[vince]

On Friday, October 14, 2016 at 2:35:24 AM UTC-7, gjr80 wrote:
>
> - A reload (or a restart if you really want to) is required if you make 
> changes to weewx.conf.
>

yup - that was the case I had a few times in the past.   I think I had 
forgotten to enable the station registry, but  didn't want to bounce the 
whole weewx set of things as it had been up for many months at the time and 
I was trying to look at memory leak measurements or the like.

Nice summary Gary, is that in the wiki or faq someplace ?

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

[erbenton07]

Strange, at first this reads zero but after awhile it **does** resume 
normal station  uptime.
I guess its a quirk,.
*For now please ignore my original post*

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.