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 <[email protected]> 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/57255078-0935-48db-b1c3-2ce7813b488a%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > <debug_disabled_weewx.txt> > <debug_enabled_weewx.txt> > <manual_log_weewx.txt> -- 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/B2D4D668-35E7-4F99-ABA9-EB37134AAEB7%40isylum.org. For more options, visit https://groups.google.com/d/optout.
