Re: [weewx-user] Re: Looking for a Weewx running script

[Andrew Milner]

I'm still a little lost as to why your weather station is talking to weewx 
via the internet - can't you just give weewx an internal IP address for the 
weather station and not bother using dyndns.

Just seen that this was discussed a year or so ago also - so will let the 
vp experts take over from here - looks as though other setting tweeks may 
be required for the ip logger.

https://groups.google.com/forum/#!topic/weewx-user/KzYWtyrct0o



On Thursday, 24 May 2018 13:01:46 UTC+3, Andrew Milner wrote:
>
> then that is when we need the log.  the log you posted weewx was still 
> running.
>
> I guess eventually weewx probably hits the wait for x minutes before 
> restarting situation - maybe that is what is happening - but weewx would 
> log a message before shutting down.
>
> I do not believe the log you posted was from a time when weewx was 
> stopped.  Next time it appears stopped can you post the log so we can see 
> how and why it shut down.
>
>
>
> On Thursday, 24 May 2018 12:58:00 UTC+3, Mike wrote:
>>
>> Hi Andrew,
>>
>> in case it would be run I should get this message when I try to start it: 
>> "already running"
>>
>> /etc/init.d/weewx start
>>
>> * Starting weewx weather system weewx
>>  *  already running...
>>...done.
>>
>> What I am calling a crash and I run
>>
>> /etc/init.d/weewx start
>>
>> I am getting, see below, so Weewx is not running and after the website is 
>> getting
>>
>> updates from the station
>>
>> * Starting weewx weather system weewx
>>...done.
>>
>>
>>
>>
>>
>>
>> 2018-05-24 16:46 GMT+07:00 Andrew Milner :
>>
>>> I am sorry - this is NOT a crash.  Weewx is sill running and is trying 
>>> and trying to reach your station.
>>>
>>> If you look closely at your log you will see it is logging try #1, try 
>>> #2, try #3, try #4 and so forth.  This is not a crash - this is handling an 
>>> error because it cannot communicate with the station.  Presumably your 
>>> redirection is not yet up-to-date, so weewx cannot communicate with the 
>>> station and must keep retrying.  There is nothi9ng else weewx can do until 
>>> the connection is re-established via your redirection.
>>>
>>> Weewx is still running and trying to communicate with the station.  Why 
>>> do you say it has crashed??  
>>>
>>>
>>>
>>>
>>> On Thursday, 24 May 2018 12:15:09 UTC+3, Mike wrote:

 Dear Andrew,

 my Weewx is not running at this point, see the log file

 Right now it is running, If I try to start it I am getting:

 * Starting weewx weather system weewx
  *  already running...
...done.

 which is right.

 But before it was not running and it was crahing. I am pretty sure the 
 Dedicated server with my Domain is getting the right IP.

 Any way, I have changed the wait time as you have suggested to 360 and 
 restarted Weewx.

 Pls have a look again into my log file, I have seen 100 times the entry 
 with the same date/time stamp. I think it is not normal too.

 May 24 00:19:11 sd-69780 weewx[1752]: vantage: Retry  #16 failed
 May 24 00:19:11 sd-69780 weewx[1752]: vantage: ip-write error: [Errno 32] 
 Broken pipe 



 2018-05-24 15:54 GMT+07:00 Andrew Milner :

