Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have manage to make all works except forecast.
WU api doesn't work anymore so I tried OWM, but insted of OWM I get 
No forecast data for WU
And I have setup API key and this is what I have in log

Jun 18 09:32:49 povej weewx[32266]: forecast: MainThread: OWM: last 
forecast issued 2019-06-18 08:55:25 CEST (1560840925), requested 2019-06-18 
08:55:25 CEST (1560840925)
Jun 18 09:32:49 povej weewx[32266]: forecast: MainThread: OWM: 
interval=10800 max_age=604800 api_key=8d95 
location=26.1280,34.6124 fc=5day3hour
Jun 18 09:32:49 povej weewx[32266]: engine: Finished loading service 
user.forecast.OWMForecast



Dne torek, 18. junij 2019 09.30.29 UTC+2 je oseba Damjan Hajsek napisala:
>
>  thank you.
> Yes I remove sofaskin from those, that was just for testing.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/54814969-eb61-4497-b080-cdf63cdba6aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

 thank you.
Yes I remove sofaskin from those, that was just for testing.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/72cf01fb-94a9-4610-a07e-bb194a315add%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[gjr80]

That is  good news. 

As a little background, WeeWX 3.9.0 saw the smartphone and mobile pages pulled 
out of the Standard skin into their own skins named Smartphone and Mobile. 
These skins were not necessarily enabled for all users. You can enable them 
(and Standard too if it is not enabled), but make sure they are no longer set 
to run sofaskin.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e35e9aa6-983b-45af-bfa8-f9cfd9c1d6cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

yes that's it.
Thank you, now all works.

Just one question.
All those skins for, mobile, smartphone, etc. can be all enabled?


Dne ponedeljek, 17. junij 2019 21.58.37 UTC+2 je oseba vince napisala:
>
> On Monday, June 17, 2019 at 12:48:28 PM UTC-7, Damjan Hajsek wrote:
>>
>> In version 3.8.0 was only one settings for skin now there are 4.
>> I tried all and always the same error, no matter where I use sofaskin.
>> Now I have disabled all and also tried all now only this is enabled and 
>> doesn't work. below is log, reporting is on 3 minutes.
>> Web page doesn't update. https://vreme.povej.net
>>
>>  
>> Jun 17 21:40:35 povej weewx[4326]: cheetahgenerator: using search list 
>> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
>> 'user.forecast.ForecastVariables']
>> Jun 17 21:40:35 povej weewx[4326]: manager: Daily summary version is 2.0
>> Jun 17 21:40:35 povej weewx[4326]: reportengine: Caught unrecoverable 
>> exception in generator 'weewx.cheetahgenerator.CheetahGenerator'
>> Jun 17 21:40:35 povej weewx[4326]:  No module named forecast
>> Jun 17 21:40:35 povej weewx[4326]:  Traceback (most recent 
>> call last):
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weewx/reportengine.py", line 204, in run
>> Jun 17 21:40:35 povej weewx[4326]:  obj.start()
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weewx/reportengine.py", line 300, in start
>> Jun 17 21:40:35 povej weewx[4326]:  self.run()
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 157, in run
>> Jun 17 21:40:35 povej weewx[4326]:  
>> self.initExtensions(gen_dict[section_name])
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 199, in initExtensions
>> Jun 17 21:40:35 povej weewx[4326]:  class_ = 
>> weeutil.weeutil._get_object(x)
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weeutil/weeutil.py", line 1130, in _get_object
>> Jun 17 21:40:35 povej weewx[4326]:  mod = 
>> __import__(module)
>> Jun 17 21:40:35 povej weewx[4326]:  ImportError: No module 
>> named forecast
>> Jun 17 21:40:35 povej weewx[4326]:  Generator terminated
>>
>>
> The logs seem to say that you forgot to install the forecast extension.
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2aa538f3-a4e3-432d-aad8-d2b186ca61b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[vince]

On Monday, June 17, 2019 at 12:48:28 PM UTC-7, Damjan Hajsek wrote:
>
> In version 3.8.0 was only one settings for skin now there are 4.
> I tried all and always the same error, no matter where I use sofaskin.
> Now I have disabled all and also tried all now only this is enabled and 
> doesn't work. below is log, reporting is on 3 minutes.
> Web page doesn't update. https://vreme.povej.net
>
>  
> Jun 17 21:40:35 povej weewx[4326]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.forecast.ForecastVariables']
> Jun 17 21:40:35 povej weewx[4326]: manager: Daily summary version is 2.0
> Jun 17 21:40:35 povej weewx[4326]: reportengine: Caught unrecoverable 
> exception in generator 'weewx.cheetahgenerator.CheetahGenerator'
> Jun 17 21:40:35 povej weewx[4326]:  No module named forecast
> Jun 17 21:40:35 povej weewx[4326]:  Traceback (most recent 
> call last):
> Jun 17 21:40:35 povej weewx[4326]:File 
> "/usr/share/weewx/weewx/reportengine.py", line 204, in run
> Jun 17 21:40:35 povej weewx[4326]:  obj.start()
> Jun 17 21:40:35 povej weewx[4326]:File 
> "/usr/share/weewx/weewx/reportengine.py", line 300, in start
> Jun 17 21:40:35 povej weewx[4326]:  self.run()
> Jun 17 21:40:35 povej weewx[4326]:File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 157, in run
> Jun 17 21:40:35 povej weewx[4326]:  
> self.initExtensions(gen_dict[section_name])
> Jun 17 21:40:35 povej weewx[4326]:File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 199, in initExtensions
> Jun 17 21:40:35 povej weewx[4326]:  class_ = 
> weeutil.weeutil._get_object(x)
> Jun 17 21:40:35 povej weewx[4326]:File 
> "/usr/share/weewx/weeutil/weeutil.py", line 1130, in _get_object
> Jun 17 21:40:35 povej weewx[4326]:  mod = 
> __import__(module)
> Jun 17 21:40:35 povej weewx[4326]:  ImportError: No module 
> named forecast
> Jun 17 21:40:35 povej weewx[4326]:  Generator terminated
>
>
The logs seem to say that you forgot to install the forecast extension.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ae3c218f-b8a6-44fb-87bf-4fd2e6da819b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[gjr80]

OK, a few points. You have set each report under [StdReport] to use 
sofaskin, confusing but provided only one is enabled it should work. 
However, at the moment you have enable = false for all three, so none of 
them will generate. Finally, you have only shown us less than two minutes 
of your log, I don't know what archive interval you are using but if it's 
the usual 5 minutes then you need to show us a longer log extract so we can 
see a report cycle. I suggest you show us a log extract at least three 
times the length of your archive period, ie 15 minutes for a 5 minute 
archive period, 30 minutes for a 10 minute archive period.

Gary

On Monday, 17 June 2019 17:10:26 UTC+10, Damjan Hajsek wrote:
>
> error below is from wrong database, I tried to use old database from 3.8.0 
> but it looks like 3.9.1 have some changes in database.
> So I switch to original database and error is gone and all what I have in 
> log is this, but page doesn't update.
>
> Jun 17 09:06:50 povej weewx[2661]: interceptor: ServerThread: GET: 
> ID=ido10==25.0=21.6=21.0=21.6=59=96=0.0=0.0=224=979.5=1018.5=0.0=3.0=3.0=9.0=9.0=26215.0=952=2019-6-17
>  
> 7:6:50=WS-1002 V2.4.6=updateraw=1=5
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: raw data: 
> ID=ido10=np8xkt1j=25.0=21.6=21.0=21.6=59=96=0.0=0.0=224=979.5=1018.5=0.0=3.0=3.0=9.0=9.0=26215.0=952=2019-6-17
>  
> 7:6:50=WS-1002 V2.4.6=updateraw=1=5
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: using 
> rain_total 9.0 from yearlyrain
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: firmware 
> WS-1002 V2.4.6: baromin is barometer
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter weeklyrain=3.0
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter monthlyrain=9.0
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter realtime=1
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter rtfreq=5
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter action=updateraw
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter PASSWORD=
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter ID=ido10
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter softwaretype=WS-1002 V2.4.6
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter relbaro=1018.5
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: raw packet: 
> {'humidity_in': 59.0, 'wind_speed': 0.0, 'temperature_in': 25.0, 
> 'windchill': 21.6, 'dewpoint': 21.0, 'luminosity': 26215.0, 'humidity_out': 
> 96.0, 'uv': 952.0, 'radiation': 281.81125, 'rain': 0.0, 'dateTime': 
> 1560755210, 'pressure': 979.5, 'temperature_out': 21.6, 'wind_dir': 224.0, 
> 'rain_total': 9.0, 'rain_rate': 0.0, 'usUnits': 16, 'wind_gust': 0.0}
> Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: mapped packet: 
> {'windchill': 21.6, 'dewpoint': 21.0, 'pressure': 979.5, 'outHumidity': 
> 96.0, 'UV': 952.0, 'radiation': 281.81125, 'rain': 0.0, 'dateTime': 
> 1560755210, 'windDir': 224.0, 'outTemp': 21.6, 'windSpeed': 0.0, 
> 'inHumidity': 59.0, 'inTemp': 25.0, 'windGust': 0.0, 'rainRate': 0.0, 
> 'usUnits': 16}
> Jun 17 09:07:00 povej weewx[2661]: interceptor: MainThread: empty queue
> Jun 17 09:07:06 povej weewx[2661]: interceptor: ServerThread: GET: 
> ID=ido10==25.0=21.6=21.0=21.6=59=96=0.0=0.0=185=979.5=1018.5=0.0=3.0=3.0=9.0=9.0=26290.9=952=2019-6-17
>  
> 7:7:6=WS-1002 V2.4.6=updateraw=1=5
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: raw data: 
> ID=ido10=np8xkt1j=25.0=21.6=21.0=21.6=59=96=0.0=0.0=185=979.5=1018.5=0.0=3.0=3.0=9.0=9.0=26290.9=952=2019-6-17
>  
> 7:7:6=WS-1002 V2.4.6=updateraw=1=5
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: using 
> rain_total 9.0 from yearlyrain
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: firmware 
> WS-1002 V2.4.6: baromin is barometer
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter weeklyrain=3.0
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter monthlyrain=9.0
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter realtime=1
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter rtfreq=5
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter action=updateraw
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter PASSWORD=
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter ID=ido10
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter softwaretype=WS-1002 V2.4.6
> Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
> parameter relbaro=1018.5
> Jun 17 09:07:06 povej weewx[2661]: 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

error below is from wrong database, I tried to use old database from 3.8.0 
but it looks like 3.9.1 have some changes in database.
So I switch to original database and error is gone and all what I have in 
log is this, but page doesn't update.

Jun 17 09:06:50 povej weewx[2661]: interceptor: ServerThread: GET: 
ID=ido10==25.0=21.6=21.0=21.6=59=96=0.0=0.0=224=979.5=1018.5=0.0=3.0=3.0=9.0=9.0=26215.0=952=2019-6-17
 
7:6:50=WS-1002 V2.4.6=updateraw=1=5
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: raw data: 
ID=ido10=np8xkt1j=25.0=21.6=21.0=21.6=59=96=0.0=0.0=224=979.5=1018.5=0.0=3.0=3.0=9.0=9.0=26215.0=952=2019-6-17
 
7:6:50=WS-1002 V2.4.6=updateraw=1=5
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: using 
rain_total 9.0 from yearlyrain
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: firmware 
WS-1002 V2.4.6: baromin is barometer
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
parameter weeklyrain=3.0
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
parameter monthlyrain=9.0
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
parameter realtime=1
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
parameter rtfreq=5
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
parameter action=updateraw
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
parameter PASSWORD=
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
parameter ID=ido10
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
parameter softwaretype=WS-1002 V2.4.6
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: ignored 
parameter relbaro=1018.5
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: raw packet: 
{'humidity_in': 59.0, 'wind_speed': 0.0, 'temperature_in': 25.0, 
'windchill': 21.6, 'dewpoint': 21.0, 'luminosity': 26215.0, 'humidity_out': 
96.0, 'uv': 952.0, 'radiation': 281.81125, 'rain': 0.0, 'dateTime': 
1560755210, 'pressure': 979.5, 'temperature_out': 21.6, 'wind_dir': 224.0, 
'rain_total': 9.0, 'rain_rate': 0.0, 'usUnits': 16, 'wind_gust': 0.0}
Jun 17 09:06:50 povej weewx[2661]: interceptor: MainThread: mapped packet: 
{'windchill': 21.6, 'dewpoint': 21.0, 'pressure': 979.5, 'outHumidity': 
96.0, 'UV': 952.0, 'radiation': 281.81125, 'rain': 0.0, 'dateTime': 
1560755210, 'windDir': 224.0, 'outTemp': 21.6, 'windSpeed': 0.0, 
'inHumidity': 59.0, 'inTemp': 25.0, 'windGust': 0.0, 'rainRate': 0.0, 
'usUnits': 16}
Jun 17 09:07:00 povej weewx[2661]: interceptor: MainThread: empty queue
Jun 17 09:07:06 povej weewx[2661]: interceptor: ServerThread: GET: 
ID=ido10==25.0=21.6=21.0=21.6=59=96=0.0=0.0=185=979.5=1018.5=0.0=3.0=3.0=9.0=9.0=26290.9=952=2019-6-17
 
7:7:6=WS-1002 V2.4.6=updateraw=1=5
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: raw data: 
ID=ido10=np8xkt1j=25.0=21.6=21.0=21.6=59=96=0.0=0.0=185=979.5=1018.5=0.0=3.0=3.0=9.0=9.0=26290.9=952=2019-6-17
 
7:7:6=WS-1002 V2.4.6=updateraw=1=5
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: using 
rain_total 9.0 from yearlyrain
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: firmware 
WS-1002 V2.4.6: baromin is barometer
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
parameter weeklyrain=3.0
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
parameter monthlyrain=9.0
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
parameter realtime=1
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
parameter rtfreq=5
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
parameter action=updateraw
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
parameter PASSWORD=
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
parameter ID=ido10
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
parameter softwaretype=WS-1002 V2.4.6
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: ignored 
parameter relbaro=1018.5
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: raw packet: 
{'humidity_in': 59.0, 'wind_speed': 0.0, 'temperature_in': 25.0, 
'windchill': 21.6, 'dewpoint': 21.0, 'luminosity': 26290.9, 'humidity_out': 
96.0, 'uv': 952.0, 'radiation': 282.6271749997, 'rain': 0.0, 
'dateTime': 1560755226, 'pressure': 979.5, 'temperature_out': 21.6, 
'wind_dir': 185.0, 'rain_total': 9.0, 'rain_rate': 0.0, 'usUnits': 16, 
'wind_gust': 0.0}
Jun 17 09:07:06 povej weewx[2661]: interceptor: MainThread: mapped packet: 
{'windchill': 21.6, 'dewpoint': 21.0, 'pressure': 979.5, 'outHumidity': 
96.0, 'UV': 952.0, 'radiation': 282.6271749997, 'rain': 0.0, 
'dateTime': 1560755226, 'windDir': 185.0, 'outTemp': 21.6, 'windSpeed': 
0.0, 'inHumidity': 59.0, 'inTemp': 25.0, 'windGust': 0.0, 'rainRate': 0.0, 
'usUnits': 16}
Jun 17 09:07:16 povej weewx[2661]: interceptor: MainThread: empty queue
Jun 17 09:07:22 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have copied sofaskin into folder /etc/weewx/skins/sofaskin

end enable it in weewx.conf

#   This section specifies what reports, using which skins, to generate.

