Hard to say without seeing the log, which brings us to a deep flaw with Sierra: they changed the logging facility in such a way to make it extremely difficult to access it.
There is still the file /var/log/system.log, but it will only contain events with very high priority. To see the lower level events that weewx generates, you have to use their "unified logging" facility, which is extremely difficult to use. This kind of works for me: 1. Run weewx 2. Now check the log for the last few minutes, grepping for just the Python stuff: *log show --info --debug --last 3m | grep Python* There may be an easier way to do this, but it's the best I can come up with. Even so, it will only show the Python-related logging events, so you may miss some OS-related events that are relevant to your problem. Help from any Mac expert would be eagerly welcome! -tk On Mon, Apr 17, 2017 at 12:35 PM, MRL <[email protected]> wrote: > My thanks for the quick responses to get weeWX running on my Mac - the > change to setup.cfg did the trick. > Started the program and it is getting data from the Davis Vantage Pro/2. > Tons of png files in the public_html directory but no index.html > It has been about 30 minutes since the program started. > Program is continuing to read data - look OK. > > What happened to index.html? > Thanks 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 [email protected]. > 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]. For more options, visit https://groups.google.com/d/optout.
