Suppose a WeeWX service is augmenting loop packets. After some time passes, it starts to receive bad data, logs this information, and ignores the bad data. If the service continues to receive bad data it will ‘flood’ the log with these error messages. I see a few possible ways to stop this.
1. Throttle the logging. For example, after X errors only log every Nth message. 2. Have the service shut itself down. This would probably require accessing the engine’s internal callbacks data structure or an enhancement to allow ‘unbinding’ to events. 3. Raise an exception, causing WeeWX to terminate. At first glance 3 seems a bit severe. But if this data is critical, it could make sense to stop WeeWX. Option 2 intrigues me if the problem is due to the computer being stressed (CPU, RAM, network, etc.). Stopping the service might help determine if the service is the cause or not. Option 1 seems the simplest and leaves the possibility that good data will start arriving and everything will ‘self correct’ and is the option I am leaning towards. Thoughts? Thanks. - rich -- You received this message because you are subscribed to the Google Groups "weewx-development" 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-development/98b0d632-9b20-48b4-bbb9-57aba4ec8a19n%40googlegroups.com.