> since you seem to be using a non-static ip connection which may not be 
> known for 5 minutes (30 secs) to the weather station have you tried 
> increasing the wait time to say 6 minutes (360 secs) in weewx.conf 
> (currently set to 180 secs).  I'm sure this is a question of tweeking the 
> timeouts and retries to make weewx cater for the fact that the ip address 
> of the station has altered.
>
> Of course, if you can give the station and host addresses on an 
> internal network things would improve - but you don't give the hardware / 
> network setup.
>
> I'm sure many people are running watchdog scripts of some kind 
> though.  Your issue does not appear to be a crash from the log segment 
> you 
> posted however - since weewx is definitely still trying to establish 
> contact with the station - so weewx is doing the right things.
>
> Another VP user will know the answer to this - but it seems to me that 
> from a theoretical viewpoint it would be better in your situation to have 
> no loop records, hardware created archive records, and only poll the 
> station once every archive interval to retrieve the latest rec - and 
> ignore 
> loop data.  This would have the effect of minimising the comms with the 
> station ….but I do not know if this is possible or not.
>
>
> On Thursday, 24 May 2018 11:35:17 UTC+3, Mike wrote:
>>
>> Thanks for your quick response. I have no fixed IP from my ISP, my 
>> DynDNS IP is checked and updated every 5 minutes
>>
>> I am running a Davice Vantage Pro with WeatherLink IP
>>
>> As attached file the log and 

Re: [weewx-user] Re: Looking for a Weewx running script

[Andrew Milner]

then that is when we need the log.  the log you posted weewx was still 
running.

I guess eventually weewx probably hits the wait for x minutes before 
restarting situation - maybe that is what is happening - but weewx would 
log a message before shutting down.

I do not believe the log you posted was from a time when weewx was 
stopped.  Next time it appears stopped can you post the log so we can see 
how and why it shut down.



On Thursday, 24 May 2018 12:58:00 UTC+3, Mike wrote:
>
> Hi Andrew,
>
> in case it would be run I should get this message when I try to start it: 
> "already running"
>
> /etc/init.d/weewx start
>
> * Starting weewx weather system weewx
>  *  already running...
>...done.
>
> What I am calling a crash and I run
>
> /etc/init.d/weewx start
>
> I am getting, see below, so Weewx is not running and after the website is 
> getting
>
> updates from the station
>
> * Starting weewx weather system weewx
>...done.
>
>
>
>
>
>
> 2018-05-24 16:46 GMT+07:00 Andrew Milner  >:
>
>> I am sorry - this is NOT a crash.  Weewx is sill running and is trying 
>> and trying to reach your station.
>>
>> If you look closely at your log you will see it is logging try #1, try 
>> #2, try #3, try #4 and so forth.  This is not a crash - this is handling an 
>> error because it cannot communicate with the station.  Presumably your 
>> redirection is not yet up-to-date, so weewx cannot communicate with the 
>> station and must keep retrying.  There is nothi9ng else weewx can do until 
>> the connection is re-established via your redirection.
>>
>> Weewx is still running and trying to communicate with the station.  Why 
>> do you say it has crashed??  
>>
>>
>>
>>
>> On Thursday, 24 May 2018 12:15:09 UTC+3, Mike wrote:
>>>
>>> Dear Andrew,
>>>
>>> my Weewx is not running at this point, see the log file
>>>
>>> Right now it is running, If I try to start it I am getting:
>>>
>>> * Starting weewx weather system weewx
>>>  *  already running...
>>>...done.
>>>
>>> which is right.
>>>
>>> But before it was not running and it was crahing. I am pretty sure the 
>>> Dedicated server with my Domain is getting the right IP.
>>>
>>> Any way, I have changed the wait time as you have suggested to 360 and 
>>> restarted Weewx.
>>>
>>> Pls have a look again into my log file, I have seen 100 times the entry 
>>> with the same date/time stamp. I think it is not normal too.
>>>
>>> May 24 00:19:11 sd-69780 weewx[1752]: vantage: Retry  #16 failed
>>> May 24 00:19:11 sd-69780 weewx[1752]: vantage: ip-write error: [Errno 32] 
>>> Broken pipe 
>>>
>>>
>>>
>>> 2018-05-24 15:54 GMT+07:00 Andrew Milner :
>>>
 since you seem to be using a non-static ip connection which may not be 
 known for 5 minutes (30 secs) to the weather station have you tried 
 increasing the wait time to say 6 minutes (360 secs) in weewx.conf 
 (currently set to 180 secs).  I'm sure this is a question of tweeking the 
 timeouts and retries to make weewx cater for the fact that the ip address 
 of the station has altered.

 Of course, if you can give the station and host addresses on an 
 internal network things would improve - but you don't give the hardware / 
 network setup.

 I'm sure many people are running watchdog scripts of some kind though.  
 Your issue does not appear to be a crash from the log segment you posted 
 however - since weewx is definitely still trying to establish contact with 
 the station - so weewx is doing the right things.

 Another VP user will know the answer to this - but it seems to me that 
 from a theoretical viewpoint it would be better in your situation to have 
 no loop records, hardware created archive records, and only poll the 
 station once every archive interval to retrieve the latest rec - and 
 ignore 
 loop data.  This would have the effect of minimising the comms with the 
 station ….but I do not know if this is possible or not.


 On Thursday, 24 May 2018 11:35:17 UTC+3, Mike wrote:
