Inconsistency in log report (sudo journalctl -u weewx -f) and contents of /var/www/html/weewx

30 views
Skip to first unread message

Jan Volschenk

unread,
6:00 AM (12 hours ago) 6:00 AM
to weewx...@googlegroups.com
Raspi and associated code is all new to me and my battle is ongoing:
  • My Ecowitt HP2553CA is linked to https://www.ecowitt.net/home/index?id=296225
  • I'm in the process of configuring  a Raspi 4 B with Weewx to place info on CWOP 
  • Allocated  CWOP ID:  GW7066 
  • However nothing reported on    http://www.findu.com/cgi-bin/wx.cgi?call=GW7066
  • My log report (sudo journalctl -u weewx -f) indicates:  "Copied 0 files to /var/www/html/weewx "
  • However /var/www/html/weewx shows multiple .png files with appropriate contents being updated every 5 minutes
I need some help as to what to do next!

Kind regards

Jan Volschenk
Amateur Radio Call-sign: ZS6VOL

John Smith

unread,
6:57 AM (11 hours ago) 6:57 AM
to weewx...@googlegroups.com
I always use tab completion and end up using -u weewx.service

--
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 weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAFrQ3S91eLj4vqbosYhzhh7SHgTPW4dr2yg-i_rLogbEYA1v%2BA%40mail.gmail.com.

Jan Volschenk

unread,
7:14 AM (11 hours ago) 7:14 AM
to weewx...@googlegroups.com
Hi John, thanks for the prompt reply, however I don't even have a vague idea what is meant by " use tab completion and end up using -u weewx.service"
 I'm not familiar with code and wouldn't know what to do!
Can you perhaps kindly provide me with more detail?



--
Kind regards
Jan
Amateur Radio Call-sign: ZS6VOL

Dominic ›OE7DRT‹

unread,
7:18 AM (11 hours ago) 7:18 AM
to weewx...@googlegroups.com
On 03.02.26 12:00, Jan Volschenk wrote:
> - I'm in the process of configuring a Raspi 4 B with Weewx to place
> info on CWOP
> - Allocated CWOP ID: GW7066
> - However nothing reported on
> http://www.findu.com/cgi-bin/wx.cgi?call=GW7066

A full log output would be helpful to get an idea whether it actually
wants to connect (maybe with added debug info?)

On weewx restart, there should be an indication if CWOP is enabled:

#v+
sudo systemctl restart weewx.service && journalctl -feu weewx.service
#v-

You should see something like this (may have to scroll a bit):
#v+
$date $hostname weewxd[8972]: INFO weewx.restx: StationRegistry:
Registration not requested.
$date $hostname weewxd[8972]: INFO weewx.restx: Wunderground: Posting
not enabled.
$date $hostname weewxd[8972]: INFO weewx.restx: PWSweather: Posting not
enabled.
$date $hostname weewxd[8972]: INFO weewx.restx: CWOP: Data for station
OE7DRT-13 will be posted
$date $hostname weewxd[8972]: INFO weewx.restx: WOW: Posting not enabled.
$date $hostname weewxd[8972]: INFO weewx.restx: AWEKAS: Posting not enabled.
#v-

> - My log report (sudo journalctl -u weewx -f) indicates: "Copied 0
> files to /var/www/html/weewx "

So nothing new copied, what is actually inside /var/www/html/weewx?
I guess the std report runs fine?

> - However /var/www/html/weewx shows multiple .png files with
> appropriate contents being updated every 5 minutes

What is inside this directory?

Did you configure the [[CWOP]] section within weewx.conf?

-dominic

--
A seed grows with no sound, but a tree falls with a huge noise.
Destruction has noise, but creation is quiet. This is the power of silence.
Grow silently.
- Confucius

John Smith

unread,
7:28 AM (10 hours ago) 7:28 AM
to weewx...@googlegroups.com
On Tue, 3 Feb 2026 at 23:14, Jan Volschenk <zs6...@gmail.com> wrote:
I don't even have a vague idea what is meant by " use tab completion and end up using -u weewx.service"