[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = /etc/weewx/skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Whether to log a successful operation
log_success = True

# Whether to log an unsuccessful operation
log_failure = False

# Each of the following subsections defines a report that will be run.
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and other
# customizations. Many of those changes can be made here by overriding
# parameters, or by modifying templates within the skin itself.

[[SeasonsReport]]
# The SeasonsReport uses the 'Seasons' skin, which contains the
# images, templates and plots for the report.
#skin = Seasons
skin = sofaskin
enable = false

[[SmartphoneReport]]
# The SmartphoneReport uses the 'Smartphone' skin, and the images 
and
# files are placed in a dedicated subdirectory.
#skin = Smartphone
skin = sofaskin
enable = false
HTML_ROOT = /var/www/html/weewx

[[MobileReport]]
# The MobileReport uses the 'Mobile' skin, and the images and files
# are placed in a dedicated subdirectory.
#skin = Mobile
skin = sofaskin
enable = false
HTML_ROOT = /var/www/html/weewx

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not enabled.
#skin = Standard
skin = Sofaskin
enable = true


this is in LOG.
Jun 17 07:59:54 povej weewx[31558]: interceptor: ServerThread: GET: 
ID=IDO10==25.0=19.6=19.5=19.6=59=99=0.0=0.0=242=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=21488.5=704=2019-6-17
 
5:59:54=WS-1002 V2.4.6=updateraw=1=5
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: raw data: 
ID=IDO10=np8xkt1j=25.0=19.6=19.5=19.6=59=99=0.0=0.0=242=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=21488.5=704=2019-6-17
 
5:59:54=WS-1002 V2.4.6=updateraw=1=5
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: using 
rain_total 9.0 from yearlyrain
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: firmware 
WS-1002 V2.4.6: baromin is barometer
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: ignored 
parameter weeklyrain=3.0
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: ignored 
parameter monthlyrain=9.0
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: ignored 
parameter realtime=1
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: ignored 
parameter rtfreq=5
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter action=updateraw
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter PASSWORD=
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter ID=IDO10
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter softwaretype=WS-1002 V2.4.6
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter relbaro=1018.6
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: raw packet: 
{'humidity_in': 59.0, 'wind_speed': 0.0, 'temperature_in': 25.0, 
'windchill': 19.6, 'dewpoint': 19.5, 'luminosity': 21488.5, 'humidity_out': 
99.0, 'uv': 704.0, 'radiation': 231.0013749997, 'rain': 0.0, 
'dateTime': 1560751194, 'pressure': 979.6, 'temperature_out': 19.6, 
'wind_dir': 242.0, 'rain_total': 9.0, 'rain_rate': 0.0, 'usUnits': 16, 
'wind_gust': 0.0}
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: mapped packet: 
{'windchill': 19.6, 'dewpoint': 19.5, 'pressure': 979.6, 'outHumidity': 
99.0, 'UV': 704.0, 'radiation': 231.0013749997, 'rain': 0.0, 
'dateTime': 1560751194, 'windDir': 242.0, 'outTemp': 19.6, 'windSpeed': 
0.0, 'inHumidity': 59.0, 'inTemp': 25.0, 'windGust': 0.0, 'rainRate': 0.0, 
'usUnits': 16}
Jun 17 08:00:05 povej weewx[31558]: interceptor: MainThread: empty queue
Jun 17 08:00:11 povej weewx[31558]: interceptor: ServerThread: GET: 
ID=IDO10==25.0=19.6=19.5=19.6=59=99=0.0=0.0=248=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=21426.4=705=2019-6-17
 
6:0:10=WS-1002 V2.4.6=updateraw=1=5
Jun 17 08:00:11 povej weewx[31558]: interceptor: MainThread: raw data: 
ID=IDO10=np8xkt1j=25.0=19.6=19.5=19.6=59=99=0.0=0.0=248=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=21426.4=705=2019-6-17
 
6:0:10=WS-1002 V2.4.6=updateraw=1=5
Jun 17 08:00:11 povej weewx[31558]: interceptor: MainThread: using 
rain_total 9.0 from yearlyrain
Jun 17 08:00:11 povej weewx[31558]: interceptor: MainThread: firmware 
WS-1002 V2.4.6: baromin is 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have copied sofaskin into folder /etc/weewx/skins/sofaskin

end enable it in weewx.conf

#   This section specifies what reports, using which skins, to generate.

[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = /etc/weewx/skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Whether to log a successful operation
log_success = True

# Whether to log an unsuccessful operation
log_failure = False

# Each of the following subsections defines a report that will be run.
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and other
# customizations. Many of those changes can be made here by overriding
# parameters, or by modifying templates within the skin itself.

[[SeasonsReport]]
# The SeasonsReport uses the 'Seasons' skin, which contains the
# images, templates and plots for the report.
#skin = Seasons
skin = sofaskin
enable = false

[[SmartphoneReport]]
# The SmartphoneReport uses the 'Smartphone' skin, and the images 
and
# files are placed in a dedicated subdirectory.
#skin = Smartphone
skin = sofaskin
enable = false
HTML_ROOT = /var/www/html/weewx

[[MobileReport]]
# The MobileReport uses the 'Mobile' skin, and the images and files
# are placed in a dedicated subdirectory.
#skin = Mobile
skin = sofaskin
enable = false
HTML_ROOT = /var/www/html/weewx

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not enabled.
#skin = Standard
skin = Sofaskin
enable = true


Dne nedelja, 16. junij 2019 22.17.46 UTC+2 je oseba gjr80 napisala:
>
> You say ‘whatever I do’ - exactly what have have you tried? Have you 
> restarted WeeWX? What does the log show when debug = 1? 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8558cce7-55ee-4fd3-98f4-41e34f1e4266%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[gjr80]

You say ‘whatever I do’ - exactly what have have you tried? Have you restarted 
WeeWX? What does the log show when debug = 1?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6794dec4-9c7d-4eb1-8788-ee407f8e80d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

One more thing.
In latest weewx.conf it is changed about skin.
I use sofaskin and whatever I do weewx doesn't want to use that skin.
I have change this line but weewx doesn't change skin.

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not enabled.
#skin = Standard
skin = Sofaskin
enable = true


Dne nedelja, 16. junij 2019 21.40.31 UTC+2 je oseba Damjan Hajsek napisala:
>
> thank you.
> I see data now it works.
>
>
> Dne nedelja, 16. junij 2019 14.21.58 UTC+2 je oseba mwall napisala:
>>
>> On Sunday, June 16, 2019 at 4:53:31 AM UTC-4, Damjan Hajsek wrote:
>>>
>>> I will try to find help with creator of driver. I see they had the same 
>>> problems before
>>>
>>
>> the problem is not the interceptor, it is your configuration.  you are 
>> listening on port 9900, but your station is not sending to that port
>>
>> to diagnose interceptor issues, you must first run the interceptor 
>> directly.  shut down weewx, then try something like this:
>>
>> sudo PYTHONPATH=/usr/share/weewx python 
>> /usr/share/weewx/user/interceptor.py --device=observer --mode=listen 
>> --port=80
>>
>> when you see data from that, put those settings into the [Interceptor] 
>> section of weewx configuration, then run weewx (still in debug mode)
>>
>> [Interceptor]
>> device_type = observer
>> mode = listen
>> port = 80
>>
>> m
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/996fc926-4f68-4d1c-817a-d91eaf0453e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

thank you.
I see data now it works.


Dne nedelja, 16. junij 2019 14.21.58 UTC+2 je oseba mwall napisala:
>
> On Sunday, June 16, 2019 at 4:53:31 AM UTC-4, Damjan Hajsek wrote:
>>
>> I will try to find help with creator of driver. I see they had the same 
>> problems before
>>
>
> the problem is not the interceptor, it is your configuration.  you are 
> listening on port 9900, but your station is not sending to that port
>
> to diagnose interceptor issues, you must first run the interceptor 
> directly.  shut down weewx, then try something like this:
>
> sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=observer --mode=listen 
> --port=80
>
> when you see data from that, put those settings into the [Interceptor] 
> section of weewx configuration, then run weewx (still in debug mode)
>
> [Interceptor]
> device_type = observer
> mode = listen
> port = 80
>
> m
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b23f0178-ad19-490b-8df8-824d48360bb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[mwall]

On Sunday, June 16, 2019 at 4:53:31 AM UTC-4, Damjan Hajsek wrote:
>
> I will try to find help with creator of driver. I see they had the same 
> problems before
>

the problem is not the interceptor, it is your configuration.  you are 
listening on port 9900, but your station is not sending to that port

to diagnose interceptor issues, you must first run the interceptor 
directly.  shut down weewx, then try something like this:

sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --device=observer --mode=listen 
--port=80

when you see data from that, put those settings into the [Interceptor] 
section of weewx configuration, then run weewx (still in debug mode)

[Interceptor]
device_type = observer
mode = listen
port = 80

m

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8756e525-d498-4b8a-bdc8-7864c9e2ad69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I will try to find help with creator of driver. I see they had the same 
problems before.

Dne nedelja, 16. junij 2019 10.47.32 UTC+2 je oseba Andrew Milner napisala:
>
> HOORAY - now we have real progress and debug messages at last!!
>
> However it now appears your interceptor driver is not receiving any data 
> at all.
>
> I cannot help here - you need an interceptor user but there does appear to 
> be a lot of debug/checking information back in the wiki to try and identify 
> problems when no dta is being received.
>
> Good luck and hope you resolve this finally!
>
>
>
> On Sunday, 16 June 2019 01:18:00 UTC+3, Damjan Hajsek wrote:
>>
>> Thank you.
>> Finally, I thought I was insane, trying everything.
>> I think some update must happend on april 4th when weewx stops to work.
>>
>> Now I have a log and this is all what I have for weewx.
>>
>> Jun 16 00:14:01 povej weewx: Starting weewx: [  V redu  ]
>> Jun 16 00:14:01 povej systemd: Started SYSV: start and stop the weewx 
>> weather system.
>> Jun 16 00:14:01 povej weewx[503]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Jun 16 00:14:01 povej weewx[503]: engine: Debug is 1
>> Jun 16 00:14:01 povej weewx[503]: engine: Initializing engine
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading station type 
>> Interceptor (user.interceptor)
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: driver version 
>> is 0.45
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: device type: 
>> observer
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: sensor map: 
>> None
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: mode is listen
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: listen on :9900
>> Jun 16 00:14:01 povej weewx[503]: interceptor: ServerThread: start tcp 
>> server
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdTimeSynch
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdTimeSynch
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdConvert
>> Jun 16 00:14:01 povej weewx[503]: engine: StdConvert target unit is 0x1
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdConvert
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdCalibrate
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdCalibrate
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdQC
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdQC
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.wxservices.StdWXCalculate
>> Jun 16 00:14:01 povej weewx[503]: wxcalculate: The following values will 
>> be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
>> rainRate=prefer_hardware, windrun=prefer_hardware, 
>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
>> humidex=prefer_hardware, pressure=prefer_hardware, 
>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
>> cloudbase=prefer_hardware
>> Jun 16 00:14:01 povej weewx[503]: wxcalculate: The following algorithms 
>> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.wxservices.StdWXCalculate
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdArchive
>> Jun 16 00:14:01 povej weewx[503]: engine: Archive will use data binding 
>> wx_binding
>> Jun 16 00:14:01 povej weewx[503]: engine: Record generation will be 
>> attempted in 'hardware'
>> Jun 16 00:14:01 povej weewx[503]: engine: Using archive interval of 60 
>> seconds (specified in weewx configuration)
>> Jun 16 00:14:01 povej weewx[503]: engine: Use LOOP data in hi/low 
>> calculations: 1
>> Jun 16 00:14:01 povej weewx[503]: manager: Daily summary version is 2.0
>> Jun 16 00:14:01 povej weewx[503]: engine: Using binding 'wx_binding' to 
>> database 'weewx'
>> Jun 16 00:14:01 povej weewx[503]: manager: Starting backfill of daily 
>> summaries
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdArchive
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.restx.StdStationRegistry
>> Jun 16 00:14:01 povej weewx[503]: restx: StationRegistry: Registration 
>> not requested.
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.restx.StdStationRegistry
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.restx.StdWunderground
>> Jun 16 00:14:01 povej weewx[503]: restx: WU essentials: {}
>> Jun 16 00:14:01 povej weewx[503]: restx: Wunderground-PWS: Data for 
>> station ido10 will be posted
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.restx.StdWunderground
>> Jun 16 00:14:01 

Re: [weewx-user] Re: weewx stop working

[Andrew Milner]

HOORAY - now we have real progress and debug messages at last!!

However it now appears your interceptor driver is not receiving any data at 
all.

I cannot help here - you need an interceptor user but there does appear to 
be a lot of debug/checking information back in the wiki to try and identify 
problems when no dta is being received.

Good luck and hope you resolve this finally!



On Sunday, 16 June 2019 01:18:00 UTC+3, Damjan Hajsek wrote:
>
> Thank you.
> Finally, I thought I was insane, trying everything.
> I think some update must happend on april 4th when weewx stops to work.
>
> Now I have a log and this is all what I have for weewx.
>
> Jun 16 00:14:01 povej weewx: Starting weewx: [  V redu  ]
> Jun 16 00:14:01 povej systemd: Started SYSV: start and stop the weewx 
> weather system.
> Jun 16 00:14:01 povej weewx[503]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Jun 16 00:14:01 povej weewx[503]: engine: Debug is 1
> Jun 16 00:14:01 povej weewx[503]: engine: Initializing engine
> Jun 16 00:14:01 povej weewx[503]: engine: Loading station type Interceptor 
> (user.interceptor)
> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: driver version 
> is 0.45
> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: device type: 
> observer
> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: sensor map: None
> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: mode is listen
> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: listen on :9900
> Jun 16 00:14:01 povej weewx[503]: interceptor: ServerThread: start tcp 
> server
> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
> weewx.engine.StdTimeSynch
> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
> weewx.engine.StdTimeSynch
> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
> weewx.engine.StdConvert
> Jun 16 00:14:01 povej weewx[503]: engine: StdConvert target unit is 0x1
> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
> weewx.engine.StdConvert
> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
> weewx.engine.StdCalibrate
> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
> weewx.engine.StdCalibrate
> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
> weewx.engine.StdQC
> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
> weewx.engine.StdQC
> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
> weewx.wxservices.StdWXCalculate
> Jun 16 00:14:01 povej weewx[503]: wxcalculate: The following values will 
> be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> cloudbase=prefer_hardware
> Jun 16 00:14:01 povej weewx[503]: wxcalculate: The following algorithms 
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
> weewx.wxservices.StdWXCalculate
> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
> weewx.engine.StdArchive
> Jun 16 00:14:01 povej weewx[503]: engine: Archive will use data binding 
> wx_binding
> Jun 16 00:14:01 povej weewx[503]: engine: Record generation will be 
> attempted in 'hardware'
> Jun 16 00:14:01 povej weewx[503]: engine: Using archive interval of 60 
> seconds (specified in weewx configuration)
> Jun 16 00:14:01 povej weewx[503]: engine: Use LOOP data in hi/low 
> calculations: 1
> Jun 16 00:14:01 povej weewx[503]: manager: Daily summary version is 2.0
> Jun 16 00:14:01 povej weewx[503]: engine: Using binding 'wx_binding' to 
> database 'weewx'
> Jun 16 00:14:01 povej weewx[503]: manager: Starting backfill of daily 
> summaries
> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
> weewx.engine.StdArchive
> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
> weewx.restx.StdStationRegistry
> Jun 16 00:14:01 povej weewx[503]: restx: StationRegistry: Registration not 
> requested.
> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
> weewx.restx.StdStationRegistry
> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
> weewx.restx.StdWunderground
> Jun 16 00:14:01 povej weewx[503]: restx: WU essentials: {}
> Jun 16 00:14:01 povej weewx[503]: restx: Wunderground-PWS: Data for 
> station ido10 will be posted
> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
> weewx.restx.StdWunderground
> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
> weewx.restx.StdPWSweather
> Jun 16 00:14:01 povej weewx[503]: restx: PWSweather: Posting not enabled.
> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
> weewx.restx.StdPWSweather
> Jun 16 00:14:01 povej weewx[503]: 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Thank you.
Finally, I thought I was insane, trying everything.
I think some update must happend on april 4th when weewx stops to work.

Now I have a log and this is all what I have for weewx.

Jun 16 00:14:01 povej weewx: Starting weewx: [  V redu  ]
Jun 16 00:14:01 povej systemd: Started SYSV: start and stop the weewx 
weather system.
Jun 16 00:14:01 povej weewx[503]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jun 16 00:14:01 povej weewx[503]: engine: Debug is 1
Jun 16 00:14:01 povej weewx[503]: engine: Initializing engine
Jun 16 00:14:01 povej weewx[503]: engine: Loading station type Interceptor 
(user.interceptor)
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: driver version 
is 0.45
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: device type: 
observer
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: sensor map: None
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: mode is listen
Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: listen on :9900
Jun 16 00:14:01 povej weewx[503]: interceptor: ServerThread: start tcp 
server
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.engine.StdTimeSynch
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.engine.StdConvert
Jun 16 00:14:01 povej weewx[503]: engine: StdConvert target unit is 0x1
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.engine.StdConvert
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.engine.StdCalibrate
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.engine.StdCalibrate
Jun 16 00:14:01 povej weewx[503]: engine: Loading service weewx.engine.StdQC
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.engine.StdQC
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Jun 16 00:14:01 povej weewx[503]: wxcalculate: The following values will be 
calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Jun 16 00:14:01 povej weewx[503]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.engine.StdArchive
Jun 16 00:14:01 povej weewx[503]: engine: Archive will use data binding 
wx_binding
Jun 16 00:14:01 povej weewx[503]: engine: Record generation will be 
attempted in 'hardware'
Jun 16 00:14:01 povej weewx[503]: engine: Using archive interval of 60 
seconds (specified in weewx configuration)
Jun 16 00:14:01 povej weewx[503]: engine: Use LOOP data in hi/low 
calculations: 1
Jun 16 00:14:01 povej weewx[503]: manager: Daily summary version is 2.0
Jun 16 00:14:01 povej weewx[503]: engine: Using binding 'wx_binding' to 
database 'weewx'
Jun 16 00:14:01 povej weewx[503]: manager: Starting backfill of daily 
summaries
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.engine.StdArchive
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.restx.StdStationRegistry
Jun 16 00:14:01 povej weewx[503]: restx: StationRegistry: Registration not 
requested.
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.restx.StdWunderground
Jun 16 00:14:01 povej weewx[503]: restx: WU essentials: {}
Jun 16 00:14:01 povej weewx[503]: restx: Wunderground-PWS: Data for station 
ido10 will be posted
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.restx.StdWunderground
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.restx.StdPWSweather
Jun 16 00:14:01 povej weewx[503]: restx: PWSweather: Posting not enabled.
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.restx.StdPWSweather
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.restx.StdCWOP
Jun 16 00:14:01 povej weewx[503]: restx: CWOP: Posting not enabled.
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.restx.StdCWOP
Jun 16 00:14:01 povej weewx[503]: engine: Loading service weewx.restx.StdWOW
Jun 16 00:14:01 povej weewx[503]: restx: WOW: Posting not enabled.
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.restx.StdWOW
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.restx.StdAWEKAS
Jun 16 00:14:01 povej weewx[503]: restx: AWEKAS: Posting not enabled.
Jun 16 00:14:01 povej weewx[503]: engine: Finished 

Re: [weewx-user] Re: weewx stop working

[Leon Shaner]

FYI, on all RH/Fedora (including CantOS) there are multiple consoles, which can 
be accessed by pressing CTRL-ALT 1 thru =.

IIRC the debug messages go to console 12, the last one behind CRTL-ALT =, but 
having them in a file is preferred in my book.

So, good job! =D

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPhone)

> On Jun 15, 2019, at 11:09 AM, gjr80  wrote:
> 
> Thanks, so if I am reading the centos7.6 /etc/rsyslog.conf correctly only 
> info and above go to /var/log/messages. There is nothing covering debug at 
> all so I expect that is why debug is (effectively) discarded. We could send 
> them to another file but that will make debugging difficult so let's just 
> send debug to /var/log/messages as well.
> 
> Damjan. Try the following:
> 
> 1. edit /etc/rsyslog.conf and add the following to the bottom of the file 
> (you will need privileged access to edit the file):
> 
> # all debug to /var/log/messages
> *.=debug /var/log/messages
> 
> 2. restart rsyslog:
> 
> $ sudo systemctl restart rsyslog
> 
> 3. make sure /etc/weewx/weewx.conf has debug=1
> 
> 4. restart WeeWX:
> 
> $ sudo systemctl restart weewx
> 
> check /var/log/messages and you should see some debug output.
> 
> Gary
> 
>> On Sunday, 16 June 2019 00:36:45 UTC+10, Leon Shaner wrote:
>> Gary, good sleuthing.
>> 
>> Could it be that the debug messages simply go to a different file, such as 
>> /var/log/debug?
>> 
>> Check to see where the debug logs are pointed in /etc/rsyslog.conf.
>> 
>> Also, see here:
>> 
>> https://www.the-art-of-web.com/system/rsyslog-config/
>> 
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPhone)
>> 
>>> On Jun 15, 2019, at 10:19 AM, gjr80  wrote:
>>> 
>>> I guess the question is where to from here given that it appears you cannot 
>>> get any debug output when running under centos7.6. I think we can assume 
>>> that your system is running properly (debug issue aside) with the simulator 
>>> driver. Troubleshooting the interceptor driver is going to be difficult 
>>> without any debug output. One thing I did notice, some time ago Matthew 
>>> suggested running WeeWX (with the interceptor driver) directly. You could 
>>> try that again, remember what we are seeking when running WeeWX directly is 
>>> not the log output but rather the console output, ie what you see on the 
>>> screen. I notice you don't appear to have provided the console output, 
>>> rather you gave the log output.
>>> 
>>> Gary
>>> 
 On Saturday, 15 June 2019 02:28:14 UTC+10, Damjan Hajsek wrote:
 Ok I did logs again I hope this time better.
 
 
 Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
> 
> Not really, no
> 
> The first part appears to show normal running with archive records every 
> minute - but no log for the startup process
> 
> The second part, manual running , shows us the startup but only loop data 
> - it runs for under a minute so does not give the coverage for two 
> archive periods (which in your case would be at least 2 minutes)
> 
> The third part says debug disabled - but there does not appear to be any 
> section where debug is enabled - so it is not clear if you are enabling 
> debug correctly or not.
> 
> it is much better to just attach the logfile directly rather than trying 
> to extract relevant portions.  you can identify sections by the 
> timestamps of when you did things
> 
> we are making slow progress - but have yet to see debug successfully 
> enabled!!  However, simulator does appear to be OK - and indeed the 
> website confirms that simulator is running just fine.
> 
> See if you can get us some log which shows debug enabled at startup!!
> 
> 
> 
> 
> 
>> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:
>> here it is.
>> Is this ok what I attach?
>> regards
>> 
>> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:
>>> 
>>> Keep running the simulator for a while, but can you now give us the log 
>>> from startup for at least two archive intervals FOR SIMULATOR so that 
>>> we can be SURE everything is working as it should be.  Then, if that 
>>> looks ok, can you stop weewx, set debug = 1, restart weewx and again 
>>> attach the log from startup until at least two archive intervals.  This 
>>> should show that all is ok with debug also!!
>>> 
>>>  
>>> 
 On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
 https://github.com/matthewwall/weewx-interceptor
 
  this is what I have for interceptor in weewx.conf
 
 [Interceptor]
 # This section is for the network traffic interceptor driver.
 
 # The driver to use:
 driver = user.interceptor
 
 # Specify the hardware device to 

Re: [weewx-user] Re: weewx stop working

[vince]

On Saturday, June 15, 2019 at 8:09:28 AM UTC-7, gjr80 wrote:
>
> Thanks, so if I am reading the centos7.6 /etc/rsyslog.conf correctly only 
> info and above go to /var/log/messages. There is nothing covering debug 
> at all so I expect that is why debug is (effectively) discarded. We could 
> send them to another file but that will make debugging difficult so let's 
> just send debug to /var/log/messages as well.
>


I've verified Gary's solution.

In a vagrant VM, I added a *.debug line pointing to a different file, and 
after restarting syslog and weewx I 'do' see debug output in the second 
file.   The original non-debug output also goes to /var/log/messages as 
expected.

*.info;mail.none;authpriv.none;cron.none/var/log/messages
*.debug 
/var/log/messages.debug


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/52725735-fd4b-4a80-a8ee-2e64066066d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[gjr80]

Thanks, so if I am reading the centos7.6 /etc/rsyslog.conf correctly only 
info and above go to /var/log/messages. There is nothing covering debug at 
all so I expect that is why debug is (effectively) discarded. We could send 
them to another file but that will make debugging difficult so let's just 
send debug to /var/log/messages as well.

Damjan. Try the following:

1. edit /etc/rsyslog.conf and add the following to the bottom of the file 
(you will need privileged access to edit the file):

# all debug to /var/log/messages
*.=debug /var/log/messages

2. restart rsyslog:

$ sudo systemctl restart rsyslog

3. make sure /etc/weewx/weewx.conf has debug=1

4. restart WeeWX:

$ sudo systemctl restart weewx

check /var/log/messages and you should see some debug output.

Gary

On Sunday, 16 June 2019 00:36:45 UTC+10, Leon Shaner wrote:
>
> Gary, good sleuthing.
>
> Could it be that the debug messages simply go to a different file, such as 
> /var/log/debug?
>
> Check to see where the debug logs are pointed in /etc/rsyslog.conf.
>
> Also, see here:
>
> https://www.the-art-of-web.com/system/rsyslog-config/
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPhone)
>
> On Jun 15, 2019, at 10:19 AM, gjr80 > 
> wrote:
>
> I guess the question is where to from here given that it appears you 
> cannot get any debug output when running under centos7.6. I think we can 
> assume that your system is running properly (debug issue aside) with the 
> simulator driver. Troubleshooting the interceptor driver is going to be 
> difficult without any debug output. One thing I did notice, some time ago 
> Matthew suggested running WeeWX (with the interceptor driver) directly. You 
> could try that again, remember what we are seeking when running WeeWX 
> directly is not the log output but rather the console output, ie what you 
> see on the screen. I notice you don't appear to have provided the console 
> output, rather you gave the log output.
>
> Gary
>
> On Saturday, 15 June 2019 02:28:14 UTC+10, Damjan Hajsek wrote:
>>
>> Ok I did logs again I hope this time better.
>>
>>
>> Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
>>>
>>> Not really, no
>>>
>>> The first part appears to show normal running with archive records every 
>>> minute - but no log for the startup process
>>>
>>> The second part, manual running , shows us the startup but only loop 
>>> data - it runs for under a minute so does not give the coverage for two 
>>> archive periods (which in your case would be at least 2 minutes)
>>>
>>> The third part says debug disabled - but there does not appear to be any 
>>> section where debug is enabled - so it is not clear if you are enabling 
>>> debug correctly or not.
>>>
>>> it is much better to just attach the logfile directly rather than trying 
>>> to extract relevant portions.  you can identify sections by the timestamps 
>>> of when you did things
>>>
>>> we are making slow progress - but have yet to see debug successfully 
>>> enabled!!  However, simulator does appear to be OK - and indeed the website 
>>> confirms that simulator is running just fine.
>>>
>>> See if you can get us some log which shows debug enabled at startup!!
>>>
>>>
>>>
>>>
>>>
>>> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:

 here it is.
 Is this ok what I attach?
 regards

 Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner 
 napisala:
>
> Keep running the simulator for a while, but can you now give us the 
> log from startup for at least two archive intervals FOR SIMULATOR so that 
> we can be SURE everything is working as it should be.  Then, if that 
> looks 
> ok, can you stop weewx, set debug = 1, restart weewx and again attach the 
> log from startup until at least two archive intervals.  This should show 
> that all is ok with debug also!!
>
>  
>
> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>>
>> https://github.com/matthewwall/weewx-interceptor
>>
>>  this is what I have for interceptor in weewx.conf
>>
>> [Interceptor]
>> # This section is for the network traffic interceptor driver.
>> 
>> # The driver to use:
>> driver = user.interceptor
>> 
>> # Specify the hardware device to capture.  Options include:
>> #   acurite-bridge - acurite internet bridge, smarthub, or access
>> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
>> #   lw30x - oregon scientific LW301/LW302
>> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>> #   wu-client - any hardware that uses the weather underground 
>> protocol
>> #device_type = acurite-bridge
>> device_type = observer
>> port = 990
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" 

Re: [weewx-user] Re: weewx stop working

[Leon Shaner]

Gary, good sleuthing.

Could it be that the debug messages simply go to a different file, such as 
/var/log/debug?

Check to see where the debug logs are pointed in /etc/rsyslog.conf.

Also, see here:

https://www.the-art-of-web.com/system/rsyslog-config/

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPhone)

> On Jun 15, 2019, at 10:19 AM, gjr80  wrote:
> 
> I guess the question is where to from here given that it appears you cannot 
> get any debug output when running under centos7.6. I think we can assume that 
> your system is running properly (debug issue aside) with the simulator 
> driver. Troubleshooting the interceptor driver is going to be difficult 
> without any debug output. One thing I did notice, some time ago Matthew 
> suggested running WeeWX (with the interceptor driver) directly. You could try 
> that again, remember what we are seeking when running WeeWX directly is not 
> the log output but rather the console output, ie what you see on the screen. 
> I notice you don't appear to have provided the console output, rather you 
> gave the log output.
> 
> Gary
> 
>> On Saturday, 15 June 2019 02:28:14 UTC+10, Damjan Hajsek wrote:
>> Ok I did logs again I hope this time better.
>> 
>> 
>> Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
>>> 
>>> Not really, no
>>> 
>>> The first part appears to show normal running with archive records every 
>>> minute - but no log for the startup process
>>> 
>>> The second part, manual running , shows us the startup but only loop data - 
>>> it runs for under a minute so does not give the coverage for two archive 
>>> periods (which in your case would be at least 2 minutes)
>>> 
>>> The third part says debug disabled - but there does not appear to be any 
>>> section where debug is enabled - so it is not clear if you are enabling 
>>> debug correctly or not.
>>> 
>>> it is much better to just attach the logfile directly rather than trying to 
>>> extract relevant portions.  you can identify sections by the timestamps of 
>>> when you did things
>>> 
>>> we are making slow progress - but have yet to see debug successfully 
>>> enabled!!  However, simulator does appear to be OK - and indeed the website 
>>> confirms that simulator is running just fine.
>>> 
>>> See if you can get us some log which shows debug enabled at startup!!
>>> 
>>> 
>>> 
>>> 
>>> 
 On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:
 here it is.
 Is this ok what I attach?
 regards
 
 Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:
> 
> Keep running the simulator for a while, but can you now give us the log 
> from startup for at least two archive intervals FOR SIMULATOR so that we 
> can be SURE everything is working as it should be.  Then, if that looks 
> ok, can you stop weewx, set debug = 1, restart weewx and again attach the 
> log from startup until at least two archive intervals.  This should show 
> that all is ok with debug also!!
> 
>  
> 
>> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>> https://github.com/matthewwall/weewx-interceptor
>> 
>>  this is what I have for interceptor in weewx.conf
>> 
>> [Interceptor]
>> # This section is for the network traffic interceptor driver.
>> 
>> # The driver to use:
>> driver = user.interceptor
>> 
>> # Specify the hardware device to capture.  Options include:
>> #   acurite-bridge - acurite internet bridge, smarthub, or access
>> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
>> #   lw30x - oregon scientific LW301/LW302
>> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>> #   wu-client - any hardware that uses the weather underground 
>> protocol
>> #device_type = acurite-bridge
>> device_type = observer
>> port = 990
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/2dc29325-db15-4831-899a-f256e2c024b4%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/AD3FDEC5-6CF4-4A58-9132-D1D9EE55BC44%40isylum.org.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[gjr80]

I guess the question is where to from here given that it appears you cannot 
get any debug output when running under centos7.6. I think we can assume 
that your system is running properly (debug issue aside) with the simulator 
driver. Troubleshooting the interceptor driver is going to be difficult 
without any debug output. One thing I did notice, some time ago Matthew 
suggested running WeeWX (with the interceptor driver) directly. You could 
try that again, remember what we are seeking when running WeeWX directly is 
not the log output but rather the console output, ie what you see on the 
screen. I notice you don't appear to have provided the console output, 
rather you gave the log output.

Gary

On Saturday, 15 June 2019 02:28:14 UTC+10, Damjan Hajsek wrote:
>
> Ok I did logs again I hope this time better.
>
>
> Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
>>
>> Not really, no
>>
>> The first part appears to show normal running with archive records every 
>> minute - but no log for the startup process
>>
>> The second part, manual running , shows us the startup but only loop data 
>> - it runs for under a minute so does not give the coverage for two archive 
>> periods (which in your case would be at least 2 minutes)
>>
>> The third part says debug disabled - but there does not appear to be any 
>> section where debug is enabled - so it is not clear if you are enabling 
>> debug correctly or not.
>>
>> it is much better to just attach the logfile directly rather than trying 
>> to extract relevant portions.  you can identify sections by the timestamps 
>> of when you did things
>>
>> we are making slow progress - but have yet to see debug successfully 
>> enabled!!  However, simulator does appear to be OK - and indeed the website 
>> confirms that simulator is running just fine.
>>
>> See if you can get us some log which shows debug enabled at startup!!
>>
>>
>>
>>
>>
>> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:
>>>
>>> here it is.
>>> Is this ok what I attach?
>>> regards
>>>
>>> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:

 Keep running the simulator for a while, but can you now give us the log 
 from startup for at least two archive intervals FOR SIMULATOR so that we 
 can be SURE everything is working as it should be.  Then, if that looks 
 ok, 
 can you stop weewx, set debug = 1, restart weewx and again attach the log 
 from startup until at least two archive intervals.  This should show that 
 all is ok with debug also!!

  

 On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>
> https://github.com/matthewwall/weewx-interceptor
>
>  this is what I have for interceptor in weewx.conf
>
> [Interceptor]
> # This section is for the network traffic interceptor driver.
> 
> # The driver to use:
> driver = user.interceptor
> 
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge, smarthub, or access
> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> #   wu-client - any hardware that uses the weather underground 
> protocol
> #device_type = acurite-bridge
> device_type = observer
> port = 990
>


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2dc29325-db15-4831-899a-f256e2c024b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[gjr80]

Well installing centos 7.6 on a VM was interesting. WeeWX 3.9.1 was 
installed from .rpm. It seems that when run under centos7.6 WeeWX (and 
python) any attempts to log at the debug level are discarded or otherwise 
lost. With debug=1:

[root@VBCentosMaster ~]# cat /etc/weewx/weewx.conf|more
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.1


starting WeeWX gives:

Jun 16 00:06:28 localhost systemd: Starting SYSV: start and stop the weewx 
weather system...
Jun 16 00:06:28 localhost weewx[7392]: engine: Initializing weewx version 
3.9.1
Jun 16 00:06:28 localhost weewx[7392]: engine: Using Python 2.7.5 (default, 
Apr  9 2019, 14:30:50) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
Jun 16 00:06:28 localhost weewx[7392]: engine: Platform Linux-3.10.0-
957.el7.x86_64-x86_64-with-centos-7.6.1810-Core
Jun 16 00:06:28 localhost weewx[7392]: engine: Locale is 'en_AU.UTF-8'
Jun 16 00:06:28 localhost weewx[7392]: engine: pid file is /var/run/weewx.
pid
Jun 16 00:06:28 localhost weewx: Starting weewx: [  OK  ]
Jun 16 00:06:28 localhost systemd: Started SYSV: start and stop the weewx 
weather system.
Jun 16 00:06:28 localhost weewx[7397]: engine: Using configuration file /etc
/weewx/weewx.conf
Jun 16 00:06:28 localhost weewx[7397]: engine: Loading station type 
Simulator (weewx.drivers.simulator)
Jun 16 00:06:28 localhost weewx[7397]: engine: StdConvert target unit is 0x1
Jun 16 00:06:28 localhost weewx[7397]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, maxSolarRad=
prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Jun 16 00:06:28 localhost weewx[7397]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun 16 00:06:28 localhost weewx[7397]: engine: Archive will use data 
binding wx_binding
Jun 16 00:06:28 localhost weewx[7397]: engine: Record generation will be 
attempted in 'hardware'
Jun 16 00:06:28 localhost weewx[7397]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Jun 16 00:06:28 localhost weewx[7397]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'
Jun 16 00:06:28 localhost weewx[7397]: manager: Starting backfill of daily 
summaries
Jun 16 00:06:28 localhost weewx[7397]: restx: StationRegistry: Registration 
not requested.
Jun 16 00:06:28 localhost weewx[7397]: restx: Wunderground: Posting not 
enabled.
Jun 16 00:06:28 localhost weewx[7397]: restx: PWSweather: Posting not 
enabled.
Jun 16 00:06:28 localhost weewx[7397]: restx: CWOP: Posting not enabled.
Jun 16 00:06:28 localhost weewx[7397]: restx: WOW: Posting not enabled.
Jun 16 00:06:28 localhost weewx[7397]: restx: AWEKAS: Posting not enabled.
Jun 16 00:06:28 localhost weewx[7397]: engine: Starting up weewx version 3.9
.1
Jun 16 00:06:28 localhost weewx[7397]: engine: Clock error is -0.02 seconds 
(positive is fast)
Jun 16 00:06:28 localhost weewx[7397]: engine: Starting main packet loop.

WeeWX appears to otherwise run properly it just cannot log at the debug 
level. Opening a python console importing syslog and doing a few syslog 
calls produced the same result, anything at LOG_DEBUG was ignored.

Not sure where the issue lies, probably needs someone with a better 
understanding of rsyslog than me. Makes me wonder if given centos' 
parentage whether RH will be the same. Enough for me, I hurt my brain 
enough battling with centos, will be glad to get back to debian.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/048923b3-9094-4717-8a07-c9d1552e4372%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Thank you.
I use shorewall on my server and I have locked it on my home IP where 
weather station is.
also fail2ban have my home IP whitelisted


Dne petek, 14. junij 2019 18.52.23 UTC+2 je oseba Leon Shaner napisala:
>
> Damjan,
> A long time ago you mentioned that your troubles all started when you 
> updated some OS pkgs.
> Have you seen this thread?  Since you are using interceptor, which must 
> accept connections from remote, it could be relevant:
>
> https://www.centos.org/forums/viewtopic.php?t=69009
>
> To rule it out, perhaps you could temporarily disable firewalld and 
> fail2ban?
>
> $ sudo systemctl disable firewalld
> $ sudo systemctl stop firewalld
>
> $ sudo systemctl disable fail2ban
> $ sudo systemctl stop fail2ban
>
> If disabling those helps with weewx, then you may need to explicitly add 
> rules for interceptor on 990 to be allowed, that way you can have the 
> benefit of those firewalls without breaking weewx.
>
> In the meantime you probably want to "enable" and "start" them so your 
> system isn't left vulnerable.
>
> Lemme know if disabling those helps and then I can dig out the proper 
> syntax to add a rule to allow interceptor to connect even with firewalld 
> active.   It may still not work, though, depending on the outcome of that 
> thread mentioned far above.  That last comment calls an an issue for people 
> upgrading from CentOS 7.5 to 7.6, but doesn't explicitly say how he got it 
> working again.  :-/
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
> On Jun 14, 2019, at 12:28 PM, Damjan Hajsek  > wrote:
>
> 
> Ok I did logs again I hope this time better.
>
>
> Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
>>
>> Not really, no
>>
>> The first part appears to show normal running with archive records every 
>> minute - but no log for the startup process
>>
>> The second part, manual running , shows us the startup but only loop data 
>> - it runs for under a minute so does not give the coverage for two archive 
>> periods (which in your case would be at least 2 minutes)
>>
>> The third part says debug disabled - but there does not appear to be any 
>> section where debug is enabled - so it is not clear if you are enabling 
>> debug correctly or not.
>>
>> it is much better to just attach the logfile directly rather than trying 
>> to extract relevant portions.  you can identify sections by the timestamps 
>> of when you did things
>>
>> we are making slow progress - but have yet to see debug successfully 
>> enabled!!  However, simulator does appear to be OK - and indeed the website 
>> confirms that simulator is running just fine.
>>
>> See if you can get us some log which shows debug enabled at startup!!
>>
>>
>>
>>
>>
>> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:
>>>
>>> here it is.
>>> Is this ok what I attach?
>>> regards
>>>
>>> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:

 Keep running the simulator for a while, but can you now give us the log 
 from startup for at least two archive intervals FOR SIMULATOR so that we 
 can be SURE everything is working as it should be.  Then, if that looks 
 ok, 
 can you stop weewx, set debug = 1, restart weewx and again attach the log 
 from startup until at least two archive intervals.  This should show that 
 all is ok with debug also!!

  

 On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>
> https://github.com/matthewwall/weewx-interceptor
>
>  this is what I have for interceptor in weewx.conf
>
> [Interceptor]
> # This section is for the network traffic interceptor driver.
> 
> # The driver to use:
> driver = user.interceptor
> 
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge, smarthub, or access
> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> #   wu-client - any hardware that uses the weather underground 
> protocol
> #device_type = acurite-bridge
> device_type = observer
> port = 990
>
 -- 
> 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/57255078-0935-48db-b1c3-2ce7813b488a%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
>
>

-- 
You received this message because you are subscribed to the Google 

Re: [weewx-user] Re: weewx stop working

[Leon Shaner]

Damjan,
A long time ago you mentioned that your troubles all started when you updated 
some OS pkgs.
Have you seen this thread?  Since you are using interceptor, which must accept 
connections from remote, it could be relevant:

https://www.centos.org/forums/viewtopic.php?t=69009

To rule it out, perhaps you could temporarily disable firewalld and fail2ban?

$ sudo systemctl disable firewalld
$ sudo systemctl stop firewalld

$ sudo systemctl disable fail2ban
$ sudo systemctl stop fail2ban

If disabling those helps with weewx, then you may need to explicitly add rules 
for interceptor on 990 to be allowed, that way you can have the benefit of 
those firewalls without breaking weewx.

In the meantime you probably want to "enable" and "start" them so your system 
isn't left vulnerable.

Lemme know if disabling those helps and then I can dig out the proper syntax to 
add a rule to allow interceptor to connect even with firewalld active.   It may 
still not work, though, depending on the outcome of that thread mentioned far 
above.  That last comment calls an an issue for people upgrading from CentOS 
7.5 to 7.6, but doesn't explicitly say how he got it working again.  :-/

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad)

> On Jun 14, 2019, at 12:28 PM, Damjan Hajsek  wrote:
> 
> 
> Ok I did logs again I hope this time better.
> 
> 
> Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
>> 
>> Not really, no
>> 
>> The first part appears to show normal running with archive records every 
>> minute - but no log for the startup process
>> 
>> The second part, manual running , shows us the startup but only loop data - 
>> it runs for under a minute so does not give the coverage for two archive 
>> periods (which in your case would be at least 2 minutes)
>> 
>> The third part says debug disabled - but there does not appear to be any 
>> section where debug is enabled - so it is not clear if you are enabling 
>> debug correctly or not.
>> 
>> it is much better to just attach the logfile directly rather than trying to 
>> extract relevant portions.  you can identify sections by the timestamps of 
>> when you did things
>> 
>> we are making slow progress - but have yet to see debug successfully 
>> enabled!!  However, simulator does appear to be OK - and indeed the website 
>> confirms that simulator is running just fine.
>> 
>> See if you can get us some log which shows debug enabled at startup!!
>> 
>> 
>> 
>> 
>> 
>>> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:
>>> here it is.
>>> Is this ok what I attach?
>>> regards
>>> 
>>> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:
 
 Keep running the simulator for a while, but can you now give us the log 
 from startup for at least two archive intervals FOR SIMULATOR so that we 
 can be SURE everything is working as it should be.  Then, if that looks 
 ok, can you stop weewx, set debug = 1, restart weewx and again attach the 
 log from startup until at least two archive intervals.  This should show 
 that all is ok with debug also!!
 
  
 
> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
> https://github.com/matthewwall/weewx-interceptor
> 
>  this is what I have for interceptor in weewx.conf
> 
> [Interceptor]
> # This section is for the network traffic interceptor driver.
> 
> # The driver to use:
> driver = user.interceptor
> 
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge, smarthub, or access
> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> #   wu-client - any hardware that uses the weather underground 
> protocol
> #device_type = acurite-bridge
> device_type = observer
> port = 990
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/57255078-0935-48db-b1c3-2ce7813b488a%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/B2D4D668-35E7-4F99-ABA9-EB37134AAEB7%40isylum.org.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Ok I did logs again I hope this time better.


Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
>
> Not really, no
>
> The first part appears to show normal running with archive records every 
> minute - but no log for the startup process
>
> The second part, manual running , shows us the startup but only loop data 
> - it runs for under a minute so does not give the coverage for two archive 
> periods (which in your case would be at least 2 minutes)
>
> The third part says debug disabled - but there does not appear to be any 
> section where debug is enabled - so it is not clear if you are enabling 
> debug correctly or not.
>
> it is much better to just attach the logfile directly rather than trying 
> to extract relevant portions.  you can identify sections by the timestamps 
> of when you did things
>
> we are making slow progress - but have yet to see debug successfully 
> enabled!!  However, simulator does appear to be OK - and indeed the website 
> confirms that simulator is running just fine.
>
> See if you can get us some log which shows debug enabled at startup!!
>
>
>
>
>
> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:
>>
>> here it is.
>> Is this ok what I attach?
>> regards
>>
>> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:
>>>
>>> Keep running the simulator for a while, but can you now give us the log 
>>> from startup for at least two archive intervals FOR SIMULATOR so that we 
>>> can be SURE everything is working as it should be.  Then, if that looks ok, 
>>> can you stop weewx, set debug = 1, restart weewx and again attach the log 
>>> from startup until at least two archive intervals.  This should show that 
>>> all is ok with debug also!!
>>>
>>>  
>>>
>>> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:

 https://github.com/matthewwall/weewx-interceptor

  this is what I have for interceptor in weewx.conf

 [Interceptor]
 # This section is for the network traffic interceptor driver.
 
 # The driver to use:
 driver = user.interceptor
 
 # Specify the hardware device to capture.  Options include:
 #   acurite-bridge - acurite internet bridge, smarthub, or access
 #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
 #   lw30x - oregon scientific LW301/LW302
 #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
 #   wu-client - any hardware that uses the weather underground 
 protocol
 #device_type = acurite-bridge
 device_type = observer
 port = 990

>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/57255078-0935-48db-b1c3-2ce7813b488a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Debug disabled
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
#debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.1

Jun 14 18:12:38 povej weewx: Starting weewx: [  V redu  ]
Jun 14 18:12:38 povej weewx[18473]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jun 14 18:12:38 povej weewx[18473]: engine: Loading station type Simulator 
(weewx.drivers.simulator)
Jun 14 18:12:38 povej weewx[18473]: engine: StdConvert target unit is 0x1
Jun 14 18:12:38 povej weewx[18473]: wxcalculate: The following values will be 
calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Jun 14 18:12:38 povej weewx[18473]: wxcalculate: The following algorithms will 
be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun 14 18:12:38 povej weewx[18473]: engine: Archive will use data binding 
wx_binding
Jun 14 18:12:38 povej weewx[18473]: engine: Record generation will be attempted 
in 'hardware'
Jun 14 18:12:38 povej weewx[18473]: engine: Using archive interval of 

Re: [weewx-user] Re: weewx stop working

[gjr80]

If you look back through this thread this is exactly where we were with the 
previous install - WeeWX running but with no indication in the startup log as 
to how debug was set, no turning on of the debug features when debug=1 and 
little evidence to aid in determining the cause (of the original problem or the 
apparent lack of ‘debug’ control). It was about this stage where we went down a 
rabbit hole chasing debug with all manner of other tools.

Maybe this is some centos 7.6 peculiarity, who knows. I intend cranking up a 
centos 7.6 vm tomorrow to see if I can replicate any of this.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/db350e72-13cb-4846-b9cf-d80b57fa8233%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Andrew Milner]

Not really, no

The first part appears to show normal running with archive records every 
minute - but no log for the startup process

The second part, manual running , shows us the startup but only loop data - 
it runs for under a minute so does not give the coverage for two archive 
periods (which in your case would be at least 2 minutes)

The third part says debug disabled - but there does not appear to be any 
section where debug is enabled - so it is not clear if you are enabling 
debug correctly or not.

it is much better to just attach the logfile directly rather than trying to 
extract relevant portions.  you can identify sections by the timestamps of 
when you did things

we are making slow progress - but have yet to see debug successfully 
enabled!!  However, simulator does appear to be OK - and indeed the website 
confirms that simulator is running just fine.

See if you can get us some log which shows debug enabled at startup!!





On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:
>
> here it is.
> Is this ok what I attach?
> regards
>
> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:
>>
>> Keep running the simulator for a while, but can you now give us the log 
>> from startup for at least two archive intervals FOR SIMULATOR so that we 
>> can be SURE everything is working as it should be.  Then, if that looks ok, 
>> can you stop weewx, set debug = 1, restart weewx and again attach the log 
>> from startup until at least two archive intervals.  This should show that 
>> all is ok with debug also!!
>>
>>  
>>
>> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>>>
>>> https://github.com/matthewwall/weewx-interceptor
>>>
>>>  this is what I have for interceptor in weewx.conf
>>>
>>> [Interceptor]
>>> # This section is for the network traffic interceptor driver.
>>> 
>>> # The driver to use:
>>> driver = user.interceptor
>>> 
>>> # Specify the hardware device to capture.  Options include:
>>> #   acurite-bridge - acurite internet bridge, smarthub, or access
>>> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
>>> #   lw30x - oregon scientific LW301/LW302
>>> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>>> #   wu-client - any hardware that uses the weather underground 
>>> protocol
>>> #device_type = acurite-bridge
>>> device_type = observer
>>> port = 990
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/82f17eec-3d5b-4ca2-8ce1-c9150b053d16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

here it is.
Is this ok what I attach?
regards

Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:
>
> Keep running the simulator for a while, but can you now give us the log 
> from startup for at least two archive intervals FOR SIMULATOR so that we 
> can be SURE everything is working as it should be.  Then, if that looks ok, 
> can you stop weewx, set debug = 1, restart weewx and again attach the log 
> from startup until at least two archive intervals.  This should show that 
> all is ok with debug also!!
>
>  
>
> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>>
>> https://github.com/matthewwall/weewx-interceptor
>>
>>  this is what I have for interceptor in weewx.conf
>>
>> [Interceptor]
>> # This section is for the network traffic interceptor driver.
>> 
>> # The driver to use:
>> driver = user.interceptor
>> 
>> # Specify the hardware device to capture.  Options include:
>> #   acurite-bridge - acurite internet bridge, smarthub, or access
>> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
>> #   lw30x - oregon scientific LW301/LW302
>> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>> #   wu-client - any hardware that uses the weather underground 
>> protocol
>> #device_type = acurite-bridge
>> device_type = observer
>> port = 990
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/11fc26fb-7694-4c40-98b7-6eaecc3c6dec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Log 
Jun 14 13:59:15 povej weewx[4536]: manager: Added record 2019-06-14 13:59:00 
CEST (1560513540) to database 'weewx'
Jun 14 13:59:15 povej weewx[4536]: manager: Added record 2019-06-14 13:59:00 
CEST (1560513540) to daily summary in 'weewx'
Jun 14 13:59:15 povej weewx[4536]: restx: Wunderground-PWS: Published record 
2019-06-14 13:59:00 CEST (1560513540)
Jun 14 13:59:16 povej weewx[4536]: cheetahgenerator: Generated 8 files for 
report SeasonsReport in 0.87 seconds
Jun 14 13:59:16 povej weewx[4536]: imagegenerator: Generated 14 images for 
SeasonsReport in 0.49 seconds
Jun 14 13:59:16 povej weewx[4536]: copygenerator: copied 0 files to 
/var/www/html/weewx
Jun 14 14:00:15 povej weewx[4536]: manager: Added record 2019-06-14 14:00:00 
CEST (1560513600) to database 'weewx'
Jun 14 14:00:15 povej weewx[4536]: manager: Added record 2019-06-14 14:00:00 
CEST (1560513600) to daily summary in 'weewx'
Jun 14 14:00:15 povej weewx[4536]: restx: Wunderground-PWS: Published record 
2019-06-14 14:00:00 CEST (1560513600)
Jun 14 14:00:16 povej weewx[4536]: cheetahgenerator: Generated 8 files for 
report SeasonsReport in 1.17 seconds
Jun 14 14:00:18 povej weewx[4536]: imagegenerator: Generated 28 images for 
SeasonsReport in 2.32 seconds
Jun 14 14:00:18 povej weewx[4536]: copygenerator: copied 0 files to 
/var/www/html/weewx