>
> Thanks for your quick response. I have no fixed IP from my ISP, my 
> DynDNS IP is checked and updated every 5 minutes
>
> I am running a Davice Vantage Pro with WeatherLink IP
>
> As attached file the log and my conf file
>
> Thanks again
>
> 2018-05-24 14:56 GMT+07:00 Andrew Milner :
>
>> Weewx does not crash without a reason.  Believe me - it doesn't.
>>
>> What does the log have to say around the time of the crashes.  Fixing 
>> the cause of your crashes is the right way to go about fixing the 
>> problem 
>> rather than trying a sticky plaster approach with automated restarts.  
>> Automated restarts are just the wrong way to go about this - believe me.
>>
>> Can you tell us your station type, install method and attach a log 
>> and/or config file and say what 

Re: [weewx-user] Re: Looking for a Weewx running script

[Mohamed Al Futtan]

Hi Andrew,

in case it would be run I should get this message when I try to start it:
"already running"

/etc/init.d/weewx start

* Starting weewx weather system weewx
 *  already running...
   ...done.

What I am calling a crash and I run

/etc/init.d/weewx start

I am getting, see below, so Weewx is not running and after the website is
getting

updates from the station

* Starting weewx weather system weewx
   ...done.






2018-05-24 16:46 GMT+07:00 Andrew Milner :

> I am sorry - this is NOT a crash.  Weewx is sill running and is trying and
> trying to reach your station.
>
> If you look closely at your log you will see it is logging try #1, try #2,
> try #3, try #4 and so forth.  This is not a crash - this is handling an
> error because it cannot communicate with the station.  Presumably your
> redirection is not yet up-to-date, so weewx cannot communicate with the
> station and must keep retrying.  There is nothi9ng else weewx can do until
> the connection is re-established via your redirection.
>
> Weewx is still running and trying to communicate with the station.  Why do
> you say it has crashed??
>
>
>
>
> On Thursday, 24 May 2018 12:15:09 UTC+3, Mike wrote:
>>
>> Dear Andrew,
>>
>> my Weewx is not running at this point, see the log file
>>
>> Right now it is running, If I try to start it I am getting:
>>
>> * Starting weewx weather system weewx
>>  *  already running...
>>...done.
>>
>> which is right.
>>
>> But before it was not running and it was crahing. I am pretty sure the 
>> Dedicated server with my Domain is getting the right IP.
>>
>> Any way, I have changed the wait time as you have suggested to 360 and 
>> restarted Weewx.
>>
>> Pls have a look again into my log file, I have seen 100 times the entry with 
>> the same date/time stamp. I think it is not normal too.
>>
>> May 24 00:19:11 sd-69780 weewx[1752]: vantage: Retry  #16 failed
>> May 24 00:19:11 sd-69780 weewx[1752]: vantage: ip-write error: [Errno 32] 
>> Broken pipe
>>
>>
>>
>> 2018-05-24 15:54 GMT+07:00 Andrew Milner :
>>
>>> since you seem to be using a non-static ip connection which may not be
>>> known for 5 minutes (30 secs) to the weather station have you tried
>>> increasing the wait time to say 6 minutes (360 secs) in weewx.conf
>>> (currently set to 180 secs).  I'm sure this is a question of tweeking the
>>> timeouts and retries to make weewx cater for the fact that the ip address
>>> of the station has altered.
>>>
>>> Of course, if you can give the station and host addresses on an internal
>>> network things would improve - but you don't give the hardware / network
>>> setup.
>>>
>>> I'm sure many people are running watchdog scripts of some kind though.
>>> Your issue does not appear to be a crash from the log segment you posted
>>> however - since weewx is definitely still trying to establish contact with
>>> the station - so weewx is doing the right things.
>>>
>>> Another VP user will know the answer to this - but it seems to me that
>>> from a theoretical viewpoint it would be better in your situation to have
>>> no loop records, hardware created archive records, and only poll the
>>> station once every archive interval to retrieve the latest rec - and ignore
>>> loop data.  This would have the effect of minimising the comms with the
>>> station ….but I do not know if this is possible or not.
>>>
>>>
>>> On Thursday, 24 May 2018 11:35:17 UTC+3, Mike wrote:

 Thanks for your quick response. I have no fixed IP from my ISP, my
 DynDNS IP is checked and updated every 5 minutes

 I am running a Davice Vantage Pro with WeatherLink IP

 As attached file the log and my conf file

 Thanks again

 2018-05-24 14:56 GMT+07:00 Andrew Milner :