In Linux and various other systems you can hit the tab key part way through typing a command and the system will complete it for you up until there may need to be further input, in this case I start typing jou<tab> and journalctl shows up, then -u wee<tab> and I get journalctl -u weewx.service so on and so forth
 
 I'm not familiar with code and wouldn't know what to do!

Nothing to do with code, but commands in a terminal.

Jan Volschenk

unread,
8:50 AM (9 hours ago) 8:50 AM
to weewx...@googlegroups.com
Hi Dominic, Itried what you suggested and find the following:

Feb 03 13:14:31 pi3 weewxd[16306]: INFO weewx.restx: StationRegistry: Station will be registered.
Feb 03 13:14:31 pi3 weewxd[16306]: INFO weewx.restx: Wunderground: Posting not enabled.
Feb 03 13:14:31 pi3 weewxd[16306]: INFO weewx.restx: PWSweather: Posting not enabled.
Feb 03 13:14:31 pi3 weewxd[16306]: INFO weewx.restx: CWOP: Posting not enabled.
Feb 03 13:14:31 pi3 weewxd[16306]: INFO weewx.restx: WOW: Posting not enabled.
Feb 03 13:14:31 pi3 weewxd[16306]: INFO weewx.restx: WOW-BE: Posting not enabled.
Feb 03 13:14:31 pi3 weewxd[16306]: INFO weewx.restx: AWEKAS: Posting not enabled.

However my code for this section is the following:

Simulator]
    # This section is for the weewx weather station simulator.
   
    # The time (in seconds) between LOOP packets.
    #loop_interval = 2.5
   
    # The simulator mode can be either 'simulator' or 'generator'.
    # Real-time simulator. Sleep between each LOOP packet.
    # mode = simulator
    # Generator.  Emit LOOP packets as fast as possible (useful for testing).
    # mode = generator
   
    # The start time. Format is YYYY-mm-ddTHH:MM. If not specified, the
    # default is to use the present time.
    #start = 2011-01-01T00:00
   
    # The driver to use.
    # driver = weewx.drivers.ulator

##############################################################################

[FineOffsetUSB]
    # This section is for the Fine Offset series of weather stations.
   
    # The station model, e.g., WH1080, WS1090, WS2080, WH3081
    # model = WS2080
   
    # How often to poll the station for data, in seconds
    polling_interval = 60
   
    # The driver to use:
    driver = weewx.drivers.fousb

##############################################################################

#   This section is for uploading data to Internet sites

[StdRESTful]
   
    # Uncomment and change to override logging for uploading services.
     log_success = True
     log_failure = True
   
    [[StationRegistry]]
        # To register this weather station at weewx.com, set this to true, and
        # set option 'station_url', located in the [Station] section above.
        register_this_station = True
   
    [[AWEKAS]]
        # This section is for configuring posts to AWEKAS.
       
        # If you wish to post to AWEKAS, set the option 'enable' to true, then
        # specify a username and password.
        # Use quotes around the password to guard against parsing errors.
        enable = False
        # username = replace_me
        # password = replace_me
   
    [[CWOP]]
        # This section is for configuring posts to CWOP.
       
        # If you wish to post to CWOP, set the option 'enable' to true,
        # then specify the station ID (e.g., CW1234).
        enable = True
        station = GW7066
        # If this is an APRS (radio amateur) station, specify the
        # passcode (e.g., 12345). Otherwise, ignore.
        # passcode = replace_me
   
    [[PWSweather]]
        # This section is for configuring posts to PWSweather.com.
       
        # If you wish to post to PWSweather.com, set the option 'enable' to
        # true, then specify a station and password.
        # Use quotes around the password to guard against parsing errors.
        # enable = True
        station = replace_me
        password = replace_me
   
    [[WOW]]
        # This section is for configuring posts to WOW (wow.metoffice.gov.uk).
       
        # If you wish to post to WOW, set the option 'enable' to true, then
        # specify a station and password.
        # Use quotes around the password to guard against parsing errors.
        # enable = False
        station = replace_me
        password = replace_me
   
    [[WOW-BE]]
        # This section is for configuring WeeWX to upload to WOW-BE (wow.meteo.be)
       
        # If you wish to post to WOW-BE, set the option 'enable' to true, then
        # specify a station and password.
        # Use quotes around the password to guard against parsing errors.
        # enable = False
        station = replace_me
        password = replace_me
   
    [[Wunderground]]
        # This section is for configuring posts to the Weather Underground.
       
        # If you wish to post to the Weather Underground, set the option
        # 'enable' to true,  then specify a station (e.g., 'KORHOODR3'). Use
        # the station key (find it at
        # https://www.wunderground.com/member/devices) for the password.
        # enable = False
        station = IPRET0237
        password = FVKcMQiv
       
        # Set the following to True to have weewx use the WU "Rapidfire"
        # protocol. Not all hardware can support it. See the User's Guide.
        rapidfire = False

