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 loading service
weewx.restx.StdAWEKAS
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.engine.StdPrint
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.engine.StdPrint
Jun 16 00:14:01 povej weewx[503]: engine: Loading service
weewx.engine.StdReport
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service
weewx.engine.StdReport
Jun 16 00:14:01 povej weewx[503]: engine: Starting up weewx version 3.9.1
Jun 16 00:14:01 povej weewx[503]: engine: Station does not support reading
the time
Jun 16 00:14:01 povej weewx[503]: engine: Starting main packet loop.
Jun 16 00:14:01 povej weewx[503]: manager: Daily summary version is 2.0
Jun 16 00:14:11 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:14:21 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:14:31 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:14:41 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:14:51 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:01 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:11 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:21 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:31 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:41 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:51 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:01 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:11 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:21 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:25 povej fail2ban.filter[28122]: INFO [apache-fakegooglebot]
Ignore 66.249.69.150 by command
Jun 16 00:16:25 povej fail2ban.filter[28122]: INFO [apache-fakegooglebot]
Ignore 66.249.69.150 by command
Jun 16 00:16:31 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:41 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:51 povej weewx[503]: interceptor: MainThread: empty queue
Dne sobota, 15. junij 2019 17.09.28 UTC+2 je oseba gjr80 napisala:
>
> 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 <[email protected]> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/2dc29325-db15-4831-899a-f256e2c024b4%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/weewx-user/2dc29325-db15-4831-899a-f256e2c024b4%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/193a67f5-661c-4552-95ff-79414012c679%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
