Just adding to last post, here are the logs on reboot: *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10_syslog-ng.init... Feb 15 23:12:47 HAL syslog-ng[15]: syslog-ng starting up; version='3.13.2' *** Booting runit daemon... *** Runit started as PID 22 using Feb 15 23:12:47 HAL weewx[30] INFO __main__: Initializing weewx version 4.6.2 Feb 15 23:12:47 HAL weewx[30] INFO __main__: Using Python 3.6.9 (default, Dec 8 2021, 21:08:43) [GCC 8.4.0] Feb 15 23:12:47 HAL weewx[30] INFO __main__: Platform Linux-5.10.0-0.bpo.9-amd64-x86_64-with-Ubuntu-18.04-bionic Feb 15 23:12:47 HAL weewx[30] INFO __main__: Locale is 'en_US.UTF-8' Feb 15 23:12:47 HAL weewx[30] INFO __main__: Using configuration file /home/weewx/weewx.conf Feb 15 23:12:47 HAL weewx[30] INFO __main__: Debug is 0 Feb 15 23:12:47 HAL weewx[30] INFO weewx.engine: Loading station type Simulator (weewx.drivers.simulator) Feb 15 23:12:47 HAL weewx[30] INFO weewx.engine: StdConvert target unit is 0x1 Feb 15 23:12:47 HAL weewx[30] INFO weewx.wxservices: StdWXCalculate will use data binding wx_binding Feb 15 23:12:48 HAL cron[26]: (CRON) INFO (pidfile fd = 3) Feb 15 23:12:48 HAL cron[26]: (CRON) INFO (Running @reboot jobs) Feb 15 23:12:48 HAL weewx[30] INFO weewx.manager: Created and initialized table 'archive' in database 'weewx.sdb' Feb 15 23:12:48 HAL weewx[30] INFO weewx.manager: Created daily summary tables Feb 15 23:12:48 HAL weewx[30] INFO weewx.engine: Archive will use data binding wx_binding Feb 15 23:12:48 HAL weewx[30] INFO weewx.engine: Record generation will be attempted in 'hardware' Feb 15 23:12:48 HAL weewx[30] INFO weewx.engine: Using archive interval of 300 seconds (specified in weewx configuration) Feb 15 23:12:48 HAL weewx[30] INFO weewx.restx: StationRegistry: Registration not requested. Feb 15 23:12:48 HAL weewx[30] INFO weewx.restx: Wunderground: Posting not enabled. Feb 15 23:12:48 HAL weewx[30] INFO weewx.restx: PWSweather: Posting not enabled. Feb 15 23:12:48 HAL weewx[30] INFO weewx.restx: CWOP: Posting not enabled. Feb 15 23:12:48 HAL weewx[30] INFO weewx.restx: WOW: Posting not enabled. Feb 15 23:12:48 HAL weewx[30] INFO weewx.restx: AWEKAS: Posting not enabled. Feb 15 23:12:48 HAL weewx[30] INFO weewx.engine: 'pyephem' detected, extended almanac data is available Feb 15 23:12:48 HAL weewx[30] INFO __main__: Starting up weewx version 4.6.2 Feb 15 23:12:48 HAL weewx[30] INFO weewx.engine: Clock error is -0.44 seconds (positive is fast) Feb 15 23:12:48 HAL weewx[30] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb' Feb 15 23:12:48 HAL weewx[30] INFO weewx.manager: Starting backfill of daily summaries Feb 15 23:12:48 HAL weewx[30] INFO weewx.manager: Empty database Feb 15 23:12:48 HAL weewx[30] INFO weewx.engine: Starting main packet loop. On Tuesday, February 15, 2022 at 6:08:11 PM UTC-5 Adam Morgan wrote: > Hello, I finally had some time to get back to this. I was hoping to > configure my upload to WU when I noticed that my WeeWx folder is empty. I > expected at the very least to see the configuration file. Am I missing > something? I scanned the docs - unless I am missing something it seems as > though this file should have been created for me. I used the yml > configuration that was posted earlier. > > [image: weewx.png] > > On Monday, February 14, 2022 at 11:41:59 AM UTC-5 Adam Morgan wrote: > >> Thank you again Doug! Ok, part of my issue was that I had not fully read >> through the docs. I haven't done a ton with Docker and all of the other >> containers that I had created were for apps that had their own web server >> where I would do the configuration. I spent a few minutes with the >> documentation right now - I see that the config is done in the >> configuration file and not in a UI. I may tackle the web server down the >> line - I really appreciate you including that. I am coming from Virtual >> Weather Station and my main goal is uploading to WU so that I can access >> via Alex by using some code that I wrote in AWS. For some reason my >> uploads to WU stopped working last year and their support refused to answer >> me. >> >> >> On Monday, February 14, 2022 at 10:53:00 AM UTC-5 [email protected] >> wrote: >> >>> Adam: >>> >>> By Default, each stack in Docker will have its own internal network. >>> These will show up as 172.16.x.x. That is ok as docker will route traffic >>> from the host to the container as long as you have the ports mapped >>> correctly. >>> >>> The next thing we need to check is to see if you have a http server >>> inside the container that you are running with WeeWx. Looking at felddy's >>> weewx-docker Dockerfile (weewx-docker/Dockerfile at develop · >>> felddy/weewx-docker · GitHub >>> <https://github.com/felddy/weewx-docker/blob/develop/Dockerfile>) I did >>> not see a http server serving the pages. So the html will not be viewable >>> without a http server. >>> >>> The best course of action here is to spin up a http server as a >>> container. I actually do this for my setup (www.largoweather.com) using >>> a nginx container. What i do is configure weewx to write to a directory >>> that is shared with the container. Then I add both containers to the same >>> yaml file and have them share the same network. >>> >>> Here is a copy of my yaml file. In it I am running Tom Mitchell's weewx >>> container (GitHub - tomdotorg/docker-weewx: Docker image for weewx >>> weather software <https://github.com/tomdotorg/docker-weewx>) with >>> Belchertown skin using a MQTT broker with a ngnix web server. You can >>> modify this to your liking. If you have any questions on the configs, just >>> let me know. >>> >>> # ====== WEEWX STACK START ====== >>> version: "2.1" >>> services: >>> web: >>> image: nginx >>> container_name: weewx_web >>> networks: >>> - wxnet >>> ports: >>> - 91:80 >>> depends_on: >>> - mqtt-broker >>> - weewx-engine >>> environment: >>> - TZ=America/New_York >>> - NGINX_HOST=<<YOUR-DOMAIN-NAME>>.com >>> - NGINX_PORT=80 >>> volumes: >>> - /media/docker/volumes/weewx/html:/usr/share/nginx/html:ro >>> - /media/docker/volumes/ngnix/templates:/etc/nginx/templates >>> restart: unless-stopped >>> >>> mqtt-broker: >>> image: eclipse-mosquitto:latest >>> container_name: weewx_mqtt >>> networks: >>> - wxnet >>> environment: >>> - TZ=America/New_York >>> volumes: >>> - /media/docker/volumes/weewx/mosquitto/config:/mosquitto/config >>> - /media/docker/volumes/weewx/mosquitto/data:/mosquitto/data >>> - /media/docker/volumes/weewx/mosquitto/log:/mosquitto/log >>> ports: >>> - 1883:1883 >>> - 9001:9001 >>> depends_on: >>> - weewx-engine >>> restart: unless-stopped >>> >>> weewx-engine: >>> image: mitct02/weewx:4.5.1 >>> container_name: weewx_engine >>> environment: >>> - TZ=America/New_York >>> networks: >>> - wxnet >>> privileged: true >>> volumes: >>> - /media/docker/volumes/weewx/config/:/home/weewx/conf/ >>> - >>> /media/docker/volumes/weewx/skins/Belchertown/:/home/weewx/skins/Belchertown/ >>> - /media/docker/volumes/weewx/html/:/home/weewx/public_html/ >>> restart: unless-stopped >>> >>> networks: >>> wxnet: >>> driver: bridge >>> >>> >>> # ====== WEEWX STACK STOP =======[ >>> >>> >>> >>> On Sunday, February 13, 2022 at 6:36:49 PM UTC-5 [email protected] >>> wrote: >>> >>>> Sorry, still struggling with this one. I don't want a new network >>>> created. Instead, I just want to bind to the host. Any help would be >>>> greatly appreciated. Thank you again! >>>> >>>> On Sunday, February 13, 2022 at 1:54:28 PM UTC-5 Adam Morgan wrote: >>>> >>>>> Thank you, that's a good thought. I did verify that nothing else is >>>>> using that port (I only have 10ish containers). >>>>> >>>>> I did notice that this created a new network. Could that be the >>>>> issue? In my limited experience I have only ever used "host". This is a >>>>> device running on my network and not local host - would that mean that I >>>>> can't use the IP of the host to access it through the browser? >>>>> >>>>> On Sunday, February 13, 2022 at 1:05:29 PM UTC-5 vince wrote: >>>>> >>>>>> I'd run "docker ps -a" and look at which containers are forwarding >>>>>> which ports. >>>>>> >>>>>>> >>>>>> -- 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/60e26057-d8cf-4243-a4ce-10e2b9651c93n%40googlegroups.com.