Jun 14 14:01:15 povej weewx[4536]: manager: Added record 2019-06-14 14:01:00 
CEST (1560513660) to database 'weewx'
Jun 14 14:01:15 povej weewx[4536]: manager: Added record 2019-06-14 14:01:00 
CEST (1560513660) to daily summary in 'weewx'
Jun 14 14:01:15 povej weewx[4536]: restx: Wunderground-PWS: Published record 
2019-06-14 14:01:00 CEST (1560513660)
Jun 14 14:01:16 povej weewx[4536]: cheetahgenerator: Generated 8 files for 
report SeasonsReport in 1.05 seconds
Jun 14 14:01:16 povej weewx[4536]: imagegenerator: Generated 14 images for 
SeasonsReport in 0.29 seconds
Jun 14 14:01:16 povej weewx[4536]: copygenerator: copied 0 files to 
/var/www/html/weewx

Jun 14 14:02:15 povej weewx[4536]: manager: Added record 2019-06-14 14:02:00 
CEST (1560513720) to database 'weewx'
Jun 14 14:02:15 povej weewx[4536]: manager: Added record 2019-06-14 14:02:00 
CEST (1560513720) to daily summary in 'weewx'
Jun 14 14:02:15 povej weewx[4536]: restx: Wunderground-PWS: Published record 
2019-06-14 14:02:00 CEST (1560513720)
Jun 14 14:02:16 povej weewx[4536]: cheetahgenerator: Generated 8 files for 
report SeasonsReport in 1.11 seconds
Jun 14 14:02:16 povej weewx[4536]: imagegenerator: Generated 14 images for 
SeasonsReport in 0.45 seconds
Jun 14 14:02:16 povej weewx[4536]: copygenerator: copied 0 files to 
/var/www/html/weewx

Log from manual starting

Jun 14 14:03:49 povej systemd: Stopped SYSV: start and stop the weewx weather 
system.
Jun 14 14:04:00 povej weewx[25422]: engine: Initializing weewx version 3.9.1
Jun 14 14:04:00 povej weewx[25422]: engine: Using Python 2.7.5 (default, Apr  9 
2019, 14:30:50) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
Jun 14 14:04:00 povej weewx[25422]: engine: Platform 
Linux-3.10.0-957.12.2.el7.x86_64-x86_64-with-centos-7.6.1810-Core
Jun 14 14:04:00 povej weewx[25422]: engine: Locale is 

Re: [weewx-user] Re: weewx stop working

[Andrew Milner]

Keep running the simulator for a while, but can you now give us the log 
from startup for at least two archive intervals FOR SIMULATOR so that we 
can be SURE everything is working as it should be.  Then, if that looks ok, 
can you stop weewx, set debug = 1, restart weewx and again attach the log 
from startup until at least two archive intervals.  This should show that 
all is ok with debug also!!

 

On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>
> https://github.com/matthewwall/weewx-interceptor
>
>  this is what I have for interceptor in weewx.conf
>
> [Interceptor]
> # This section is for the network traffic interceptor driver.
> 
> # The driver to use:
> driver = user.interceptor
> 
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge, smarthub, or access
> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> #   wu-client - any hardware that uses the weather underground protocol
> #device_type = acurite-bridge
> device_type = observer
> port = 990
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d749384f-acce-49df-b194-addea2609f94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

https://github.com/matthewwall/weewx-interceptor

 this is what I have for interceptor in weewx.conf

[Interceptor]
# This section is for the network traffic interceptor driver.

# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture.  Options include:
#   acurite-bridge - acurite internet bridge, smarthub, or access
#   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
#   wu-client - any hardware that uses the weather underground protocol
#device_type = acurite-bridge
device_type = observer
port = 990

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e8e3cd25-9e0d-4449-989a-6fe4b69acf3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Yes I did. When I have installed it it worked.
Now I have reconfigure it for simulator driver and it works.
https://vreme.povej.net
so it really is something with driver, what I can do to check what it is?


Dne petek, 14. junij 2019 11.24.55 UTC+2 je oseba gjr80 napisala:
>
> I think people are trying to help, it is just without a debug log it is 
> rather difficult to determine what is going on and therefore what might be 
> wrong. Also, if settings in weewx.conf are being ignored (eg debug=1) it 
> begs the question what else is amiss.
>
> So when you installed WeeWX did you run it first with the simulator to 
> prove you have a properly functioning WeeWX install? If not perhaps you 
> should take a step back and get WeeWX running with the simulator. That at 
> least proves WeeWX is functioning as it should before you move on to a more 
> complex setup.
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fbdba08a-c849-4526-8cab-d4c67455fdbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[gjr80]

I think people are trying to help, it is just without a debug log it is rather 
difficult to determine what is going on and therefore what might be wrong. 
Also, if settings in weewx.conf are being ignored (eg debug=1) it begs the 
question what else is amiss.

So when you installed WeeWX did you run it first with the simulator to prove 
you have a properly functioning WeeWX install? If not perhaps you should take a 
step back and get WeeWX running with the simulator. That at least proves WeeWX 
is functioning as it should before you move on to a more complex setup.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/34dfb345-8e6f-45b9-8d3d-4e437c2bef51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

First time I have installed weewx manually, just copy tar on server and 
install it.

Now on new server I have downloaded weewx-3.9.1-1.rhel.noarch.rpm 
 and install it.
than install driver interceptor and setup everything.
I even changed port from  to 9900.

I am really desperate, spend alof of hours try to solve this and it was not 
possible, now on new server it is the same.

Have somebody please any idea what I can do???
Delete all and install it again?
what if it is a problem with interceptor driver?
I have myweather station at home and my weewx server is at home, that's why 
I use interceptor.

regards

Dne petek, 14. junij 2019 10.18.32 UTC+2 je oseba Andrew Milner napisala:
>
> as always, my mistake. sorry.
>
> On Friday, 14 June 2019 10:48:31 UTC+3, gjr80 wrote:
>>
>> I agree something is not right, but it is not WEEWX_ROOT.  For an other 
>> than setup.py install WEEWX_ROOT is indeed / - 
>> http://weewx.com/docs/usersguide.htm#Where_to_find_things refers.
>>
>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/66c97157-589d-40f2-a0b5-2a163dd9f0b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Andrew Milner]

as always, my mistake. sorry.

On Friday, 14 June 2019 10:48:31 UTC+3, gjr80 wrote:
>
> I agree something is not right, but it is not WEEWX_ROOT.  For an other 
> than setup.py install WEEWX_ROOT is indeed / - 
> http://weewx.com/docs/usersguide.htm#Where_to_find_things refers.
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/444bed5f-3778-4705-a42b-731c505241cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[gjr80]

I agree something is not right, but it is not WEEWX_ROOT.  For an other than 
setup.py install WEEWX_ROOT is indeed / - 
http://weewx.com/docs/usersguide.htm#Where_to_find_things refers.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/54a923db-8180-4e46-abcf-1e71979ff03b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Andrew Milner]

hold on a minute, something is not correct.  The section of weewx.conf you 
posted says WEEWX_ROOT is / whilst the weewx startup says weewx is using 
/etc/weewx/weewx.conf, which implies that WEEWX_ROOT should be /etc/weewx 
and not /

also debug should be set = 1 in /etc/weewx/weewx.conf - I suspect you are 
editing a version of weewx.conf in the root directory which is why there is 
no debug information.



On Friday, 14 June 2019 10:03:50 UTC+3, Damjan Hajsek wrote:
>
> Sorry all of that I already did on old server.
> Below I did this again, no other logs. This is the reason why I had to 
> reinstall server again and again not working.
> I run manually again fev times and all what I get in log is
>
> # WEEWX CONFIGURATION FILE
> #
> # Copyright (c) 2009-2019 Tom Keffer >
> # See the file LICENSE.txt for your rights.
>
>
> ##
>
> # This section is for general configuration information.
>
> # Set to 1 for extra debug info, otherwise comment it out or set to zero
> debug = 1
>
> # Root directory of the weewx data file hierarchy for this station
> WEEWX_ROOT = /
>
> # Whether to log successful operations
> log_success = True
>
> # Whether to log unsuccessful operations
> log_failure = True
>
> # How long to wait before timing out a socket (FTP, HTTP) connection
> socket_timeout = 20
>
> # Do not modify this. It is used when installing and updating weewx.
> version = 3.9.1
>
> sudo weewxd /etc/weewx/weewx.conf
>
> Jun 14 09:00:23 povej weewx[6760]: engine: Main loop exiting. Shutting 
> engine down.
> Jun 14 09:00:23 povej weewx[6760]: interceptor: MainThread: shutting down 
> server thread
> Jun 14 09:00:24 povej weewx[6760]: engine: Keyboard interrupt.
> Jun 14 09:00:26 povej weewx[11161]: engine: Initializing weewx version 
> 3.9.1
> Jun 14 09:00:26 povej weewx[11161]: engine: Using Python 2.7.5 (default, 
> Apr  9 2019, 14:30:50) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
> Jun 14 09:00:26 povej weewx[11161]: engine: Platform 
> Linux-3.10.0-957.12.2.el7.x86_64-x86_64-with-centos-7.6.1810-Core
> Jun 14 09:00:26 povej weewx[11161]: engine: Locale is 'sl_SI.UTF-8'
> Jun 14 09:00:26 povej weewx[11161]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Jun 14 09:00:26 povej weewx[11161]: engine: Loading station type 
> Interceptor (user.interceptor)
> Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: driver 
> version is 0.45
> Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: device type: 
> acurite-bridge
> Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: sensor map: 
> None
> Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: mode is listen
> Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: listen on 
> :9900
> Jun 14 09:00:26 povej weewx[11161]: engine: StdConvert target unit is 0x1
> Jun 14 09:00:26 povej weewx[11161]: wxcalculate: The following values will 
> be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> cloudbase=prefer_hardware
> Jun 14 09:00:26 povej weewx[11161]: wxcalculate: The following algorithms 
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Jun 14 09:00:26 povej weewx[11161]: engine: Archive will use data binding 
> wx_binding
> Jun 14 09:00:26 povej weewx[11161]: engine: Record generation will be 
> attempted in 'hardware'
> Jun 14 09:00:26 povej weewx[11161]: engine: Using archive interval of 60 
> seconds (specified in weewx configuration)
> Jun 14 09:00:26 povej weewx[11161]: engine: Using binding 'wx_binding' to 
> database 'weewx'
> Jun 14 09:00:26 povej weewx[11161]: manager: Starting backfill of daily 
> summaries
> Jun 14 09:00:26 povej weewx[11161]: restx: StationRegistry: Registration 
> not requested.
> Jun 14 09:00:26 povej weewx[11161]: restx: Wunderground-PWS: Data for 
> station IDO8 will be posted
> Jun 14 09:00:26 povej weewx[11161]: restx: PWSweather: Posting not enabled.
> Jun 14 09:00:26 povej weewx[11161]: restx: CWOP: Posting not enabled.
> Jun 14 09:00:26 povej weewx[11161]: restx: WOW: Posting not enabled.
> Jun 14 09:00:26 povej weewx[11161]: restx: AWEKAS: Posting not enabled.
> Jun 14 09:00:26 povej weewx[11161]: engine: Starting up weewx version 3.9.1
> Jun 14 09:00:26 povej weewx[11161]: engine: Starting main packet loop.
>
> Dne petek, 14. junij 2019 03.25.32 UTC+2 je oseba Andrew Milner napisala:
>>
>> Have you done what Matthew asked some time ago and run weewx manually - 
>> not as a daemon??
>>
>> Did you get any LOOP packets logged to the screen when you ran manually??
>>
>> The log you posted just shows a normal startup - although debug does not 
>> appear to be set.  Did 

Re: [weewx-user] Re: weewx stop working

[Andrew Milner]

is your weewx installation really in the root directory as you have got 
specified in weewx.conf?

how did you install weewx ??



On Friday, 14 June 2019 04:25:32 UTC+3, Andrew Milner wrote:
>
> Have you done what Matthew asked some time ago and run weewx manually - 
> not as a daemon??
>
> Did you get any LOOP packets logged to the screen when you ran manually??
>
> The log you posted just shows a normal startup - although debug does not 
> appear to be set.  Did you edit the correct weewx,conf file when setting 
> debug=1??
>
>
>
> On Thursday, 13 June 2019 19:52:46 UTC+3, Damjan Hajsek wrote:
>>
>> Sorry I already post log from old centos server and it is the same on new 
>> centos server. All I have in log is only this
>>
>> Jun 13 18:50:56 povej systemd: Started SYSV: start and stop the weewx 
>> weather system.
>> Jun 13 18:50:56 povej weewx[15848]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Jun 13 18:50:56 povej weewx[15848]: engine: Loading station type 
>> Interceptor (user.interceptor)
>> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: driver 
>> version is 0.45
>> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: device type: 
>> acurite-bridge
>> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: sensor map: 
>> None
>> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: mode is 
>> listen
>> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: listen on 
>> :9900
>> Jun 13 18:50:56 povej weewx[15848]: engine: StdConvert target unit is 0x1
>> Jun 13 18:50:56 povej weewx[15848]: wxcalculate: The following values 
>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
>> rainRate=prefer_hardware, windrun=prefer_hardware, 
>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
>> humidex=prefer_hardware, pressure=prefer_hardware, 
>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
>> cloudbase=prefer_hardware
>> Jun 13 18:50:56 povej weewx[15848]: wxcalculate: The following algorithms 
>> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Jun 13 18:50:56 povej weewx[15848]: engine: Archive will use data binding 
>> wx_binding
>> Jun 13 18:50:56 povej weewx[15848]: engine: Record generation will be 
>> attempted in 'hardware'
>> Jun 13 18:50:56 povej weewx[15848]: engine: Using archive interval of 60 
>> seconds (specified in weewx configuration)
>> Jun 13 18:50:56 povej weewx[15848]: engine: Using binding 'wx_binding' to 
>> database 'weewx'
>> Jun 13 18:50:56 povej weewx[15848]: manager: Starting backfill of daily 
>> summaries
>> Jun 13 18:50:56 povej weewx[15848]: restx: StationRegistry: Registration 
>> not requested.
>> Jun 13 18:50:56 povej weewx[15848]: restx: Wunderground-PWS: Data for 
>> station IDOE7 will be posted
>> Jun 13 18:50:56 povej weewx[15848]: restx: PWSweather: Posting not 
>> enabled.
>> Jun 13 18:50:56 povej weewx[15848]: restx: CWOP: Posting not enabled.
>> Jun 13 18:50:56 povej weewx[15848]: restx: WOW: Posting not enabled.
>> Jun 13 18:50:56 povej weewx[15848]: restx: AWEKAS: Posting not enabled.
>> Jun 13 18:50:56 povej weewx[15848]: engine: Starting up weewx version 
>> 3.9.1
>> Jun 13 18:50:56 povej weewx[15848]: engine: Starting main packet loop.
>>
>> Dne četrtek, 13. junij 2019 14.02.25 UTC+2 je oseba Andrew Milner 
>> napisala:
>>>
>>> what does weex say in the log when it is starting??  weewx outputs a lot 
>>> of information at startup - so you need to locate the log and post the log 
>>> to this forum then we may be able to help you further
>>>
>>>
>>>
>>> On Thursday, 13 June 2019 11:11:32 UTC+3, Damjan Hajsek wrote:

 Any idea how to solve this please?

 Dne torek, 11. junij 2019 22.24.35 UTC+2 je oseba Damjan Hajsek 
 napisala:
>
> I have installed fresh new server centos 7.6
> also installed fresh installation of weewx 3.9.1
> also installed driver interceptor.
> And I get the same result as before.
> I have checked database doesn't change or fill up.
> there is no loop of weewx in logs and debug is 1
>
>
>  sudo strace -d /tmp/weewxd_strace.txt weewxd
> strace: ptrace_setoptions = 0x11
> strace: new tcb for pid 11807, active tcbs:1
> strace: [wait(0x80137f) = 11807] WIFSTOPPED,sig=SIGSTOP,EVENT_STOP 
> (128)
> strace: pid 11807 has TCB_STARTUP, initializing it
> strace: [wait(0x80057f) = 11807] WIFSTOPPED,sig=SIGTRAP,EVENT_STOP 
> (128)
> strace: [wait(0x00127f) = 11807] WIFSTOPPED,sig=SIGCONT
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> execve("/tmp/weewxd_strace.txt", ["/tmp/weewxd_strace.txt", "weewxd"], 
> [/* 18 vars */]strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> ) = -1 ENOEXEC (Exec format error)
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Sorry all of that I already did on old server.
Below I did this again, no other logs. This is the reason why I had to 
reinstall server again and again not working.
I run manually again fev times and all what I get in log is

# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.1

sudo weewxd /etc/weewx/weewx.conf

Jun 14 09:00:23 povej weewx[6760]: engine: Main loop exiting. Shutting 
engine down.
Jun 14 09:00:23 povej weewx[6760]: interceptor: MainThread: shutting down 
server thread
Jun 14 09:00:24 povej weewx[6760]: engine: Keyboard interrupt.
Jun 14 09:00:26 povej weewx[11161]: engine: Initializing weewx version 3.9.1
Jun 14 09:00:26 povej weewx[11161]: engine: Using Python 2.7.5 (default, 
Apr  9 2019, 14:30:50) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
Jun 14 09:00:26 povej weewx[11161]: engine: Platform 
Linux-3.10.0-957.12.2.el7.x86_64-x86_64-with-centos-7.6.1810-Core
Jun 14 09:00:26 povej weewx[11161]: engine: Locale is 'sl_SI.UTF-8'
Jun 14 09:00:26 povej weewx[11161]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jun 14 09:00:26 povej weewx[11161]: engine: Loading station type 
Interceptor (user.interceptor)
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: driver version 
is 0.45
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: device type: 
acurite-bridge
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: sensor map: 
None
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: mode is listen
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: listen on :9900
Jun 14 09:00:26 povej weewx[11161]: engine: StdConvert target unit is 0x1
Jun 14 09:00:26 povej weewx[11161]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Jun 14 09:00:26 povej weewx[11161]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun 14 09:00:26 povej weewx[11161]: engine: Archive will use data binding 
wx_binding
Jun 14 09:00:26 povej weewx[11161]: engine: Record generation will be 
attempted in 'hardware'
Jun 14 09:00:26 povej weewx[11161]: engine: Using archive interval of 60 
seconds (specified in weewx configuration)
Jun 14 09:00:26 povej weewx[11161]: engine: Using binding 'wx_binding' to 
database 'weewx'
Jun 14 09:00:26 povej weewx[11161]: manager: Starting backfill of daily 
summaries
Jun 14 09:00:26 povej weewx[11161]: restx: StationRegistry: Registration 
not requested.
Jun 14 09:00:26 povej weewx[11161]: restx: Wunderground-PWS: Data for 
station IDO8 will be posted
Jun 14 09:00:26 povej weewx[11161]: restx: PWSweather: Posting not enabled.
Jun 14 09:00:26 povej weewx[11161]: restx: CWOP: Posting not enabled.
Jun 14 09:00:26 povej weewx[11161]: restx: WOW: Posting not enabled.
Jun 14 09:00:26 povej weewx[11161]: restx: AWEKAS: Posting not enabled.
Jun 14 09:00:26 povej weewx[11161]: engine: Starting up weewx version 3.9.1
Jun 14 09:00:26 povej weewx[11161]: engine: Starting main packet loop.

Dne petek, 14. junij 2019 03.25.32 UTC+2 je oseba Andrew Milner napisala:
>
> Have you done what Matthew asked some time ago and run weewx manually - 
> not as a daemon??
>
> Did you get any LOOP packets logged to the screen when you ran manually??
>
> The log you posted just shows a normal startup - although debug does not 
> appear to be set.  Did you edit the correct weewx,conf file when setting 
> debug=1??
>
>
>
> On Thursday, 13 June 2019 19:52:46 UTC+3, Damjan Hajsek wrote:
>>
>> Sorry I already post log from old centos server and it is the same on new 
>> centos server. All I have in log is only this
>>
>> Jun 13 18:50:56 povej systemd: Started SYSV: start and stop the weewx 
>> weather system.
>> Jun 13 18:50:56 povej weewx[15848]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Jun 13 18:50:56 povej weewx[15848]: engine: Loading station type 
>> Interceptor (user.interceptor)
>> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: driver 
>> version is 0.45
>> Jun 13 

Re: [weewx-user] Re: weewx stop working

[Andrew Milner]

Have you done what Matthew asked some time ago and run weewx manually - not 
as a daemon??

Did you get any LOOP packets logged to the screen when you ran manually??

The log you posted just shows a normal startup - although debug does not 
appear to be set.  Did you edit the correct weewx,conf file when setting 
debug=1??