> Weewx does not crash without a reason.  Believe me - it doesn't.
>
> What does the log have to say around the time of the crashes.  Fixing
> the cause of your crashes is the right way to go about fixing the problem
> rather than trying a sticky plaster approach with automated restarts.
> Automated restarts are just the wrong way to go about this - believe me.
>
> Can you tell us your station type, install method and attach a log
> and/or config file and say what skin(s) or extensions you are using.
>
> Then we can help you sort out your problems.
>
> If you are using a raspberry pi have you also checked the weewx wiki
> for advice on using weewx with a raspberry pi
>
>
> On Thursday, 24 May 2018 09:42:18 UTC+3, Mike wrote:
>>
>> Hi guys,
>>
>> my Weewx is crashing time by time.
>>
>> I am looking for a script which is checking the status of Weewx every
>> hour. In case Weewx was crashing the script is starting Weewx.
>>
>> My Linux knowledge is not the best at all. Looking like something: It
>> does not work.
>>
>> #!/bin/bash
>> #weewx 

Re: [weewx-user] Re: Looking for a Weewx running script

[Andrew Milner]

I am sorry - this is NOT a crash.  Weewx is sill running and is trying and 
trying to reach your station.

If you look closely at your log you will see it is logging try #1, try #2, 
try #3, try #4 and so forth.  This is not a crash - this is handling an 
error because it cannot communicate with the station.  Presumably your 
redirection is not yet up-to-date, so weewx cannot communicate with the 
station and must keep retrying.  There is nothi9ng else weewx can do until 
the connection is re-established via your redirection.

Weewx is still running and trying to communicate with the station.  Why do 
you say it has crashed??  