I'm sorry if I'm being long winded, but this is the only way I know of copying code !

Thanks for your patience



--
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 weewx-user+...@googlegroups.com.


--
Kind regards/ Vriendelike groete

Jan Volschenk, Pr Eng

Mobile: +27 (0)83 627 8690
Amateur Radio Call-sign: ZS6VOL

Vince Skahan

unread,
11:51 AM (6 hours ago) 11:51 AM
to weewx-user
A few things:
  • you really shouldn't post your unedited weewx.conf - (you appended your Wunderground username and password)
  • ignore the 'Copied 0 files to' messages.  It's normal and has nothing to do with CWOP uploads
  • set debug = 1 in your weewx.conf and restart weewx  to make that take effect
  • after you do this, we need to see your logs from weewx startup through one or two report intervals
So what to do....

1. We need to see your full config file.  There is an option in 'weectl' that can report your whole setup with the usernames/passwords obfuscated.
  • run "weectl debug --output=/tmp/debug.txt"
2. After you set debug = 1, restart weewx and lets see what your logs say.
  • restart weewx via "sudo systemctl restart weewx"
  • wait perhaps 10-11 minutes to let a couple report sets run
  • run "sudo journalctl -u weewx  | tail -n 250 > /tmp/logs.txt"
3. Then post a followup message and 'attach' both /tmp/debug.txt and /tmp/logs.txt so we can take a look

The command in (2) above just sends the last 250 lines in the perhaps verbose logs to that file. That should be enough for us to see the weewx startup and two report cycles.  A quick test here logged under 200 lines of output on a new system.   We need to see that weewx startup lines that look like the following and everything after that....

Feb 03 08:13:50 weewx-pip systemd[1]: Started weewx.service - WeeWX.
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Initializing weewxd version 5.2.0
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Command line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Using Python: 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Located at:   /usr/bin/python3
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Platform:     Linux-6.12.38+deb13-amd64-x86_64-with-glibc2.41
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Locale:       'en_US.UTF-8'
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Entry path:   /usr/share/weewx/weewxd.py
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: WEEWX_ROOT:   /etc/weewx
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Config file:  /etc/weewx/weewx.conf
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: User module:  /etc/weewx/bin/user
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Debug:        1
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: User:         weewx
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Group:        weewx
Feb 03 08:13:50 weewx-pip weewxd[2964]: INFO __main__: Groups:       weewx
Feb 03 08:13:50 weewx-pip weewxd[2964]: DEBUG __main__: loop_on_init: False
Feb 03 08:13:50 weewx-pip weewxd[2964]: DEBUG __main__: Initializing engine


Definitely 'ATTACH' the two files please.  Making sure the filenames end in .txt makes it easier on folks to open the attachments.  Thanks.

Jan Volschenk

unread,
12:45 PM (5 hours ago) 12:45 PM
to weewx...@googlegroups.com
Hie Vince, appreciate your reply, just give me a bit of time - will get back!

--
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 weewx-user+...@googlegroups.com.


--
Kind regards

Jan Volschenk, 
Amateur Radio Call-sign: ZS6VOL
Reply all
Reply to author
Forward
0 new messages