On Thursday, 13 June 2019 19:52:46 UTC+3, Damjan Hajsek wrote:
>
> Sorry I already post log from old centos server and it is the same on new 
> centos server. All I have in log is only this
>
> Jun 13 18:50:56 povej systemd: Started SYSV: start and stop the weewx 
> weather system.
> Jun 13 18:50:56 povej weewx[15848]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Jun 13 18:50:56 povej weewx[15848]: engine: Loading station type 
> Interceptor (user.interceptor)
> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: driver 
> version is 0.45
> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: device type: 
> acurite-bridge
> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: sensor map: 
> None
> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: mode is listen
> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: listen on 
> :9900
> Jun 13 18:50:56 povej weewx[15848]: engine: StdConvert target unit is 0x1
> Jun 13 18:50:56 povej weewx[15848]: wxcalculate: The following values will 
> be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> cloudbase=prefer_hardware
> Jun 13 18:50:56 povej weewx[15848]: wxcalculate: The following algorithms 
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Jun 13 18:50:56 povej weewx[15848]: engine: Archive will use data binding 
> wx_binding
> Jun 13 18:50:56 povej weewx[15848]: engine: Record generation will be 
> attempted in 'hardware'
> Jun 13 18:50:56 povej weewx[15848]: engine: Using archive interval of 60 
> seconds (specified in weewx configuration)
> Jun 13 18:50:56 povej weewx[15848]: engine: Using binding 'wx_binding' to 
> database 'weewx'
> Jun 13 18:50:56 povej weewx[15848]: manager: Starting backfill of daily 
> summaries
> Jun 13 18:50:56 povej weewx[15848]: restx: StationRegistry: Registration 
> not requested.
> Jun 13 18:50:56 povej weewx[15848]: restx: Wunderground-PWS: Data for 
> station IDOE7 will be posted
> Jun 13 18:50:56 povej weewx[15848]: restx: PWSweather: Posting not enabled.
> Jun 13 18:50:56 povej weewx[15848]: restx: CWOP: Posting not enabled.
> Jun 13 18:50:56 povej weewx[15848]: restx: WOW: Posting not enabled.
> Jun 13 18:50:56 povej weewx[15848]: restx: AWEKAS: Posting not enabled.
> Jun 13 18:50:56 povej weewx[15848]: engine: Starting up weewx version 3.9.1
> Jun 13 18:50:56 povej weewx[15848]: engine: Starting main packet loop.
>
> Dne četrtek, 13. junij 2019 14.02.25 UTC+2 je oseba Andrew Milner napisala:
>>
>> what does weex say in the log when it is starting??  weewx outputs a lot 
>> of information at startup - so you need to locate the log and post the log 
>> to this forum then we may be able to help you further
>>
>>
>>
>> On Thursday, 13 June 2019 11:11:32 UTC+3, Damjan Hajsek wrote:
>>>
>>> Any idea how to solve this please?
>>>
>>> Dne torek, 11. junij 2019 22.24.35 UTC+2 je oseba Damjan Hajsek napisala:

 I have installed fresh new server centos 7.6
 also installed fresh installation of weewx 3.9.1
 also installed driver interceptor.
 And I get the same result as before.
 I have checked database doesn't change or fill up.
 there is no loop of weewx in logs and debug is 1


  sudo strace -d /tmp/weewxd_strace.txt weewxd
 strace: ptrace_setoptions = 0x11
 strace: new tcb for pid 11807, active tcbs:1
 strace: [wait(0x80137f) = 11807] WIFSTOPPED,sig=SIGSTOP,EVENT_STOP (128)
 strace: pid 11807 has TCB_STARTUP, initializing it
 strace: [wait(0x80057f) = 11807] WIFSTOPPED,sig=SIGTRAP,EVENT_STOP (128)
 strace: [wait(0x00127f) = 11807] WIFSTOPPED,sig=SIGCONT
 strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
 execve("/tmp/weewxd_strace.txt", ["/tmp/weewxd_strace.txt", "weewxd"], 
 [/* 18 vars */]strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
 ) = -1 ENOEXEC (Exec format error)
 strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
 write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec 
 format error
 strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
 ) = 32
 strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
 exit_group(1)   = ?
 strace: [wait(0x000100) = 11807] WIFEXITED,exitcode=1
 +++ exited with 1 +++
 strace: dropped tcb for pid 11807, 0 remain

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Sorry I already post log from old centos server and it is the same on new 
centos server. All I have in log is only this

Jun 13 18:50:56 povej systemd: Started SYSV: start and stop the weewx 
weather system.
Jun 13 18:50:56 povej weewx[15848]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jun 13 18:50:56 povej weewx[15848]: engine: Loading station type 
Interceptor (user.interceptor)
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: driver version 
is 0.45
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: device type: 
acurite-bridge
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: sensor map: 
None
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: mode is listen
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: listen on :9900
Jun 13 18:50:56 povej weewx[15848]: engine: StdConvert target unit is 0x1
Jun 13 18:50:56 povej weewx[15848]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Jun 13 18:50:56 povej weewx[15848]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun 13 18:50:56 povej weewx[15848]: engine: Archive will use data binding 
wx_binding
Jun 13 18:50:56 povej weewx[15848]: engine: Record generation will be 
attempted in 'hardware'
Jun 13 18:50:56 povej weewx[15848]: engine: Using archive interval of 60 
seconds (specified in weewx configuration)
Jun 13 18:50:56 povej weewx[15848]: engine: Using binding 'wx_binding' to 
database 'weewx'
Jun 13 18:50:56 povej weewx[15848]: manager: Starting backfill of daily 
summaries
Jun 13 18:50:56 povej weewx[15848]: restx: StationRegistry: Registration 
not requested.
Jun 13 18:50:56 povej weewx[15848]: restx: Wunderground-PWS: Data for 
station IDOE7 will be posted
Jun 13 18:50:56 povej weewx[15848]: restx: PWSweather: Posting not enabled.
Jun 13 18:50:56 povej weewx[15848]: restx: CWOP: Posting not enabled.
Jun 13 18:50:56 povej weewx[15848]: restx: WOW: Posting not enabled.
Jun 13 18:50:56 povej weewx[15848]: restx: AWEKAS: Posting not enabled.
Jun 13 18:50:56 povej weewx[15848]: engine: Starting up weewx version 3.9.1
Jun 13 18:50:56 povej weewx[15848]: engine: Starting main packet loop.

Dne četrtek, 13. junij 2019 14.02.25 UTC+2 je oseba Andrew Milner napisala:
>
> what does weex say in the log when it is starting??  weewx outputs a lot 
> of information at startup - so you need to locate the log and post the log 
> to this forum then we may be able to help you further
>
>
>
> On Thursday, 13 June 2019 11:11:32 UTC+3, Damjan Hajsek wrote:
>>
>> Any idea how to solve this please?
>>
>> Dne torek, 11. junij 2019 22.24.35 UTC+2 je oseba Damjan Hajsek napisala:
>>>
>>> I have installed fresh new server centos 7.6
>>> also installed fresh installation of weewx 3.9.1
>>> also installed driver interceptor.
>>> And I get the same result as before.
>>> I have checked database doesn't change or fill up.
>>> there is no loop of weewx in logs and debug is 1
>>>
>>>
>>>  sudo strace -d /tmp/weewxd_strace.txt weewxd
>>> strace: ptrace_setoptions = 0x11
>>> strace: new tcb for pid 11807, active tcbs:1
>>> strace: [wait(0x80137f) = 11807] WIFSTOPPED,sig=SIGSTOP,EVENT_STOP (128)
>>> strace: pid 11807 has TCB_STARTUP, initializing it
>>> strace: [wait(0x80057f) = 11807] WIFSTOPPED,sig=SIGTRAP,EVENT_STOP (128)
>>> strace: [wait(0x00127f) = 11807] WIFSTOPPED,sig=SIGCONT
>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> execve("/tmp/weewxd_strace.txt", ["/tmp/weewxd_strace.txt", "weewxd"], 
>>> [/* 18 vars */]strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> ) = -1 ENOEXEC (Exec format error)
>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec 
>>> format error
>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> ) = 32
>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> exit_group(1)   = ?
>>> strace: [wait(0x000100) = 11807] WIFEXITED,exitcode=1
>>> +++ exited with 1 +++
>>> strace: dropped tcb for pid 11807, 0 remain
>>>
>>>
>>>
>>> Dne četrtek, 25. april 2019 18.38.58 UTC+2 je oseba Leon Shaner napisala:

 Damian,

 Still very strange that we do not see debug = 1 echoed in the logs.

 At this point I am at a loss other than, perhaps you could preface the 
 command with strace so we can see what is going on.  I expect it gets to a 
 point where it is just more or less sleeping, doing nothing.

 I say that based on your previous "ps -elf" output where it showed 
 00:00:00 cpu time and was sleeping.   It is 

Re: [weewx-user] Re: weewx stop working

[Andrew Milner]

what does weex say in the log when it is starting??  weewx outputs a lot of 
information at startup - so you need to locate the log and post the log to 
this forum then we may be able to help you further



On Thursday, 13 June 2019 11:11:32 UTC+3, Damjan Hajsek wrote:
>
> Any idea how to solve this please?
>
> Dne torek, 11. junij 2019 22.24.35 UTC+2 je oseba Damjan Hajsek napisala:
>>
>> I have installed fresh new server centos 7.6
>> also installed fresh installation of weewx 3.9.1
>> also installed driver interceptor.
>> And I get the same result as before.
>> I have checked database doesn't change or fill up.
>> there is no loop of weewx in logs and debug is 1
>>
>>
>>  sudo strace -d /tmp/weewxd_strace.txt weewxd
>> strace: ptrace_setoptions = 0x11
>> strace: new tcb for pid 11807, active tcbs:1
>> strace: [wait(0x80137f) = 11807] WIFSTOPPED,sig=SIGSTOP,EVENT_STOP (128)
>> strace: pid 11807 has TCB_STARTUP, initializing it
>> strace: [wait(0x80057f) = 11807] WIFSTOPPED,sig=SIGTRAP,EVENT_STOP (128)
>> strace: [wait(0x00127f) = 11807] WIFSTOPPED,sig=SIGCONT
>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>> execve("/tmp/weewxd_strace.txt", ["/tmp/weewxd_strace.txt", "weewxd"], 
>> [/* 18 vars */]strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>> ) = -1 ENOEXEC (Exec format error)
>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>> write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec format 
>> error
>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>> ) = 32
>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>> exit_group(1)   = ?
>> strace: [wait(0x000100) = 11807] WIFEXITED,exitcode=1
>> +++ exited with 1 +++
>> strace: dropped tcb for pid 11807, 0 remain
>>
>>
>>
>> Dne četrtek, 25. april 2019 18.38.58 UTC+2 je oseba Leon Shaner napisala:
>>>
>>> Damian,
>>>
>>> Still very strange that we do not see debug = 1 echoed in the logs.
>>>
>>> At this point I am at a loss other than, perhaps you could preface the 
>>> command with strace so we can see what is going on.  I expect it gets to a 
>>> point where it is just more or less sleeping, doing nothing.
>>>
>>> I say that based on your previous "ps -elf" output where it showed 
>>> 00:00:00 cpu time and was sleeping.   It is normal for the process to sleep 
>>> when there is no input, but it should have to be doing at least some work 
>>> from time to time.
>>>
>>> From the ps man page:
>>>
>>> PROCESS STATE CODES
>>>Here are the different values that the s, stat and state output 
>>> specifiers (header "STAT" or "S") will display to describe the state of a 
>>> process:
>>>
>>>Duninterruptible sleep (usually IO)
>>>Rrunning or runnable (on run queue)
>>>Sinterruptible sleep (waiting for an event to 
>>> complete)
>>>Tstopped by job control signal
>>>tstopped by debugger during the tracing
>>>Wpaging (not valid since the 2.6.xx kernel)
>>>Xdead (should never be seen)
>>>Zdefunct ("zombie") process, terminated but not 
>>> reaped by its parent
>>>
>>> Here is an example of how to strace the process and get the debug output 
>>> into a file:
>>>
>>> $ sudo strace -o /tmp/weewxd_strace.txt weewxd
>>>
>>> You can "tail -f /tmp/weewxd_strace.txt" to see what is going on.
>>> It will likely get to a point where it is quiet for long periods.  You 
>>> can stop the strace after you see those a couple of times.
>>>
>>> The output could be quite large so you may want to compress it:
>>>
>>> $ gzip /tmp/weewxd_strace.txt
>>>
>>> Regards,
>>> Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>>
>>> On Apr 25, 2019, at 10:30 AM, Damjan Hajsek  wrote:
>>>
>>> Hi
>>> I have done this and it is all the same. I created some logs from 
>>> manually starting weewx.
>>> when I start weewx manually sudo weewxd /etc/weewx/weewx.conf'
>>> it didn't crash, I stopped it.
>>> here it is.
>>>
>>> http://zerobin.povej.net/?b06b1ad942bc51a2#34Nj1ed+8odSg7jHbjz7AU+WsqZ3yxPjZDB1EPHyVAk=
>>>
>>>
>>>
>>> Dne sreda, 24. april 2019 15.48.25 UTC+2 je oseba Leon Shaner napisala:

 Damian,
 You have to give wee_config a command.
 From the usage, you want this:

 $ sudo wee_config --reconfigure --config=/etc/weewx/weewx.conf

 (Although you can leave the --config part off, since your conf file is 
 located in the default location).

 But do be sure to back up the config file first...

 Regards,
 Leon
 --
 Leon Shaner :: Dearborn, Michigan (iPad Pro)

 On Apr 24, 2019, at 6:20 AM, Damjan Hajsek  wrote:

 Hi
 What I did is first use some old weewx.conf file from last year and 
 doesn't work either.
 So I tried to reconfigure it but can't
 when I run wee_config --help I get list of help
 but when I do this I get
 wee_config /etc/weewx/weewx.conf
 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Any idea how to solve this please?

Dne torek, 11. junij 2019 22.24.35 UTC+2 je oseba Damjan Hajsek napisala:
>
> I have installed fresh new server centos 7.6
> also installed fresh installation of weewx 3.9.1
> also installed driver interceptor.
> And I get the same result as before.
> I have checked database doesn't change or fill up.
> there is no loop of weewx in logs and debug is 1
>
>
>  sudo strace -d /tmp/weewxd_strace.txt weewxd
> strace: ptrace_setoptions = 0x11
> strace: new tcb for pid 11807, active tcbs:1
> strace: [wait(0x80137f) = 11807] WIFSTOPPED,sig=SIGSTOP,EVENT_STOP (128)
> strace: pid 11807 has TCB_STARTUP, initializing it
> strace: [wait(0x80057f) = 11807] WIFSTOPPED,sig=SIGTRAP,EVENT_STOP (128)
> strace: [wait(0x00127f) = 11807] WIFSTOPPED,sig=SIGCONT
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> execve("/tmp/weewxd_strace.txt", ["/tmp/weewxd_strace.txt", "weewxd"], [/* 
> 18 vars */]strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> ) = -1 ENOEXEC (Exec format error)
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec format 
> error
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> ) = 32
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> exit_group(1)   = ?
> strace: [wait(0x000100) = 11807] WIFEXITED,exitcode=1
> +++ exited with 1 +++
> strace: dropped tcb for pid 11807, 0 remain
>
>
>
> Dne četrtek, 25. april 2019 18.38.58 UTC+2 je oseba Leon Shaner napisala:
>>
>> Damian,
>>
>> Still very strange that we do not see debug = 1 echoed in the logs.
>>
>> At this point I am at a loss other than, perhaps you could preface the 
>> command with strace so we can see what is going on.  I expect it gets to a 
>> point where it is just more or less sleeping, doing nothing.
>>
>> I say that based on your previous "ps -elf" output where it showed 
>> 00:00:00 cpu time and was sleeping.   It is normal for the process to sleep 
>> when there is no input, but it should have to be doing at least some work 
>> from time to time.
>>
>> From the ps man page:
>>
>> PROCESS STATE CODES
>>Here are the different values that the s, stat and state output 
>> specifiers (header "STAT" or "S") will display to describe the state of a 
>> process:
>>
>>Duninterruptible sleep (usually IO)
>>Rrunning or runnable (on run queue)
>>Sinterruptible sleep (waiting for an event to complete)
>>Tstopped by job control signal
>>tstopped by debugger during the tracing
>>Wpaging (not valid since the 2.6.xx kernel)
>>Xdead (should never be seen)
>>Zdefunct ("zombie") process, terminated but not reaped 
>> by its parent
>>
>> Here is an example of how to strace the process and get the debug output 
>> into a file:
>>
>> $ sudo strace -o /tmp/weewxd_strace.txt weewxd
>>
>> You can "tail -f /tmp/weewxd_strace.txt" to see what is going on.
>> It will likely get to a point where it is quiet for long periods.  You 
>> can stop the strace after you see those a couple of times.
>>
>> The output could be quite large so you may want to compress it:
>>
>> $ gzip /tmp/weewxd_strace.txt
>>
>> Regards,
>> Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On Apr 25, 2019, at 10:30 AM, Damjan Hajsek  wrote:
>>
>> Hi
>> I have done this and it is all the same. I created some logs from 
>> manually starting weewx.
>> when I start weewx manually sudo weewxd /etc/weewx/weewx.conf'
>> it didn't crash, I stopped it.
>> here it is.
>>
>> http://zerobin.povej.net/?b06b1ad942bc51a2#34Nj1ed+8odSg7jHbjz7AU+WsqZ3yxPjZDB1EPHyVAk=
>>
>>
>>
>> Dne sreda, 24. april 2019 15.48.25 UTC+2 je oseba Leon Shaner napisala:
>>>
>>> Damian,
>>> You have to give wee_config a command.
>>> From the usage, you want this:
>>>
>>> $ sudo wee_config --reconfigure --config=/etc/weewx/weewx.conf
>>>
>>> (Although you can leave the --config part off, since your conf file is 
>>> located in the default location).
>>>
>>> But do be sure to back up the config file first...
>>>
>>> Regards,
>>> Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>>
>>> On Apr 24, 2019, at 6:20 AM, Damjan Hajsek  wrote:
>>>
>>> Hi
>>> What I did is first use some old weewx.conf file from last year and 
>>> doesn't work either.
>>> So I tried to reconfigure it but can't
>>> when I run wee_config --help I get list of help
>>> but when I do this I get
>>> wee_config /etc/weewx/weewx.conf
>>> No command specified.
>>> wee_config --config=/etc/weewx/weewx.conf
>>> No command specified.
>>>
>>>
>>> Dne torek, 23. april 2019 15.17.24 UTC+2 je oseba Leon Shaner napisala:

 Damian,

 These logs still do not state debug = 1.
 It still could be that the weewx.conf isn't being parsed correctly, and 
 isn't even able to read the debug = 1 setting.

 Did you try my 