On Thursday, 24 May 2018 12:15:09 UTC+3, Mike wrote:
>
> Dear Andrew,
>
> my Weewx is not running at this point, see the log file
>
> Right now it is running, If I try to start it I am getting:
>
> * Starting weewx weather system weewx
>  *  already running...
>...done.
>
> which is right.
>
> But before it was not running and it was crahing. I am pretty sure the 
> Dedicated server with my Domain is getting the right IP.
>
> Any way, I have changed the wait time as you have suggested to 360 and 
> restarted Weewx.
>
> Pls have a look again into my log file, I have seen 100 times the entry with 
> the same date/time stamp. I think it is not normal too.
>
> May 24 00:19:11 sd-69780 weewx[1752]: vantage: Retry  #16 failed
> May 24 00:19:11 sd-69780 weewx[1752]: vantage: ip-write error: [Errno 32] 
> Broken pipe 
>
>
>
> 2018-05-24 15:54 GMT+07:00 Andrew Milner  >:
>
>> since you seem to be using a non-static ip connection which may not be 
>> known for 5 minutes (30 secs) to the weather station have you tried 
>> increasing the wait time to say 6 minutes (360 secs) in weewx.conf 
>> (currently set to 180 secs).  I'm sure this is a question of tweeking the 
>> timeouts and retries to make weewx cater for the fact that the ip address 
>> of the station has altered.
>>
>> Of course, if you can give the station and host addresses on an internal 
>> network things would improve - but you don't give the hardware / network 
>> setup.
>>
>> I'm sure many people are running watchdog scripts of some kind though.  
>> Your issue does not appear to be a crash from the log segment you posted 
>> however - since weewx is definitely still trying to establish contact with 
>> the station - so weewx is doing the right things.
>>
>> Another VP user will know the answer to this - but it seems to me that 
>> from a theoretical viewpoint it would be better in your situation to have 
>> no loop records, hardware created archive records, and only poll the 
>> station once every archive interval to retrieve the latest rec - and ignore 
>> loop data.  This would have the effect of minimising the comms with the 
>> station ….but I do not know if this is possible or not.
>>
>>
>> On Thursday, 24 May 2018 11:35:17 UTC+3, Mike wrote:
>>>
>>> Thanks for your quick response. I have no fixed IP from my ISP, my 
>>> DynDNS IP is checked and updated every 5 minutes
>>>
>>> I am running a Davice Vantage Pro with WeatherLink IP
>>>
>>> As attached file the log and my conf file
>>>
>>> Thanks again
>>>
>>> 2018-05-24 14:56 GMT+07:00 Andrew Milner :
>>>
 Weewx does not crash without a reason.  Believe me - it doesn't.

 What does the log have to say around the time of the crashes.  Fixing 
 the cause of your crashes is the right way to go about fixing the problem 
 rather than trying a sticky plaster approach with automated restarts.  
 Automated restarts are just the wrong way to go about this - believe me.

 Can you tell us your station type, install method and attach a log 
 and/or config file and say what skin(s) or extensions you are using.

 Then we can help you sort out your problems.

 If you are using a raspberry pi have you also checked the weewx wiki 
 for advice on using weewx with a raspberry pi


 On Thursday, 24 May 2018 09:42:18 UTC+3, Mike wrote:
>
> Hi guys,
>
> my Weewx is crashing time by time.
>
> I am looking for a script which is checking the status of Weewx every 
> hour. In case Weewx was crashing the script is starting Weewx.
>
> My Linux knowledge is not the best at all. Looking like something: It 
> does not work.
>
> #!/bin/bash
> #weewx check
> if ps x | grep -v grep | grep -v checkweewx.sh | grep -c weewx 
> >/dev/null
> then
> echo "weewx  ok"
> else
> echo ""
> date >> /etc/weewx/weewx.fail
> echo "weewx crashed ... restarting now" >> /usr/local/
> sleep 1
> /etc/init.d/weewx start
> fi
>
> Thanks
>
> -- 
 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/c3NEhifi_Ro/unsubscribe.
 To 

Re: [weewx-user] Re: Looking for a Weewx running script

[Mohamed Al Futtan]

Dear Andrew,

my Weewx is not running at this point, see the log file

Right now it is running, If I try to start it I am getting:

* Starting weewx weather system weewx
 *  already running...
   ...done.

which is right.

But before it was not running and it was crahing. I am pretty sure the
Dedicated server with my Domain is getting the right IP.

Any way, I have changed the wait time as you have suggested to 360 and
restarted Weewx.

Pls have a look again into my log file, I have seen 100 times the
entry with the same date/time stamp. I think it is not normal too.

May 24 00:19:11 sd-69780 weewx[1752]: vantage: Retry  #16 failed
May 24 00:19:11 sd-69780 weewx[1752]: vantage: ip-write error: [Errno
32] Broken pipe



2018-05-24 15:54 GMT+07:00 Andrew Milner :

