That's good news Benjamin. Not sure why that would have fixed things, but if its working... I use nginx on my RPis as well, Apache is just too much of a hog for my liking and needs. Sometimes takes a little more effort to do something with nginx since a lot of things seems to have instructions for Apache.
Your comment re the SD card reminded me, do be careful if you are doing everything on SD card. There can be a lot of write activity on the card and some folks have had problems with longevity of cards. There are a myriad of ways to mitigate the issue; use a good quality SD card, logging to ramdisk, have weeWX generate to ramdisk, move all except boot partition to USB disk, install rorpi and the list goes on. A search of the forums will reveal quite a few threads and there is at least one wiki entry <https://github.com/weewx/weewx/wiki/Minimize-writes-on-SD-cards> that is relevant. Gary On Tuesday, 16 January 2018 14:24:46 UTC+10, Benjamin Fox wrote: > > > Hi Gary, > > The results of the logs overnight were fine mate. However, once I tested > rebooting the PI the error came back. > > So I bite the bullet ( had a spare SD card ), installed Raspbian from > scratch and installed Weewx via setup.py and decided to go > with nginx instead of apache. > > Guess what?? No issues. Even when powering down the pi and starting it up. > I'm not experiencing the same issues as before. Plus WU isn't reporting > any issues with RapidFire. > > Thank you for your help my friend. > > Take Care. > Benjamin > > -- 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.