Re: [weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[St. B.]

Great, I will look into this thank you.

On Wednesday, June 5, 2019 at 1:13:16 AM UTC+2, gjr80 wrote:
>
> This issue was fixed in v1.0.4. The v1.0.4 code was not released as a 
> package but can be installed by following the instructions in this post 
> .
>
> Gary
>
> On Tuesday, 4 June 2019 13:14:57 UTC+10, gjr80 wrote:
>>
>> Agree that WeeWX-WD has struck again and caused the error that was 
>> posted. Am sure this been fixed in a later version, I will track that one 
>> down and post a link as necessary.
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1c81be04-d0f8-496e-a10f-7b4bb41c85b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[gjr80]

This issue was fixed in v1.0.4. The v1.0.4 code was not released as a 
package but can be installed by following the instructions in this post 
.

Gary

On Tuesday, 4 June 2019 13:14:57 UTC+10, gjr80 wrote:
>
> Agree that WeeWX-WD has struck again and caused the error that was posted. 
> Am sure this been fixed in a later version, I will track that one down and 
> post a link as necessary.
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9ee29b9d-0c2d-40aa-82e2-76c54290061e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[St. B.]

Ok, 

Thanks for the info regarding WU. I might give a look into this, if it is 
not already taken care of by someone proficient on this topic.

The SDR is not failing, it was closed by Weewx, and the message order is 
somehow wrong. My station is back online since this morning, and did not 
shutdown.


On Tuesday, June 4, 2019 at 9:09:32 AM UTC+2, gjr80 wrote:
>
> You won’t be getting any forecast from WU using the forecast extension for 
> the time being as it has not yet been updated to work with the new WU API. 
> I suspect your time will be better spent looking into why the SDR driver is 
> exiting and causing the WeeWX engine to shut down. 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/96be47b1-58dd-4a2e-893c-0567748c3c22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[gjr80]

You won’t be getting any forecast from WU using the forecast extension for the 
time being as it has not yet been updated to work with the new WU API. I 
suspect your time will be better spent looking into why the SDR driver is 
exiting and causing the WeeWX engine to shut down.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9ae0bef2-cd30-42c7-8597-7e17eb63075d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[gjr80]

Agree that WeeWX-WD has struck again and caused the error that was posted. 
Am sure this been fixed in a later version, I will track that one down and 
post a link as necessary.

I also think there is another somewhat more critical issue - refer to the 
highlighted lines:

Jun  3 23:29:29 raspberrypi weewx[22046]: engine: Initializing weewx 
version 3.9.1
Jun  3 23:29:29 raspberrypi weewx[22046]: engine: Using Python 2.7.13 (
default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jun  3 23:29:29 raspberrypi weewx[22046]: engine: Platform Linux-4.19.42-v7
+-armv7l-with-debian-9.9
Jun  3 23:29:29 raspberrypi weewx[22046]: engine: Locale is 'en_GB.UTF-8'
Jun  3 23:29:29 raspberrypi weewx[22046]: engine: pid file is /var/run/weewx
.pid
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Using configuration file /
etc/weewx/weewx.conf
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Loading station type SDR (
user.sdr)
Jun  3 23:29:29 raspberrypi weewx[22051]: sdr: MainThread: driver version is 
0.14rc1
Jun  3 23:29:29 raspberrypi weewx[22051]: sdr: MainThread: sensor map is {
'windGust': 'wind_gust.0:*.OSWGR800Packet', 'windSpeed': 
'wind_speed.0:*.OSWGR800Packet', 'windBatteryStatus': 
'battery.0:*.OSWGR800Packet', 'windDir': 'wind_dir.0:*.OSWGR800Packet', 
'outHumidity': 'humidity.1:*.OSTHGR810Packet', 'outTemp': 
'temperature.1:*.OSTHGR810Packet', 'outTempBatteryStatus': 
'battery.1:*.OSTHGR810Packet', 'rain_total': 'rain_total.0:*.OSPCR800Packet'
, 'rainBatteryStatus': 'battery.0:*.OSPCR800Packet', 'extraTemp1': 
'temperature.1:14.RubicsonTempPacket', 'UV': 'uv_index.1:*.OSUV800Packet', 
'pressure': 'pressure.1:*.OSBTHGN129Packet', 'inTemp': 
'temperature.1:*.OSBTHGN129Packet', 'inHumidity': 
'humidity.1:*.OSBTHGN129Packet', 'inTempBatteryStatus': 
'battery.1:*.OSBTHGN129Packet'}
Jun  3 23:29:29 raspberrypi weewx[22051]: sdr: MainThread: deltas is {
'strikes': 'strikes_total', 'rain': 'rain_total'}
Jun  3 23:29:29 raspberrypi weewx[22051]: sdr: MainThread: startup process 
'/usr/local/bin/rtl_433 
-q -U'
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: StdConvert target unit is 
0x1
Jun  3 23:29:29 raspberrypi weewx[22051]: wxcalculate: The following values 
will be calculated: barometer=software, windchill=prefer_hardware, dewpoint=
prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=
prefer_hardware, heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, inDewpoint=
prefer_hardware, ET=prefer_hardware, altimeter=software, cloudbase=
prefer_hardware
Jun  3 23:29:29 raspberrypi weewx[22051]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Archive will use data 
binding wx_binding
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Record generation will be 
attempted in 'hardware'
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Using archive interval of 
90 seconds (specified in weewx configuration)
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Using binding 'wx_binding' 
to database 'weewx'
Jun  3 23:29:29 raspberrypi weewx[22051]: manager: Starting backfill of 
daily summaries
Jun  3 23:29:29 raspberrypi weewx[22051]: WdArchive: WdArchive will use 
data binding wd_binding
Jun  3 23:29:29 raspberrypi weewx[22051]: WdArchive: Using binding 
'wd_binding' to database 'weewxwd'
Jun  3 23:29:29 raspberrypi weewx[22051]: WdArchive: Starting backfill of 
daily summaries
Jun  3 23:29:29 raspberrypi kernel: [113521.231818] r820t 4-001a: 
destroying instance
Jun  3 23:29:29 raspberrypi kernel: [113521.232349] dvb_usb_v2: 'Realtek 
RTL2832U reference design:1-1.4' successfully deinitialized and disconnected
Jun  3 23:29:29 raspberrypi weewx[22051]: manager: Starting backfill of 
daily summaries
Jun  3 23:29:29 raspberrypi weewx[22051]: WdArchive: Daily summaries up to 
date.
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: Zambretti: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: Zambretti: 
interval=600 max_age=604800 winddir_period=1800 pressure_period=10800 
hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: NWS: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: WU: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: WU: interval
=10800 max_age=604800 api_key=b92d location=pws:IRHNEALP38 fc=
hourly10day
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: OWM: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: UKMO: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: Aeris: 
forecast version 3.2.14
Jun  3 23:29:30 raspberrypi weewx[22051]: forecast: MainThread: WWO: 
forecast version 3.2.14
Jun  3 23:29:30 raspberrypi 

Re: [weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[Thomas Keffer]

The problem is not with WeeWX, but with the weewxwd3 extension you
installed. It does not seem to check for missing data before attempting to
calculate humidity.

On Mon, Jun 3, 2019 at 2:36 PM St. B.  wrote:

> Ok,
>
> Below is the the /var/log/messages generated when running systemctl
> restart weewx.
>
> Weirdly enough systemctl start weewx does not seem to run anything.
>
> Stack trace when running from command prompt is as follows :
> root@raspberrypi:~# weewxd /etc/weewx/weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 890, in main
> engine.run()
>   File "/usr/share/weewx/weewx/engine.py", line 191, in run
> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>   File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> callback(event)
>   File "/usr/share/weewx/user/weewxwd3.py", line 144, in new_loop_packet
> wd_data['humidex'] =
> weewx.wxformulas.humidexC(data_metricwx['outTemp'],
> KeyError: 'outTemp'
> root@raspberrypi:~#
>
> Associated message traces are in mylog.shell
>
> On Monday, June 3, 2019 at 11:19:52 PM UTC+2, Pat wrote:
>>
>> Nothing jumping out. Pasting some logs and debugs would be super helpful.
>> See Help! Posting to weewx user
>> 
>>
>>
>>
>> On Monday, June 3, 2019 at 4:49:17 PM UTC-4, St. B. wrote:
>>>
>>> Hi,
>>>
>>> I decided (because my WU forecast where not working anymore) to update
>>> weewx to 3.9.1. on my raspberry running debian stretch.
>>> downloaded the weewx.3.9.1.all.deb installed, and kept my conf files.
>>> Upon install completion, no restart of the service.
>>>
>>> When starting, weewx starts the mainloop then shutsdown, wait for RTL
>>> process shutdown and dies.
>>> rtl runs fine from the command prompt.
>>> when running from the command prompt weewxd starts, and dies quickly
>>> with an invalid key "windSpeed" or some other key.
>>> These keys are in my mappings, but did not change since 3.6
>>>
>>> I ran a full update of my raspberry and am now at deb 9.9, but still no
>>> weewx.
>>>
>>> What obvious "you must check when updating" did I miss on this one ?
>>>
>>> Regards;
>>>
>>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/66dc95b4-7dff-42f7-9d7f-476efdbe8225%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAz-G5Ys_wSQAAj%2BObMNCBKCZcdGFZijGFrChiPd9nw6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Leon Shaner]

Damian,

Still very strange that we do not see debug = 1 echoed in the logs.

At this point I am at a loss other than, perhaps you could preface the command 
with strace so we can see what is going on.  I expect it gets to a point where 
it is just more or less sleeping, doing nothing.

I say that based on your previous "ps -elf" output where it showed 00:00:00 cpu 
time and was sleeping.   It is normal for the process to sleep when there is no 
input, but it should have to be doing at least some work from time to time.

>From the ps man page:

PROCESS STATE CODES
   Here are the different values that the s, stat and state output 
specifiers (header "STAT" or "S") will display to describe the state of a 
process:

   Duninterruptible sleep (usually IO)
   Rrunning or runnable (on run queue)
   Sinterruptible sleep (waiting for an event to complete)
   Tstopped by job control signal
   tstopped by debugger during the tracing
   Wpaging (not valid since the 2.6.xx kernel)
   Xdead (should never be seen)
   Zdefunct ("zombie") process, terminated but not reaped by 
its parent

Here is an example of how to strace the process and get the debug output into a 
file:

$ sudo strace -o /tmp/weewxd_strace.txt weewxd

You can "tail -f /tmp/weewxd_strace.txt" to see what is going on.
It will likely get to a point where it is quiet for long periods.  You can stop 
the strace after you see those a couple of times.

The output could be quite large so you may want to compress it:

$ gzip /tmp/weewxd_strace.txt

Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On Apr 25, 2019, at 10:30 AM, Damjan Hajsek  wrote:
> 
> Hi
> I have done this and it is all the same. I created some logs from manually 
> starting weewx.
> when I start weewx manually sudo weewxd /etc/weewx/weewx.conf'
> it didn't crash, I stopped it.
> here it is.
> http://zerobin.povej.net/?b06b1ad942bc51a2#34Nj1ed+8odSg7jHbjz7AU+WsqZ3yxPjZDB1EPHyVAk=
> 
> 
> 
> Dne sreda, 24. april 2019 15.48.25 UTC+2 je oseba Leon Shaner napisala:
>> 
>> Damian,
>> You have to give wee_config a command.
>> From the usage, you want this:
>> 
>> $ sudo wee_config --reconfigure --config=/etc/weewx/weewx.conf
>> 
>> (Although you can leave the --config part off, since your conf file is 
>> located in the default location).
>> 
>> But do be sure to back up the config file first...
>> 
>> Regards,
>> Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>> 
>>> On Apr 24, 2019, at 6:20 AM, Damjan Hajsek  wrote:
>>> 
>>> Hi
>>> What I did is first use some old weewx.conf file from last year and doesn't 
>>> work either.
>>> So I tried to reconfigure it but can't
>>> when I run wee_config --help I get list of help
>>> but when I do this I get
>>> wee_config /etc/weewx/weewx.conf
>>> No command specified.
>>> wee_config --config=/etc/weewx/weewx.conf
>>> No command specified.
>>> 
>>> 
>>> Dne torek, 23. april 2019 15.17.24 UTC+2 je oseba Leon Shaner napisala:
 
 Damian,
 
 These logs still do not state debug = 1.
 It still could be that the weewx.conf isn't being parsed correctly, and 
 isn't even able to read the debug = 1 setting.
 
 Did you try my suggestions for how to "rebuild" the conf file?
 
 Regards,
 Leon
 --
 Leon Shaner :: Dearborn, Michigan (iPhone)
 
 
> On Apr 23, 2019, at 8:45 AM, Damjan Hajsek  wrote:
> 
> Hi
> I have followed your instruction so I did all as described
> first turn off monit
> stop weewx
> debug = 1 was already set
> than I run weewx manually
> here is a log from that
> 
> http://zerobin.povej.net/?a63b7ac09e222bcc#9Y5+B9WWtxXgUJWTKZWmzElusp9QRgEK5Pde606SvQc=
> 
> http://zerobin.povej.net/?7d382c267025fd54#0p/b4Z0y5k7U3qFc8T/2Sgl0CbbU8ZkYxdSFCRh/I4I=
> 
> 
> Dne nedelja, 21. april 2019 15.41.04 UTC+2 je oseba mwall napisala:
>> 
>> at this point in the thread it is not clear what is happening or what is 
>> the state of your system.
>> 
>> so start over and explain what your configuration looks like now
>> 
>> then, to diagnose weewx, do the following:
>> 
>> - remove whatever it is that keeps restarting weewx
>> - stop weewx if it is running
>> - set debug=1 in your weewx configuration
>> - run weewx directly, not as a daemon
>> - if weewx crashes, post (1) the log prior to the crash, (2) the stack 
>> trace or other output from the console in which you started it
>> 
>> m
> 
> -- 
> 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...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this 

Re: [weewx-user] Re: weewx stop working

[Leon Shaner]

Damian,
You have to give wee_config a command.
>From the usage, you want this:

$ sudo wee_config --reconfigure --config=/etc/weewx/weewx.conf

(Although you can leave the --config part off, since your conf file is located 
in the default location).

But do be sure to back up the config file first...

Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On Apr 24, 2019, at 6:20 AM, Damjan Hajsek  wrote:
> 
> Hi
> What I did is first use some old weewx.conf file from last year and doesn't 
> work either.
> So I tried to reconfigure it but can't
> when I run wee_config --help I get list of help
> but when I do this I get
> wee_config /etc/weewx/weewx.conf
> No command specified.
> wee_config --config=/etc/weewx/weewx.conf
> No command specified.
> 
> 
> Dne torek, 23. april 2019 15.17.24 UTC+2 je oseba Leon Shaner napisala:
>> 
>> Damian,
>> 
>> These logs still do not state debug = 1.
>> It still could be that the weewx.conf isn't being parsed correctly, and 
>> isn't even able to read the debug = 1 setting.
>> 
>> Did you try my suggestions for how to "rebuild" the conf file?
>> 
>> Regards,
>> Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPhone)
>> 
>> 
>>> On Apr 23, 2019, at 8:45 AM, Damjan Hajsek  wrote:
>>> 
>>> Hi
>>> I have followed your instruction so I did all as described
>>> first turn off monit
>>> stop weewx
>>> debug = 1 was already set
>>> than I run weewx manually
>>> here is a log from that
>>> 
>>> http://zerobin.povej.net/?a63b7ac09e222bcc#9Y5+B9WWtxXgUJWTKZWmzElusp9QRgEK5Pde606SvQc=
>>> 
>>> http://zerobin.povej.net/?7d382c267025fd54#0p/b4Z0y5k7U3qFc8T/2Sgl0CbbU8ZkYxdSFCRh/I4I=
>>> 
>>> 
>>> Dne nedelja, 21. april 2019 15.41.04 UTC+2 je oseba mwall napisala:
 
 at this point in the thread it is not clear what is happening or what is 
 the state of your system.
 
 so start over and explain what your configuration looks like now
 
 then, to diagnose weewx, do the following:
 
 - remove whatever it is that keeps restarting weewx
 - stop weewx if it is running
 - set debug=1 in your weewx configuration
 - run weewx directly, not as a daemon
 - if weewx crashes, post (1) the log prior to the crash, (2) the stack 
 trace or other output from the console in which you started it
 
 m
>>> 
>>> -- 
>>> 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...@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.

-- 
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: weewx stop working

[Damjan Hajsek]

Hi
What I did is first use some old weewx.conf file from last year and doesn't 
work either.
So I tried to reconfigure it but can't
when I run wee_config --help I get list of help
but when I do this I get
wee_config /etc/weewx/weewx.conf
No command specified.
wee_config --config=/etc/weewx/weewx.conf
No command specified.


Dne torek, 23. april 2019 15.17.24 UTC+2 je oseba Leon Shaner napisala:
>
> Damian,
>
> These logs still do not state debug = 1.
> It still could be that the weewx.conf isn't being parsed correctly, and 
> isn't even able to read the debug = 1 setting.
>
> Did you try my suggestions for how to "rebuild" the conf file?
>
> Regards,
> Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPhone)
>
>
>
> On Apr 23, 2019, at 8:45 AM, Damjan Hajsek  > wrote:
>
> Hi
> I have followed your instruction so I did all as described
> first turn off monit
> stop weewx
> debug = 1 was already set
> than I run weewx manually
> here is a log from that
>
>
> http://zerobin.povej.net/?a63b7ac09e222bcc#9Y5+B9WWtxXgUJWTKZWmzElusp9QRgEK5Pde606SvQc=
>
>
> http://zerobin.povej.net/?7d382c267025fd54#0p/b4Z0y5k7U3qFc8T/2Sgl0CbbU8ZkYxdSFCRh/I4I=
>
>
> Dne nedelja, 21. april 2019 15.41.04 UTC+2 je oseba mwall napisala:
>>
>> at this point in the thread it is not clear what is happening or what is 
>> the state of your system.
>>
>> so start over and explain what your configuration looks like now
>>
>> then, to diagnose weewx, do the following:
>>
>> - remove whatever it is that keeps restarting weewx
>> - stop weewx if it is running
>> - set debug=1 in your weewx configuration
>> - run weewx directly, not as a daemon
>> - if weewx crashes, post (1) the log prior to the crash, (2) the stack 
>> trace or other output from the console in which you started it
>>
>> m
>>
> -- 
> 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...@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: weewx stop working

[Leon Shaner]

Damian,

These logs still do not state debug = 1.
It still could be that the weewx.conf isn't being parsed correctly, and isn't 
even able to read the debug = 1 setting.

Did you try my suggestions for how to "rebuild" the conf file?

Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPhone)


> On Apr 23, 2019, at 8:45 AM, Damjan Hajsek  wrote:
> 
> Hi
> I have followed your instruction so I did all as described
> first turn off monit
> stop weewx
> debug = 1 was already set
> than I run weewx manually
> here is a log from that
> 
> http://zerobin.povej.net/?a63b7ac09e222bcc#9Y5+B9WWtxXgUJWTKZWmzElusp9QRgEK5Pde606SvQc=
> 
> http://zerobin.povej.net/?7d382c267025fd54#0p/b4Z0y5k7U3qFc8T/2Sgl0CbbU8ZkYxdSFCRh/I4I=
> 
> 
> Dne nedelja, 21. april 2019 15.41.04 UTC+2 je oseba mwall napisala:
>> 
>> at this point in the thread it is not clear what is happening or what is the 
>> state of your system.
>> 
>> so start over and explain what your configuration looks like now
>> 
>> then, to diagnose weewx, do the following:
>> 
>> - remove whatever it is that keeps restarting weewx
>> - stop weewx if it is running
>> - set debug=1 in your weewx configuration
>> - run weewx directly, not as a daemon
>> - if weewx crashes, post (1) the log prior to the crash, (2) the stack trace 
>> or other output from the console in which you started it
>> 
>> m
> 
> -- 
> 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.

Re: [weewx-user] Re: weewx stop working

[mwall]

the logs that you posted do not have debug enabled

the logs that you posted do not show any crashes - they show you starting 
and stopping weewx 9 times.

why do you keep killing weewx?

you must do the following:

1 - set debug=1 in /etc/weewx/weewx.conf
2 - start weewx manually, i.e., 'sudo weewxd /etc/weewx/weewx.conf'
3 - let weewx run until it crashes
4 - when (if) weewx crashes,
4a - post the log from a few minutes prior to the crash up to the crash
4b - post the output from the console in which you ran weewx manually


On Tuesday, April 23, 2019 at 8:45:29 AM UTC-4, Damjan Hajsek wrote:
>
> Hi
> I have followed your instruction so I did all as described
> first turn off monit
> stop weewx
> debug = 1 was already set
> than I run weewx manually
> here is a log from that
>
>
> http://zerobin.povej.net/?a63b7ac09e222bcc#9Y5+B9WWtxXgUJWTKZWmzElusp9QRgEK5Pde606SvQc=
>
>
> http://zerobin.povej.net/?7d382c267025fd54#0p/b4Z0y5k7U3qFc8T/2Sgl0CbbU8ZkYxdSFCRh/I4I=
>

 

-- 
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: weewx stop working

[Damjan Hajsek]

Hi
I have followed your instruction so I did all as described
first turn off monit
stop weewx
debug = 1 was already set
than I run weewx manually
here is a log from that

http://zerobin.povej.net/?a63b7ac09e222bcc#9Y5+B9WWtxXgUJWTKZWmzElusp9QRgEK5Pde606SvQc=

http://zerobin.povej.net/?7d382c267025fd54#0p/b4Z0y5k7U3qFc8T/2Sgl0CbbU8ZkYxdSFCRh/I4I=


Dne nedelja, 21. april 2019 15.41.04 UTC+2 je oseba mwall napisala:
>
> at this point in the thread it is not clear what is happening or what is 
> the state of your system.
>
> so start over and explain what your configuration looks like now
>
> then, to diagnose weewx, do the following:
>
> - remove whatever it is that keeps restarting weewx
> - stop weewx if it is running
> - set debug=1 in your weewx configuration
> - run weewx directly, not as a daemon
> - if weewx crashes, post (1) the log prior to the crash, (2) the stack 
> trace or other output from the console in which you started it
>
> m
>

-- 
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: weewx stop working

[mwall]

at this point in the thread it is not clear what is happening or what is 
the state of your system.

so start over and explain what your configuration looks like now

then, to diagnose weewx, do the following:

- remove whatever it is that keeps restarting weewx
- stop weewx if it is running
- set debug=1 in your weewx configuration
- run weewx directly, not as a daemon
- if weewx crashes, post (1) the log prior to the crash, (2) the stack 
trace or other output from the console in which you started it

m

-- 
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: weewx stop working

[Damjan Hajsek]

I have manualls started interceptor, what can I expect from it, because 
nothing changes?
 PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py 
--device=observer --mode=listen --port=

Dne torek, 16. april 2019 11.16.05 UTC+2 je oseba gjr80 napisala:
>
> There have been no changes to the database since 3.8.1, but this is not a 
> database problem. WeeWX is event driven and it relies on loop packets 
> and/or archive records from the driver triggering events which then cause 
> archive records to be created and saved to the database, reports to be 
> generated etc. None of that is happening which makes me think there may be 
> a driver issue given we have ruled out any other obvious issue. You are 
> using the interceptor driver which, due to its nature, is susceptible to 
> changes in your network. Perhaps something has changed on your network? 
> Perhaps you should try running the interceptor driver directly to take 
> WeeWX out of the equation and ensure you can get data from the interceptor 
> driver. Running the driver directly is covered in the interceptor driver 
> wiki entry. 
>
> I would not be re-installing, as someone else here once said 'this is 
> Linux not Windows'.
>
> Gary
>
> On Tuesday, 16 April 2019 17:56:56 UTC+10, Damjan Hajsek wrote:
>>
>> Thank you I did this and no luck.
>> Can you tell me are there any changes in databasebetween version 3.8.1 
>> and the latest version??
>> If not I will install new weewx with rpm and than use old database.
>> regards
>>
>> Dne petek, 12. april 2019 15.34.53 UTC+2 je oseba Leon Shaner napisala:
>>>
>>> Damian,
>>>
>>> The symptoms I mentioned where it seems like weewxd is waiting for input 
>>> could be due to an issue parsing your conf file.  The wee_debug info you 
>>> posted has these lines:
>>>
>>> # This section can adjust data using calibration expressions.
>>>
>>> [1] 
>>>
>>>
>>> That looks like garbage.
>>> And yet way before that you have the typical section:
>>>
>>> #   This section can adjust data using calibration expressions.
>>>
>>> [StdCalibrate]
>>>
>>> [[Corrections]]
>>> # For each type, an arbitrary calibration expression can be 
>>> given.
>>> # It should be in the units defined in the StdConvert section.
>>> # Example:
>>> foo = foo + 0.2
>>>
>>>
>>> ##
>>>
>>>
>>> I suggest you try commenting out that extraneous "[1]" by preceding it 
>>> with # a la:
>>>
>>> #[1]
>>>
>>> Other than that you may need to make a backup of your weewx.conf and run 
>>> wee_config.  It may be confused by your current conf file, just as weewxd 
>>> appears to be.
>>> If all else fails, remove your conf file, run wee_config, and use diff 
>>> against the backup to see what else you need to add back, but with care to 
>>> only put the important parameters and to not reintroduce corruption.
>>>
>>> Regards,
>>> Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPhone)
>>>
>>> https://twitter.com/AEtherZcythe
>>>
>>> On Apr 12, 2019, at 4:12 AM, Damjan Hajsek  wrote:
>>>
>>> hi
>>> here is my debug log.
>>>
>>> http://zerobin.povej.net/?6a7fc01d0616ffa9#Zj15RUTw5bxNGfoVlibcKTgn5D2oPqPX0Dg+rkHOeR4=
>>> don't know what happend here all what I do on server latelly was to 
>>> uninstall gnome desktop and reinstall it.
>>> Maybe is some part of python deleted or something like that?
>>>
>>> Damian
>>>
>>> Dne petek, 12. april 2019 01.14.27 UTC+2 je oseba gjr80 napisala:

 Let's be very clear here, you have logs they are not missing, that is 
 what you have been posting over the last 12 hours. It would seem that once 
 WeeWX has completed its loading/initialisation something is causing it to 
 die or otherwise not do anything. You say that the  last log extract 
 posted 
 was with debug = 1, I don't doubt you but the log extract you provided 
 is not with debug = 1. A log with debug = 1 will include somethign 
 like this:

 Apr  5 22:54:29 stretch7 weewx[1012]: Starting weewx weather system: 
 weewx.
 Apr  5 22:54:29 stretch7 weewx[1024]: engine: Locale is 'en_AU.UTF-8'
 Apr  5 22:54:29 stretch7 weewx[1024]: engine: pid file is /var/run/
 weewx.pid
 Apr  5 22:54:29 stretch7 weewx[1028]: engine: Using configuration file 
 /home/weewx/weewx.conf
 Apr  5 22:54:29 stretch7 weewx[1028]: engine: debug is 1
 Apr  5 22:54:29 stretch7 weewx[1028]: engine: Initializing engine
 Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading station type 
 Simulator (weewx.drivers.simulator)
 Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading service weewx.
 engine.StdTimeSynch
 Apr  5 22:54:29 stretch7 weewx[1028]: engine: Finished loading service 
 weewx.engine.StdTimeSynch

 which shows debug is 1 and there is more detail about services being 
 loaded/initialised.

 I 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Thank you I did this and no luck.
Can you tell me are there any changes in databasebetween version 3.8.1 and 
the latest version??
If not I will install new weewx with rpm and than use old database.
regards