> since you seem to be using a non-static ip connection which may not be
> known for 5 minutes (30 secs) to the weather station have you tried
> increasing the wait time to say 6 minutes (360 secs) in weewx.conf
> (currently set to 180 secs).  I'm sure this is a question of tweeking the
> timeouts and retries to make weewx cater for the fact that the ip address
> of the station has altered.
>
> Of course, if you can give the station and host addresses on an internal
> network things would improve - but you don't give the hardware / network
> setup.
>
> I'm sure many people are running watchdog scripts of some kind though.
> Your issue does not appear to be a crash from the log segment you posted
> however - since weewx is definitely still trying to establish contact with
> the station - so weewx is doing the right things.
>
> Another VP user will know the answer to this - but it seems to me that
> from a theoretical viewpoint it would be better in your situation to have
> no loop records, hardware created archive records, and only poll the
> station once every archive interval to retrieve the latest rec - and ignore
> loop data.  This would have the effect of minimising the comms with the
> station ….but I do not know if this is possible or not.
>
>
> On Thursday, 24 May 2018 11:35:17 UTC+3, Mike wrote:
>>
>> Thanks for your quick response. I have no fixed IP from my ISP, my DynDNS
>> IP is checked and updated every 5 minutes
>>
>> I am running a Davice Vantage Pro with WeatherLink IP
>>
>> As attached file the log and my conf file
>>
>> Thanks again
>>
>> 2018-05-24 14:56 GMT+07:00 Andrew Milner :
>>
>>> Weewx does not crash without a reason.  Believe me - it doesn't.
>>>
>>> What does the log have to say around the time of the crashes.  Fixing
>>> the cause of your crashes is the right way to go about fixing the problem
>>> rather than trying a sticky plaster approach with automated restarts.
>>> Automated restarts are just the wrong way to go about this - believe me.
>>>
>>> Can you tell us your station type, install method and attach a log
>>> and/or config file and say what skin(s) or extensions you are using.
>>>
>>> Then we can help you sort out your problems.
>>>
>>> If you are using a raspberry pi have you also checked the weewx wiki for
>>> advice on using weewx with a raspberry pi
>>>
>>>
>>> On Thursday, 24 May 2018 09:42:18 UTC+3, Mike wrote:

 Hi guys,

 my Weewx is crashing time by time.

 I am looking for a script which is checking the status of Weewx every
 hour. In case Weewx was crashing the script is starting Weewx.

 My Linux knowledge is not the best at all. Looking like something: It
 does not work.

 #!/bin/bash
 #weewx check
 if ps x | grep -v grep | grep -v checkweewx.sh | grep -c weewx
 >/dev/null
 then
 echo "weewx  ok"
 else
 echo ""
 date >> /etc/weewx/weewx.fail
 echo "weewx crashed ... restarting now" >> /usr/local/
 sleep 1
 /etc/init.d/weewx start
 fi

 Thanks

 --
>>> 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/to
>>> pic/weewx-user/c3NEhifi_Ro/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+...@googlegroups.com.
>>> 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/c3NEhifi_Ro/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.

Re: [weewx-user] Re: Looking for a Weewx running script

[Andrew Milner]

since you seem to be using a non-static ip connection which may not be 
known for 5 minutes (30 secs) to the weather station have you tried 
increasing the wait time to say 6 minutes (360 secs) in weewx.conf 
(currently set to 180 secs).  I'm sure this is a question of tweeking the 
timeouts and retries to make weewx cater for the fact that the ip address 
of the station has altered.

Of course, if you can give the station and host addresses on an internal 
network things would improve - but you don't give the hardware / network 
setup.

I'm sure many people are running watchdog scripts of some kind though.  
Your issue does not appear to be a crash from the log segment you posted 
however - since weewx is definitely still trying to establish contact with 
the station - so weewx is doing the right things.

Another VP user will know the answer to this - but it seems to me that from 
a theoretical viewpoint it would be better in your situation to have no 
loop records, hardware created archive records, and only poll the station 
once every archive interval to retrieve the latest rec - and ignore loop 
data.  This would have the effect of minimising the comms with the station 
….but I do not know if this is possible or not.


