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 <gjroder...@gmail.com> 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.