Dne petek, 12. april 2019 15.34.53 UTC+2 je oseba Leon Shaner napisala:
>
> Damian,
>
> The symptoms I mentioned where it seems like weewxd is waiting for input 
> could be due to an issue parsing your conf file.  The wee_debug info you 
> posted has these lines:
>
> # This section can adjust data using calibration expressions.
>
> [1] 
>
>
> That looks like garbage.
> And yet way before that you have the typical section:
>
> #   This section can adjust data using calibration expressions.
>
> [StdCalibrate]
>
> [[Corrections]]
> # For each type, an arbitrary calibration expression can be given.
> # It should be in the units defined in the StdConvert section.
> # Example:
> foo = foo + 0.2
>
>
> ##
>
>
> I suggest you try commenting out that extraneous "[1]" by preceding it 
> with # a la:
>
> #[1]
>
> Other than that you may need to make a backup of your weewx.conf and run 
> wee_config.  It may be confused by your current conf file, just as weewxd 
> appears to be.
> If all else fails, remove your conf file, run wee_config, and use diff 
> against the backup to see what else you need to add back, but with care to 
> only put the important parameters and to not reintroduce corruption.
>
> Regards,
> Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPhone)
>
> https://twitter.com/AEtherZcythe
>
> On Apr 12, 2019, at 4:12 AM, Damjan Hajsek  > wrote:
>
> hi
> here is my debug log.
>
> http://zerobin.povej.net/?6a7fc01d0616ffa9#Zj15RUTw5bxNGfoVlibcKTgn5D2oPqPX0Dg+rkHOeR4=
> don't know what happend here all what I do on server latelly was to 
> uninstall gnome desktop and reinstall it.
> Maybe is some part of python deleted or something like that?
>
> Damian
>
> Dne petek, 12. april 2019 01.14.27 UTC+2 je oseba gjr80 napisala:
>>
>> Let's be very clear here, you have logs they are not missing, that is 
>> what you have been posting over the last 12 hours. It would seem that once 
>> WeeWX has completed its loading/initialisation something is causing it to 
>> die or otherwise not do anything. You say that the  last log extract posted 
>> was with debug = 1, I don't doubt you but the log extract you provided 
>> is not with debug = 1. A log with debug = 1 will include somethign like 
>> this:
>>
>> Apr  5 22:54:29 stretch7 weewx[1012]: Starting weewx weather system: 
>> weewx.
>> Apr  5 22:54:29 stretch7 weewx[1024]: engine: Locale is 'en_AU.UTF-8'
>> Apr  5 22:54:29 stretch7 weewx[1024]: engine: pid file is /var/run/weewx.
>> pid
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Using configuration file /
>> home/weewx/weewx.conf
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: debug is 1
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Initializing engine
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading station type 
>> Simulator (weewx.drivers.simulator)
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading service weewx.
>> engine.StdTimeSynch
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Finished loading service 
>> weewx.engine.StdTimeSynch
>>
>> which shows debug is 1 and there is more detail about services being 
>> loaded/initialised.
>>
>> I think it might be a good time to have a look at your weewx.conf. Can 
>> you run the wee_debug utility 
>>  and post its 
>> output. The advantage of running wee_debug is that it will locate the 
>> weewx.conf that WeeWX is using which is handy if you have more than one 
>> weewx.conf on your system. Before you post the wee_debug output just 
>> check the output for sensitive info like usernames, passwords, api keys 
>> etc. wee_debug does a good job at obfuscating such info but it's not 
>> perfect.
>>
>> Gary
>>
>> On Friday, 12 April 2019 02:37:20 UTC+10, Damjan Hajsek wrote:
>>>
>>> Hi
>>>
>>> [image: 2019-04-11 18_34_45-_etc_weewx_weewx.conf - root@194.249.178.190 
>>> - Editor - WinSCP.png]
>>> Yes I really changed debug to 1 in conf file. I am from GMT +2
>>> And I tested, date shows real date and time as it should be
>>> Why there is no logs I don't know, that is all what I get for fev hours 
>>> after starting it manually.
>>>
>>> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala:

 Hi, Damjan,

 I do not see debug output.  Did you change debug = 0 to debug = 1 in 
 the conf file?

 Other than that, there is a thread where folks mentioned issues when 
 the date is off by too much...
 I can't tell what time zone your host is set to, but I would guess UTC 
 or GMT, no?
 In my case I have the host time zone set to my local time zone and when 
 I type "date" it shows the current local time.   Mine works, so it 

Re: [weewx-user] Re: weewx stop working

[Leon Shaner]

Damian,

The symptoms I mentioned where it seems like weewxd is waiting for input could 
be due to an issue parsing your conf file.  The wee_debug info you posted has 
these lines:

# This section can adjust data using calibration expressions.

[1]


That looks like garbage.
And yet way before that you have the typical section:

#   This section can adjust data using calibration expressions.

[StdCalibrate]

[[Corrections]]
# For each type, an arbitrary calibration expression can be given.
# It should be in the units defined in the StdConvert section.
# Example:
foo = foo + 0.2

##


I suggest you try commenting out that extraneous "[1]" by preceding it with # a 
la:

#[1]

Other than that you may need to make a backup of your weewx.conf and run 
wee_config.  It may be confused by your current conf file, just as weewxd 
appears to be.
If all else fails, remove your conf file, run wee_config, and use diff against 
the backup to see what else you need to add back, but with care to only put the 
important parameters and to not reintroduce corruption.

Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPhone)
https://twitter.com/AEtherZcythe

> On Apr 12, 2019, at 4:12 AM, Damjan Hajsek  wrote:
> 
> hi
> here is my debug log.
> http://zerobin.povej.net/?6a7fc01d0616ffa9#Zj15RUTw5bxNGfoVlibcKTgn5D2oPqPX0Dg+rkHOeR4=
> don't know what happend here all what I do on server latelly was to uninstall 
> gnome desktop and reinstall it.
> Maybe is some part of python deleted or something like that?
> 
> Damian
> 
> Dne petek, 12. april 2019 01.14.27 UTC+2 je oseba gjr80 napisala:
>> 
>> Let's be very clear here, you have logs they are not missing, that is what 
>> you have been posting over the last 12 hours. It would seem that once WeeWX 
>> has completed its loading/initialisation something is causing it to die or 
>> otherwise not do anything. You say that the  last log extract posted was 
>> with debug = 1, I don't doubt you but the log extract you provided is not 
>> with debug = 1. A log with debug = 1 will include somethign like this:
>> 
>> Apr  5 22:54:29 stretch7 weewx[1012]: Starting weewx weather system: weewx.
>> Apr  5 22:54:29 stretch7 weewx[1024]: engine: Locale is 'en_AU.UTF-8'
>> Apr  5 22:54:29 stretch7 weewx[1024]: engine: pid file is /var/run/weewx.pid
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Using configuration file 
>> /home/weewx/weewx.conf
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: debug is 1
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Initializing engine
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading station type Simulator 
>> (weewx.drivers.simulator)
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading service 
>> weewx.engine.StdTimeSynch
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Finished loading service 
>> weewx.engine.StdTimeSynch
>> 
>> which shows debug is 1 and there is more detail about services being 
>> loaded/initialised.
>> 
>> I think it might be a good time to have a look at your weewx.conf. Can you 
>> run the wee_debug utility and post its output. The advantage of running 
>> wee_debug is that it will locate the weewx.conf that WeeWX is using which is 
>> handy if you have more than one weewx.conf on your system. Before you post 
>> the wee_debug output just check the output for sensitive info like 
>> usernames, passwords, api keys etc. wee_debug does a good job at obfuscating 
>> such info but it's not perfect.
>> 
>> Gary
>> 
>>> On Friday, 12 April 2019 02:37:20 UTC+10, Damjan Hajsek wrote:
>>> Hi
>>> 
>>> 
>>> Yes I really changed debug to 1 in conf file. I am from GMT +2
>>> And I tested, date shows real date and time as it should be
>>> Why there is no logs I don't know, that is all what I get for fev hours 
>>> after starting it manually.
>>> 
>>> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala:
 
 Hi, Damjan,
 
 I do not see debug output.  Did you change debug = 0 to debug = 1 in the 
 conf file?
 
 Other than that, there is a thread where folks mentioned issues when the 
 date is off by too much...
 I can't tell what time zone your host is set to, but I would guess UTC or 
 GMT, no?
 In my case I have the host time zone set to my local time zone and when I 
 type "date" it shows the current local time.   Mine works, so it could be 
 a factor.
 
 Other than that, I posted just yesterday about an issue with 
 Wunderground-RF (rapid fire) not working unless I also explicitly forced 
 Wunderground-PWS on.  The setting to do that is in the Wunderground 
 section and you can try adding it right under the rapidfire = True a la:
 
  archive_post = True
 
 I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it might 
 not be the issue in your case.
 
 Regards,
 Leon
 --
 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

hi
here is my debug log.
http://zerobin.povej.net/?6a7fc01d0616ffa9#Zj15RUTw5bxNGfoVlibcKTgn5D2oPqPX0Dg+rkHOeR4=
don't know what happend here all what I do on server latelly was to 
uninstall gnome desktop and reinstall it.
Maybe is some part of python deleted or something like that?

Damian

Dne petek, 12. april 2019 01.14.27 UTC+2 je oseba gjr80 napisala:
>
> Let's be very clear here, you have logs they are not missing, that is what 
> you have been posting over the last 12 hours. It would seem that once WeeWX 
> has completed its loading/initialisation something is causing it to die or 
> otherwise not do anything. You say that the  last log extract posted was 
> with debug = 1, I don't doubt you but the log extract you provided is not 
> with debug = 1. A log with debug = 1 will include somethign like this:
>
> Apr  5 22:54:29 stretch7 weewx[1012]: Starting weewx weather system: weewx
> .
> Apr  5 22:54:29 stretch7 weewx[1024]: engine: Locale is 'en_AU.UTF-8'
> Apr  5 22:54:29 stretch7 weewx[1024]: engine: pid file is /var/run/weewx.
> pid
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Using configuration file /
> home/weewx/weewx.conf
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: debug is 1
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Initializing engine
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading station type 
> Simulator (weewx.drivers.simulator)
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading service weewx.engine
> .StdTimeSynch
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Finished loading service 
> weewx.engine.StdTimeSynch
>
> which shows debug is 1 and there is more detail about services being 
> loaded/initialised.
>
> I think it might be a good time to have a look at your weewx.conf. Can 
> you run the wee_debug utility 
>  and post its 
> output. The advantage of running wee_debug is that it will locate the 
> weewx.conf that WeeWX is using which is handy if you have more than one 
> weewx.conf on your system. Before you post the wee_debug output just 
> check the output for sensitive info like usernames, passwords, api keys 
> etc. wee_debug does a good job at obfuscating such info but it's not 
> perfect.
>
> Gary
>
> On Friday, 12 April 2019 02:37:20 UTC+10, Damjan Hajsek wrote:
>>
>> Hi
>>
>> [image: 2019-04-11 18_34_45-_etc_weewx_weewx.conf - root@194.249.178.190 
>> - Editor - WinSCP.png]
>> Yes I really changed debug to 1 in conf file. I am from GMT +2
>> And I tested, date shows real date and time as it should be
>> Why there is no logs I don't know, that is all what I get for fev hours 
>> after starting it manually.
>>
>> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala:
>>>
>>> Hi, Damjan,
>>>
>>> I do not see debug output.  Did you change debug = 0 to debug = 1 in the 
>>> conf file?
>>>
>>> Other than that, there is a thread where folks mentioned issues when the 
>>> date is off by too much...
>>> I can't tell what time zone your host is set to, but I would guess UTC 
>>> or GMT, no?
>>> In my case I have the host time zone set to my local time zone and when 
>>> I type "date" it shows the current local time.   Mine works, so it could be 
>>> a factor.
>>>
>>> Other than that, I posted just yesterday about an issue with 
>>> Wunderground-RF (rapid fire) not working unless I also explicitly forced 
>>> Wunderground-PWS on.  The setting to do that is in the Wunderground section 
>>> and you can try adding it right under the rapidfire = True a la:
>>>
>>>  archive_post = True
>>>
>>> I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it 
>>> might not be the issue in your case.
>>>
>>> Regards,
>>> Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>>
>>> On Apr 11, 2019, at 11:35 AM, Damjan Hajsek  wrote:
>>>
>>> Here is log with debug enabled.
>>>
>>>
>>> http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0=
>>>
>>>
>>> Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala:

 Ok, so you do have logs. The startup log extract you posted looks fine 
 to me. What's happens next in the log? Need to see at least the next 5 
 minutes of log.

 Not that it seems to be required but your attempt at running WeeWX 
 directly failed because WeeWX could not find weewx.conf, you need to 
 provide the path to weewx.conf in full eg:

 $ sudo weewxd /etc/weewx/weewx.conf

 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...@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 

Re: [weewx-user] Re: weewx stop working

[Leon Shaner]

Damian,

It's really strange that there is no mention of debug = 1 in the log.  
Normally, when debug = 1 is actually working, the log mentions it.  :-/

We know you are using /etc/weewx/weewx.conf, because it's there in the "ps -ef" 
output.

Another thing that is strange is while we can see that the weewxd process was 
started at 18:50 local time, it has used only 00:00:00 cpu time.  It seems as 
if something has stopped the process from executing further.   Or that it is 
blocked, waiting on some kind of input.

If nothing else, maybe gdb could offer some clues?

See here:

https://medium.com/python-pandemonium/debugging-an-inactive-python-process-2b11f88730c7