On Thursday, 24 May 2018 11:35:17 UTC+3, Mike wrote:
>
> Thanks for your quick response. I have no fixed IP from my ISP, my DynDNS 
> IP is checked and updated every 5 minutes
>
> I am running a Davice Vantage Pro with WeatherLink IP
>
> As attached file the log and my conf file
>
> Thanks again
>
> 2018-05-24 14:56 GMT+07:00 Andrew Milner  >:
>
>> Weewx does not crash without a reason.  Believe me - it doesn't.
>>
>> What does the log have to say around the time of the crashes.  Fixing the 
>> cause of your crashes is the right way to go about fixing the problem 
>> rather than trying a sticky plaster approach with automated restarts.  
>> Automated restarts are just the wrong way to go about this - believe me.
>>
>> Can you tell us your station type, install method and attach a log and/or 
>> config file and say what skin(s) or extensions you are using.
>>
>> Then we can help you sort out your problems.
>>
>> If you are using a raspberry pi have you also checked the weewx wiki for 
>> advice on using weewx with a raspberry pi
>>
>>
>> On Thursday, 24 May 2018 09:42:18 UTC+3, Mike wrote:
>>>
>>> Hi guys,
>>>
>>> my Weewx is crashing time by time.
>>>
>>> I am looking for a script which is checking the status of Weewx every 
>>> hour. In case Weewx was crashing the script is starting Weewx.
>>>
>>> My Linux knowledge is not the best at all. Looking like something: It 
>>> does not work.
>>>
>>> #!/bin/bash
>>> #weewx check
>>> if ps x | grep -v grep | grep -v checkweewx.sh | grep -c weewx >/dev/null
>>> then
>>> echo "weewx  ok"
>>> else
>>> echo ""
>>> date >> /etc/weewx/weewx.fail
>>> echo "weewx crashed ... restarting now" >> /usr/local/
>>> sleep 1
>>> /etc/init.d/weewx start
>>> fi
>>>
>>> Thanks
>>>
>>> -- 
>> 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/c3NEhifi_Ro/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@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.

Re: [weewx-user] Re: Looking for a Weewx running script

[Mohamed Al Futtan]

Thanks for your quick response. I have no fixed IP from my ISP, my DynDNS
IP is checked and updated every 5 minutes

I am running a Davice Vantage Pro with WeatherLink IP

As attached file the log and my conf file

Thanks again

2018-05-24 14:56 GMT+07:00 Andrew Milner :

> Weewx does not crash without a reason.  Believe me - it doesn't.
>
> What does the log have to say around the time of the crashes.  Fixing the
> cause of your crashes is the right way to go about fixing the problem
> rather than trying a sticky plaster approach with automated restarts.
> Automated restarts are just the wrong way to go about this - believe me.
>
> Can you tell us your station type, install method and attach a log and/or
> config file and say what skin(s) or extensions you are using.
>
> Then we can help you sort out your problems.
>
> If you are using a raspberry pi have you also checked the weewx wiki for
> advice on using weewx with a raspberry pi
>
>
> On Thursday, 24 May 2018 09:42:18 UTC+3, Mike wrote:
>>
>> Hi guys,
>>
>> my Weewx is crashing time by time.
>>
>> I am looking for a script which is checking the status of Weewx every
>> hour. In case Weewx was crashing the script is starting Weewx.
>>
>> My Linux knowledge is not the best at all. Looking like something: It
>> does not work.
>>
>> #!/bin/bash
>> #weewx check
>> if ps x | grep -v grep | grep -v checkweewx.sh | grep -c weewx >/dev/null
>> then
>> echo "weewx  ok"
>> else
>> echo ""
>> date >> /etc/weewx/weewx.fail
>> echo "weewx crashed ... restarting now" >> /usr/local/
>> sleep 1
>> /etc/init.d/weewx start
>> fi
>>
>> Thanks
>>
>> --
> 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/c3NEhifi_Ro/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.conf
Description: Binary data


weewy.log
Description: Binary data