Yep, that was it. User perms. chmod'd /var/html/www/ files to weewx:weewx and its working as expected now.
Thanks!!! If you are at all interested I can write up how to do this on an LXC container. Its trivial really, Not at all unlike doing it on a "normal" machine. Prolly the dame for Docker too (but I have no Docker experience)? Mark On Monday, May 6, 2024 at 7:08:02 PM UTC-4 G7LTT wrote: > Aha! > > JINX!! > > We responded with more-or-less the same thing at the same time. > > Looking now at users perms etc. > > On Monday, May 6, 2024 at 7:02:57 PM UTC-4 Tom Keffer wrote: > >> A major change between V4 and V5 is daemon and file ownerships. By >> default, V5 runs as user "weewx", not "root." >> >> Be sure to check the Upgrade Guide >> <https://www.weewx.com/docs/5.0/upgrade/#weewx-runs-as-non-root-user>! >> >> >> On Mon, May 6, 2024 at 3:41 PM G7LTT <[email protected]> wrote: >> >>> And that's one of the issues. No logs are being written. /var/log/syslog >>> has nothing and neither does/var/log/weewx/weexd.log. The debug=1 setting >>> is set. >>> >>> This was working just fine under V4 so I can't believe its to do with >>> things like perms. >>> >>> "running a somewhat unusual setup"? I assume you have no other users >>> runing weewx in a container? Makes total sense to do it that way when you >>> think about it. Even on an RPi. Why waste a whole machine on such a trivial >>> task? >>> >>> I'll take another swing at it. see if I can't get some logging going. >>> >>> Mark >>> >>> On Sunday, May 5, 2024 at 4:53:16 PM UTC-4 vince wrote: >>> >>>> We can't read minds. Need to see actual logs with debug=1 set in >>>> weewx.conf and ideally your weewx.conf file as well. >>>> >>>> The usual error tends to be permissions accessing the hardware or the >>>> network itself. Considering you're running a somewhat unusual setup you >>>> might want to provide a way for folks to try to look at what you might be >>>> missing within your container image. >>>> >>>> >>>> On Sunday, May 5, 2024 at 12:39:03 PM UTC-7 G7LTT wrote: >>>> >>>>> So I upgraded to V5.0.4 from 4.whatever and it looked like everything >>>>> went ok. But then about an hour later I noticed that the web pages were >>>>> not >>>>> being updated. Off to the logs I go - nothing in the logs. >>>>> >>>>> Hmmnnn. OK, time to run it manually at the command line to see if it >>>>> spews anything out. Nope, works perfectly. I can leave "weewxd" running >>>>> for >>>>> hours without any error. And the pages get updated/uploaded etc etc etc. >>>>> What gives? >>>>> >>>>> I am running Weewx in an LXC container on Proxmox in my homelab >>>>> system. I have the Ambient WS2000 API installed (rather than talk to the >>>>> station it collects the station data from Ambient themselves). >>>>> >>>>> V4 was running as expected in daemon mode. It would survive a >>>>> reboot/restart of the machine and the container. V5? Not so much. But >>>>> there >>>>> are no entries in the log files for it which is making me suspicious. >>>>> >>>>> Any ideas? >>>>> >>>>> >>>>> >>>> -- >>> 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/0a125bbf-e4ca-429a-a7ea-6af232e67bb7n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/0a125bbf-e4ca-429a-a7ea-6af232e67bb7n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- 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/76a8df35-b6e4-48f6-99d7-7195ba222b88n%40googlegroups.com.