Meanwhile, perhaps consider upgrading to 1.3.9-1 (from your 1.3.8) and try 
again?

Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On Apr 11, 2019, at 12:55 PM, Damjan Hajsek  wrote:
> 
> Hi
> I have checked debug and it is only once and it is on 1.
> my logs are in /var/log/messages (centos 7)
> And I already did that but there was no weewx logs. I also have webmin and 
> have filtered out all weewx logs, which you already see it.
> 
> [root@localhost ~]# ps -ef | grep weewx | grep -v grep
> root 19180 1  0 18:50 ?00:00:00 python /usr/bin/weewxd 
> --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
> regards
> Damian
> 
> Dne četrtek, 11. april 2019 18.44.50 UTC+2 je oseba Leon Shaner napisala:
>> 
>> Hi, Damjan,
>> 
>> Just to rule out whether "debug" appears in the log file more than once you 
>> could do this:
>> 
>> $ grep 'debug' /etc/weewx/weewx.conf
>> 
>> If there is a debug = 1 followed later by debug = 0 (and it is not commented 
>> out with a preceeding #), then the later one will likely take precedence.
>> 
>> And to see if the daemon is dying somehow unexpectedly, please paste the 
>> output from this command:
>> 
>> $ ps -ef | grep weewx | grep -v grep
>> 
>> One more thing.  My logs go to syslog.  Just to rule it out, you could try 
>> grep'ing there:
>> 
>> $ grep weewx /var/log/syslog
>> 
>> And to make a copy to share, it would be something like:
>> 
>> $ grep weewx /var/log/syslog > /var/tmp/weewx.log
>> 
>> (And you could upload /var/tmp/weewx.log, but only if it actually has recent 
>> log entries).
>> 
>> Regards,
>> Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>> 
>>> On Apr 11, 2019, at 12:37 PM, Damjan Hajsek  wrote:
>>> 
>>> Hi
>>> <2019-04-11 18_34_45-_etc_weewx_weewx.conf - ro...@194.249.178.190 - Editor 
>>> - WinSCP.png>
>>> 
>>> Yes I really changed debug to 1 in conf file. I am from GMT +2
>>> And I tested, date shows real date and time as it should be
>>> Why there is no logs I don't know, that is all what I get for fev hours 
>>> after starting it manually.
>>> 
>>> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala:
 
 Hi, Damjan,
 
 I do not see debug output.  Did you change debug = 0 to debug = 1 in the 
 conf file?
 
 Other than that, there is a thread where folks mentioned issues when the 
 date is off by too much...
 I can't tell what time zone your host is set to, but I would guess UTC or 
 GMT, no?
 In my case I have the host time zone set to my local time zone and when I 
 type "date" it shows the current local time.   Mine works, so it could be 
 a factor.
 
 Other than that, I posted just yesterday about an issue with 
 Wunderground-RF (rapid fire) not working unless I also explicitly forced 
 Wunderground-PWS on.  The setting to do that is in the Wunderground 
 section and you can try adding it right under the rapidfire = True a la:
 
  archive_post = True
 
 I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it might 
 not be the issue in your case.
 
 Regards,
 Leon
 --
 Leon Shaner :: Dearborn, Michigan (iPad Pro)
 
> On Apr 11, 2019, at 11:35 AM, Damjan Hajsek  wrote:
> 
> Here is log with debug enabled.
> 
> http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0=
> 
> 
> Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala:
>> 
>> Ok, so you do have logs. The startup log extract you posted looks fine 
>> to me. What's happens next in the log? Need to see at least the next 5 
>> minutes of log.
>> Not that it seems to be required but your attempt at running WeeWX 
>> directly failed because WeeWX could not find weewx.conf, you need to 
>> provide the path to weewx.conf in full eg:
>> 
>> $ sudo weewxd /etc/weewx/weewx.conf
>> 
>> 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...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> 

Re: [weewx-user] Re: weewx stop working

[gjr80]

Let's be very clear here, you have logs they are not missing, that is what 
you have been posting over the last 12 hours. It would seem that once WeeWX 
has completed its loading/initialisation something is causing it to die or 
otherwise not do anything. You say that the  last log extract posted was 
with debug = 1, I don't doubt you but the log extract you provided is not 
with debug = 1. A log with debug = 1 will include somethign like this:

Apr  5 22:54:29 stretch7 weewx[1012]: Starting weewx weather system: weewx.
Apr  5 22:54:29 stretch7 weewx[1024]: engine: Locale is 'en_AU.UTF-8'
Apr  5 22:54:29 stretch7 weewx[1024]: engine: pid file is /var/run/weewx.pid
Apr  5 22:54:29 stretch7 weewx[1028]: engine: Using configuration file /home
/weewx/weewx.conf
Apr  5 22:54:29 stretch7 weewx[1028]: engine: debug is 1
Apr  5 22:54:29 stretch7 weewx[1028]: engine: Initializing engine
Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading station type Simulator 
(weewx.drivers.simulator)
Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading service weewx.engine.
StdTimeSynch
Apr  5 22:54:29 stretch7 weewx[1028]: engine: Finished loading service weewx
.engine.StdTimeSynch

which shows debug is 1 and there is more detail about services being 
loaded/initialised.

I think it might be a good time to have a look at your weewx.conf. Can you 
run the wee_debug utility 
 and post its 
output. The advantage of running wee_debug is that it will locate the 
weewx.conf that WeeWX is using which is handy if you have more than one 
weewx.conf on your system. Before you post the wee_debug output just check 
the output for sensitive info like usernames, passwords, api keys etc. 
wee_debug does a good job at obfuscating such info but it's not perfect.

Gary

On Friday, 12 April 2019 02:37:20 UTC+10, Damjan Hajsek wrote:
>
> Hi
>
> [image: 2019-04-11 18_34_45-_etc_weewx_weewx.conf - root@194.249.178.190 - 
> Editor - WinSCP.png]
> Yes I really changed debug to 1 in conf file. I am from GMT +2
> And I tested, date shows real date and time as it should be
> Why there is no logs I don't know, that is all what I get for fev hours 
> after starting it manually.
>
> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala:
>>
>> Hi, Damjan,
>>
>> I do not see debug output.  Did you change debug = 0 to debug = 1 in the 
>> conf file?
>>
>> Other than that, there is a thread where folks mentioned issues when the 
>> date is off by too much...
>> I can't tell what time zone your host is set to, but I would guess UTC or 
>> GMT, no?
>> In my case I have the host time zone set to my local time zone and when I 
>> type "date" it shows the current local time.   Mine works, so it could be a 
>> factor.
>>
>> Other than that, I posted just yesterday about an issue with 
>> Wunderground-RF (rapid fire) not working unless I also explicitly forced 
>> Wunderground-PWS on.  The setting to do that is in the Wunderground section 
>> and you can try adding it right under the rapidfire = True a la:
>>
>>  archive_post = True
>>
>> I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it might 
>> not be the issue in your case.
>>
>> Regards,
>> Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On Apr 11, 2019, at 11:35 AM, Damjan Hajsek  wrote:
>>
>> Here is log with debug enabled.
>>
>>
>> http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0=
>>
>>
>> Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala:
>>>
>>> Ok, so you do have logs. The startup log extract you posted looks fine 
>>> to me. What's happens next in the log? Need to see at least the next 5 
>>> minutes of log.
>>>
>>> Not that it seems to be required but your attempt at running WeeWX 
>>> directly failed because WeeWX could not find weewx.conf, you need to 
>>> provide the path to weewx.conf in full eg:
>>>
>>> $ sudo weewxd /etc/weewx/weewx.conf
>>>
>>> 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...@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: weewx stop working

[Damjan Hajsek]

Hi
I have checked debug and it is only once and it is on 1.
my logs are in /var/log/messages (centos 7)
And I already did that but there was no weewx logs. I also have webmin and 
have filtered out all weewx logs, which you already see it.

[root@localhost ~]# ps -ef | grep weewx | grep -v grep
root 19180 1  0 18:50 ?00:00:00 python /usr/bin/weewxd 
--daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
regards
Damian

Dne četrtek, 11. april 2019 18.44.50 UTC+2 je oseba Leon Shaner napisala:
>
> Hi, Damjan,
>
> Just to rule out whether "debug" appears in the log file more than once 
> you could do this:
>
> $ grep 'debug' /etc/weewx/weewx.conf
>
> If there is a debug = 1 followed later by debug = 0 (and it is not 
> commented out with a preceeding #), then the later one will likely take 
> precedence.
>
> And to see if the daemon is dying somehow unexpectedly, please paste the 
> output from this command:
>
> $ ps -ef | grep weewx | grep -v grep
>
> One more thing.  My logs go to syslog.  Just to rule it out, you could try 
> grep'ing there:
>
> $ grep weewx /var/log/syslog
>
> And to make a copy to share, it would be something like:
>
> $ grep weewx /var/log/syslog > /var/tmp/weewx.log
>
> (And you could upload /var/tmp/weewx.log, but only if it actually has 
> recent log entries).
>
> Regards,
> Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On Apr 11, 2019, at 12:37 PM, Damjan Hajsek  > wrote:
>
> Hi
>
> <2019-04-11 18_34_45-_etc_weewx_weewx.conf - ro...@194.249.178.190 
>  - Editor - WinSCP.png>
> Yes I really changed debug to 1 in conf file. I am from GMT +2
> And I tested, date shows real date and time as it should be
> Why there is no logs I don't know, that is all what I get for fev hours 
> after starting it manually.
>
> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala:
>>
>> Hi, Damjan,
>>
>> I do not see debug output.  Did you change debug = 0 to debug = 1 in the 
>> conf file?
>>
>> Other than that, there is a thread where folks mentioned issues when the 
>> date is off by too much...
>> I can't tell what time zone your host is set to, but I would guess UTC or 
>> GMT, no?
>> In my case I have the host time zone set to my local time zone and when I 
>> type "date" it shows the current local time.   Mine works, so it could be a 
>> factor.
>>
>> Other than that, I posted just yesterday about an issue with 
>> Wunderground-RF (rapid fire) not working unless I also explicitly forced 
>> Wunderground-PWS on.  The setting to do that is in the Wunderground section 
>> and you can try adding it right under the rapidfire = True a la:
>>
>>  archive_post = True
>>
>> I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it might 
>> not be the issue in your case.
>>
>> Regards,
>> Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On Apr 11, 2019, at 11:35 AM, Damjan Hajsek  wrote:
>>
>> Here is log with debug enabled.
>>
>>
>> http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0=
>>
>>
>> Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala:
>>>
>>> Ok, so you do have logs. The startup log extract you posted looks fine 
>>> to me. What's happens next in the log? Need to see at least the next 5 
>>> minutes of log.
>>>
>>> Not that it seems to be required but your attempt at running WeeWX 
>>> directly failed because WeeWX could not find weewx.conf, you need to 
>>> provide the path to weewx.conf in full eg:
>>>
>>> $ sudo weewxd /etc/weewx/weewx.conf
>>>
>>> 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...@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...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
> <2019-04-11 18_34_45-_etc_weewx_weewx.conf - ro...@194.249.178.190 
>  - Editor - WinSCP.png>
>
>

-- 
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: weewx stop working

[Leon Shaner]

Hi, Damjan,

Just to rule out whether "debug" appears in the log file more than once you 
could do this:

$ grep 'debug' /etc/weewx/weewx.conf

If there is a debug = 1 followed later by debug = 0 (and it is not commented 
out with a preceeding #), then the later one will likely take precedence.

And to see if the daemon is dying somehow unexpectedly, please paste the output 
from this command:

$ ps -ef | grep weewx | grep -v grep

One more thing.  My logs go to syslog.  Just to rule it out, you could try 
grep'ing there:

$ grep weewx /var/log/syslog

And to make a copy to share, it would be something like:

$ grep weewx /var/log/syslog > /var/tmp/weewx.log

(And you could upload /var/tmp/weewx.log, but only if it actually has recent 
log entries).

Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

> On Apr 11, 2019, at 12:37 PM, Damjan Hajsek  wrote:
> 
> Hi
> <2019-04-11 18_34_45-_etc_weewx_weewx.conf - root@194.249.178.190 - Editor - 
> WinSCP.png>
> 
> Yes I really changed debug to 1 in conf file. I am from GMT +2
> And I tested, date shows real date and time as it should be
> Why there is no logs I don't know, that is all what I get for fev hours after 
> starting it manually.
> 
> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala:
>> 
>> Hi, Damjan,
>> 
>> I do not see debug output.  Did you change debug = 0 to debug = 1 in the 
>> conf file?
>> 
>> Other than that, there is a thread where folks mentioned issues when the 
>> date is off by too much...
>> I can't tell what time zone your host is set to, but I would guess UTC or 
>> GMT, no?
>> In my case I have the host time zone set to my local time zone and when I 
>> type "date" it shows the current local time.   Mine works, so it could be a 
>> factor.
>> 
>> Other than that, I posted just yesterday about an issue with Wunderground-RF 
>> (rapid fire) not working unless I also explicitly forced Wunderground-PWS 
>> on.  The setting to do that is in the Wunderground section and you can try 
>> adding it right under the rapidfire = True a la:
>> 
>>  archive_post = True
>> 
>> I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it might 
>> not be the issue in your case.
>> 
>> Regards,
>> Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>> 
>>> On Apr 11, 2019, at 11:35 AM, Damjan Hajsek  wrote:
>>> 
>>> Here is log with debug enabled.
>>> 
>>> http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0=
>>> 
>>> 
>>> Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala:
 
 Ok, so you do have logs. The startup log extract you posted looks fine to 
 me. What's happens next in the log? Need to see at least the next 5 
 minutes of log.
 Not that it seems to be required but your attempt at running WeeWX 
 directly failed because WeeWX could not find weewx.conf, you need to 
 provide the path to weewx.conf in full eg:
 
 $ sudo weewxd /etc/weewx/weewx.conf
 
 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...@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.
> <2019-04-11 18_34_45-_etc_weewx_weewx.conf - root@194.249.178.190 - Editor - 
> WinSCP.png>

-- 
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: weewx stop working

[Damjan Hajsek]

Here is log with debug enabled.

http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0=


Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala:
>
> Ok, so you do have logs. The startup log extract you posted looks fine to 
> me. What's happens next in the log? Need to see at least the next 5 minutes 
> of log.
>
> Not that it seems to be required but your attempt at running WeeWX 
> directly failed because WeeWX could not find weewx.conf, you need to 
> provide the path to weewx.conf in full eg:
>
> $ sudo weewxd /etc/weewx/weewx.conf
>
> 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: weewx stop working

[gjr80]

Ok, so you do have logs. The startup log extract you posted looks fine to me. 
What's happens next in the log? Need to see at least the next 5 minutes of log.

Not that it seems to be required but your attempt at running WeeWX directly 
failed because WeeWX could not find weewx.conf, you need to provide the path to 
weewx.conf in full eg:

$ sudo weewxd /etc/weewx/weewx.conf

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: weewx stop working

[Damjan Hajsek]

this log is when I restart weewx
http://zerobin.povej.net/?d31ee849647759be#97lZ+kWzpA/GMSj9XL9BOVz6N9QqRWbm513C1W4Qf+c=

when I start it directly I get this

[root@localhost /]# sudo weewxd weewx.conf
Unable to open configuration file /weewx.confTraceback (most recent call 
last):
  File "/bin/weewxd", line 64, in 
weewx.engine.main(options, args)
  File "/usr/share/weewx/weewx/engine.py", line 846, in main
config_dict = getConfiguration(config_path)
  File "/usr/share/weewx/weewx/engine.py", line 958, in getConfiguration
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/site-packages/configobj.py", line 1242, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/site-packages/configobj.py", line 1254, in _load
raise IOError('Config file not found: "%s".' % self.filename)
IOError: Config file not found: "/weewx.conf".


Dne četrtek, 11. april 2019 12.05.21 UTC+2 je oseba gjr80 napisala:
>
> Whether WeeWX runs properly or not there should be some log output 
> indicating WeeWX tried to start.  No matter. What happens when you try to 
> run WeeWX directly (http://weewx.com/docs/usersguide.htm#Running_directly). 
> Please post all of the screen output, including the command you entered.
>
> 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: weewx stop working

[gjr80]

Whether WeeWX runs properly or not there should be some log output indicating 
WeeWX tried to start.  No matter. What happens when you try to run WeeWX 
directly (http://weewx.com/docs/usersguide.htm#Running_directly). Please post 
all of the screen output, including the command you entered.

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: weewx stop working

[Damjan Hajsek]

I have posted logs and last logs are from april 1. when weewxwas running 
and latest logs are only when I restart weewx and nothing else. 

Dne četrtek, 11. april 2019 10.48.17 UTC+2 je oseba gjr80 napisala:
>
> I am afraid until you can find where your WeeWX log is being written there 
> is little we can do to help you with WeeWX. Perhaps some Googling or a 
> support forum for your flavour of Linux might be able to help.
>
> Gary
>
> On Wednesday, 10 April 2019 17:00:37 UTC+10, Damjan Hajsek wrote:
>>
>> Any help here please? I am stuck, nothing works.
>>
>> Dne nedelja, 07. april 2019 21.57.30 UTC+2 je oseba Damjan Hajsek 
>> napisala:
>>>
>>> I have set debug = 3
>>> but there is all of log I have, I posted it already.
>>> my console is connected and working.
>>>
>>>
>>> Dne nedelja, 07. april 2019 20.56.17 UTC+2 je oseba vince napisala:

 On Sunday, April 7, 2019 at 11:23:59 AM UTC-7, Damjan Hajsek wrote:
>
> I have installed with setup.py.
> Now I am thinking to use rpm and database from old setup.
> Any idea what I need to do to transfer all what I need?
>
>>
>>
 I think you need to slow down and stop changing things so we can try to 
 help.

 I've run weewx on centos6 and centos7 from both rpm and setup.py and it 
 works fine for the Simulator driver.

 If it previously worked and you didn't change anything, and it stopped 
 working a few days ago, it is likely that it is not weewx nor the os.  
 It's 
 more likely that you either lost connection to your database server (if it 
 is on a second system) or to your station.   Set debug=1 in weewx.conf and 
 restart weewx and provide more log info if it stops working again.




-- 
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: weewx stop working

[gjr80]

I am afraid until you can find where your WeeWX log is being written there 
is little we can do to help you with WeeWX. Perhaps some Googling or a 
support forum for your flavour of Linux might be able to help.

Gary

On Wednesday, 10 April 2019 17:00:37 UTC+10, Damjan Hajsek wrote:
>
> Any help here please? I am stuck, nothing works.
>
> Dne nedelja, 07. april 2019 21.57.30 UTC+2 je oseba Damjan Hajsek napisala:
>>
>> I have set debug = 3
>> but there is all of log I have, I posted it already.
>> my console is connected and working.
>>
>>
>> Dne nedelja, 07. april 2019 20.56.17 UTC+2 je oseba vince napisala:
>>>
>>> On Sunday, April 7, 2019 at 11:23:59 AM UTC-7, Damjan Hajsek wrote:

 I have installed with setup.py.
 Now I am thinking to use rpm and database from old setup.
 Any idea what I need to do to transfer all what I need?

>
>
>>> I think you need to slow down and stop changing things so we can try to 
>>> help.
>>>
>>> I've run weewx on centos6 and centos7 from both rpm and setup.py and it 
>>> works fine for the Simulator driver.
>>>
>>> If it previously worked and you didn't change anything, and it stopped 
>>> working a few days ago, it is likely that it is not weewx nor the os.  It's 
>>> more likely that you either lost connection to your database server (if it 
>>> is on a second system) or to your station.   Set debug=1 in weewx.conf and 
>>> restart weewx and provide more log info if it stops working again.
>>>
>>>
>>>

-- 
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: weewx stop working

[Damjan Hajsek]

Any help here please? I am stuck, nothing works.

Dne nedelja, 07. april 2019 21.57.30 UTC+2 je oseba Damjan Hajsek napisala:
>
> I have set debug = 3
> but there is all of log I have, I posted it already.
> my console is connected and working.
>
>
> Dne nedelja, 07. april 2019 20.56.17 UTC+2 je oseba vince napisala:
>>
>> On Sunday, April 7, 2019 at 11:23:59 AM UTC-7, Damjan Hajsek wrote:
>>>
>>> I have installed with setup.py.
>>> Now I am thinking to use rpm and database from old setup.
>>> Any idea what I need to do to transfer all what I need?
>>>


>> I think you need to slow down and stop changing things so we can try to 
>> help.
>>
>> I've run weewx on centos6 and centos7 from both rpm and setup.py and it 
>> works fine for the Simulator driver.
>>
>> If it previously worked and you didn't change anything, and it stopped 
>> working a few days ago, it is likely that it is not weewx nor the os.  It's 
>> more likely that you either lost connection to your database server (if it 
>> is on a second system) or to your station.   Set debug=1 in weewx.conf and 
>> restart weewx and provide more log info if it stops working again.
>>
>>
>>

-- 
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: weewx stop working

[Damjan Hajsek]

I have set debug = 3
but there is all of log I have, I posted it already.
my console is connected and working.


Dne nedelja, 07. april 2019 20.56.17 UTC+2 je oseba vince napisala:
>
> On Sunday, April 7, 2019 at 11:23:59 AM UTC-7, Damjan Hajsek wrote:
>>
>> I have installed with setup.py.
>> Now I am thinking to use rpm and database from old setup.
>> Any idea what I need to do to transfer all what I need?
>>
>>>
>>>
> I think you need to slow down and stop changing things so we can try to 
> help.
>
> I've run weewx on centos6 and centos7 from both rpm and setup.py and it 
> works fine for the Simulator driver.
>
> If it previously worked and you didn't change anything, and it stopped 
> working a few days ago, it is likely that it is not weewx nor the os.  It's 
> more likely that you either lost connection to your database server (if it 
> is on a second system) or to your station.   Set debug=1 in weewx.conf and 
> restart weewx and provide more log info if it stops working again.
>
>
>

-- 
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: weewx stop working

[vince]

On Sunday, April 7, 2019 at 11:23:59 AM UTC-7, Damjan Hajsek wrote:
>
> I have installed with setup.py.
> Now I am thinking to use rpm and database from old setup.
> Any idea what I need to do to transfer all what I need?
>
>>
>>
I think you need to slow down and stop changing things so we can try to 
help.

I've run weewx on centos6 and centos7 from both rpm and setup.py and it 
works fine for the Simulator driver.

If it previously worked and you didn't change anything, and it stopped 
working a few days ago, it is likely that it is not weewx nor the os.  It's 
more likely that you either lost connection to your database server (if it 
is on a second system) or to your station.   Set debug=1 in weewx.conf and 
restart weewx and provide more log info if it stops working again.


-- 
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: weewx stop working

[Damjan Hajsek]

I have installed with setup.py.
Now I am thinking to use rpm and database from old setup.
Any idea what I need to do to transfer all what I need?

Dne nedelja, 07. april 2019 17.35.45 UTC+2 je oseba vince napisala:
>
> On Sunday, April 7, 2019 at 8:25:22 AM UTC-7, Damjan Hajsek wrote:
>>
>> Ok how to do that?
>> I have removed abrt-server and still the same problem.
>>
>>
>> Dne nedelja, 07. april 2019 15.17.01 UTC+2 je oseba jo...@johnkline.com 
>> napisala:
>>>
>>> The problem is in the log:
>>> abrt-server: Package 'weewx' isn't signed with proper key
>>
>>
>
> How did you install weewx ?
> Did you install a rpm or did you run setup.py ?
>
>

-- 
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: weewx stop working

[Damjan Hajsek]

I use default centos logging didn't change anything and this worked fev 
days ago and suddenly stopped.
What about if I install this regullyary with rmp and than use mysql 
database which is already stored?
Now I have manually installed weewx.

Dne nedelja, 07. april 2019 18.29.22 UTC+2 je oseba Thomas Keffer napisala:
>
> Well, it's hard to diagnose much of anything without the log. A Google 
> search shows that some CentOS installations 
>  do not use a traditional logging 
> daemon. For these, you must use the command journalctl. Try that. 
>
> -tk
>
> On Sat, Apr 6, 2019 at 11:13 PM Damjan Hajsek  > wrote:
>
>> Yes it is missing.
>> I have setup debug to 3 and when I start weewx I can see that in log, but 
>> only that and nothing else.
>> I have disabled SElinux and it is the same.
>>
>> Dne nedelja, 07. april 2019 06.14.05 UTC+2 je oseba Thomas Keffer 
>> napisala:
>>>
>>> On CentOS, your log should be in /var/log/messages. Are you saying that 
>>> is missing completely? 
>>>
>>> On Sat, Apr 6, 2019 at 2:08 PM Damjan Hajsek  
>>> wrote:
>>>
 I have done some more test and this is what I found out.
  detected unhandled Python exception in '/usr/bin/weewxd'
 don't know is this is the reason?

 Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek 
 napisala:
>
> I noticed that weewx stop working, so I have checked log and there is 
> no log. Than I restarted weex and it restart normally but still no logs.
> Any idea what can be wrong?? It worked for a long time with no problem 
> but suddenly it stopped
> It is version 3.8.1 and is installed on centos 7.6. and also use mysql 
> database for it.
>
> -- 
 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...@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...@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: weewx stop working

[Thomas Keffer]

Well, it's hard to diagnose much of anything without the log. A Google
search shows that some CentOS installations
 do not use a traditional logging
daemon. For these, you must use the command journalctl. Try that.

-tk

On Sat, Apr 6, 2019 at 11:13 PM Damjan Hajsek 
wrote:

> Yes it is missing.
> I have setup debug to 3 and when I start weewx I can see that in log, but
> only that and nothing else.
> I have disabled SElinux and it is the same.
>
> Dne nedelja, 07. april 2019 06.14.05 UTC+2 je oseba Thomas Keffer napisala:
>>
>> On CentOS, your log should be in /var/log/messages. Are you saying that
>> is missing completely?
>>
>> On Sat, Apr 6, 2019 at 2:08 PM Damjan Hajsek  wrote:
>>
>>> I have done some more test and this is what I found out.
>>>  detected unhandled Python exception in '/usr/bin/weewxd'
>>> don't know is this is the reason?
>>>
>>> Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek
>>> napisala:

 I noticed that weewx stop working, so I have checked log and there is
 no log. Than I restarted weex and it restart normally but still no logs.
 Any idea what can be wrong?? It worked for a long time with no problem
 but suddenly it stopped
 It is version 3.8.1 and is installed on centos 7.6. and also use mysql
 database for it.

 --
>>> 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...@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.
>

-- 
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: weewx stop working

[vince]

On Sunday, April 7, 2019 at 8:25:22 AM UTC-7, Damjan Hajsek wrote:
>
> Ok how to do that?
> I have removed abrt-server and still the same problem.
>
>
> Dne nedelja, 07. april 2019 15.17.01 UTC+2 je oseba jo...@johnkline.com 
> napisala:
>>
>> The problem is in the log:
>> abrt-server: Package 'weewx' isn't signed with proper key
>
>

How did you install weewx ?
Did you install a rpm or did you run setup.py ?

-- 
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: weewx stop working

[Damjan Hajsek]

Ok how to do that?
I have removed abrt-server and still the same problem.


Dne nedelja, 07. april 2019 15.17.01 UTC+2 je oseba jo...@johnkline.com 
napisala:
>
> The problem is in the log:
> abrt-server: Package 'weewx' isn't signed with proper key
>
>

-- 
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: weewx stop working

[john]

The problem is in the log:
abrt-server: Package 'weewx' isn't signed with proper key

-- 
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: weewx stop working

[Damjan Hajsek]

Ok here is log from april 1. there I can see reports from weewx and that 
was last reports.
Than on april 5. and 6. when I restarted weewx fev times, that is all what 
is in log.

I have put it in pastebin because there is alot of log.
http://zerobin.povej.net/?93548ecff653710f#UC94AO2wvBbQS6nOPg5Kic+iqz5qRCU4SiLkCE4Q0c4=


Dne nedelja, 07. april 2019 09.58.41 UTC+2 je oseba gjr80 napisala:
>
> Perhaps it is the language barrier but I for one am a little confused. Is 
> there any log output from WeeWX, anywhere? You said:
>
> I can see that in log
>>
>
> perhaps it is best that you post whatever it is you can see. Otherwise we 
> are just guessing.
>
> Gary
>
> On Sunday, 7 April 2019 16:13:15 UTC+10, Damjan Hajsek wrote:
>>
>> Yes it is missing.
>> I have setup debug to 3 and when I start weewx I can see that in log, but 
>> only that and nothing else.
>> I have disabled SElinux and it is the same.
>>
>> Dne nedelja, 07. april 2019 06.14.05 UTC+2 je oseba Thomas Keffer 
>> napisala:
>>>
>>> On CentOS, your log should be in /var/log/messages. Are you saying that 
>>> is missing completely? 
>>>
>>> On Sat, Apr 6, 2019 at 2:08 PM Damjan Hajsek  
>>> wrote:
>>>
 I have done some more test and this is what I found out.
  detected unhandled Python exception in '/usr/bin/weewxd'
 don't know is this is the reason?

 Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek 
 napisala:
>
> I noticed that weewx stop working, so I have checked log and there is 
> no log. Than I restarted weex and it restart normally but still no logs.
> Any idea what can be wrong?? It worked for a long time with no problem 
> but suddenly it stopped
> It is version 3.8.1 and is installed on centos 7.6. and also use mysql 
> database for it.
>
> -- 
 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...@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: weewx stop working

[gjr80]

Perhaps it is the language barrier but I for one am a little confused. Is 
there any log output from WeeWX, anywhere? You said:

I can see that in log
>

perhaps it is best that you post whatever it is you can see. Otherwise we 
are just guessing.

Gary

On Sunday, 7 April 2019 16:13:15 UTC+10, Damjan Hajsek wrote:
>
> Yes it is missing.
> I have setup debug to 3 and when I start weewx I can see that in log, but 
> only that and nothing else.
> I have disabled SElinux and it is the same.
>
> Dne nedelja, 07. april 2019 06.14.05 UTC+2 je oseba Thomas Keffer napisala:
>>
>> On CentOS, your log should be in /var/log/messages. Are you saying that 
>> is missing completely? 
>>
>> On Sat, Apr 6, 2019 at 2:08 PM Damjan Hajsek  wrote:
>>
>>> I have done some more test and this is what I found out.
>>>  detected unhandled Python exception in '/usr/bin/weewxd'
>>> don't know is this is the reason?
>>>
>>> Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek 
>>> napisala:

 I noticed that weewx stop working, so I have checked log and there is 
 no log. Than I restarted weex and it restart normally but still no logs.
 Any idea what can be wrong?? It worked for a long time with no problem 
 but suddenly it stopped
 It is version 3.8.1 and is installed on centos 7.6. and also use mysql 
 database for it.

 -- 
>>> 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...@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: weewx stop working

[Damjan Hajsek]

Yes it is missing.
I have setup debug to 3 and when I start weewx I can see that in log, but 
only that and nothing else.
I have disabled SElinux and it is the same.

Dne nedelja, 07. april 2019 06.14.05 UTC+2 je oseba Thomas Keffer napisala:
>
> On CentOS, your log should be in /var/log/messages. Are you saying that is 
> missing completely? 
>
> On Sat, Apr 6, 2019 at 2:08 PM Damjan Hajsek  > wrote:
>
>> I have done some more test and this is what I found out.
>>  detected unhandled Python exception in '/usr/bin/weewxd'
>> don't know is this is the reason?
>>
>> Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek napisala:
>>>
>>> I noticed that weewx stop working, so I have checked log and there is no 
>>> log. Than I restarted weex and it restart normally but still no logs.
>>> Any idea what can be wrong?? It worked for a long time with no problem 
>>> but suddenly it stopped
>>> It is version 3.8.1 and is installed on centos 7.6. and also use mysql 
>>> database for it.
>>>
>>> -- 
>> 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...@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: weewx stop working

[Thomas Keffer]

On CentOS, your log should be in /var/log/messages. Are you saying that is
missing completely?

On Sat, Apr 6, 2019 at 2:08 PM Damjan Hajsek 
wrote:

> I have done some more test and this is what I found out.
>  detected unhandled Python exception in '/usr/bin/weewxd'
> don't know is this is the reason?
>
> Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek napisala:
>>
>> I noticed that weewx stop working, so I have checked log and there is no
>> log. Than I restarted weex and it restart normally but still no logs.
>> Any idea what can be wrong?? It worked for a long time with no problem
>> but suddenly it stopped
>> It is version 3.8.1 and is installed on centos 7.6. and also use mysql
>> database for it.
>>
>> --
> 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.