weewx[2692]: interceptor: MainThread: empty queue??

[Chris Maness]

I am new to weewx.  I am trying to use a ecowitt GW1000 bridge to set up CWOP reporting.  I have my station reporting to WU with weewx running on raspberry pi as a hotspot.  The GW1000 is connecting through my Pi.  I am trying to use wu-intercept, but no joy.  "I get: weewx[2692]: interceptor: MainThread: empty queue" in the syslog.  The relevant configuration is:

System info

  Platform:       Linux-4.14.79-v7+-armv7l-with-debian-9.8

  Python Version: 2.7.13

Load Information

  1 minute load average:  0.04

  5 minute load average:  0.07

  15 minute load average: 0.02

General Weewx info

  Weewx version 3.9.1 detected.

Station info

  Station type: Interceptor

  Driver:       user.interceptor

Driver info

[Interceptor]

    # This section is for the network traffic interceptor driver.

    

    # The driver to use:

    driver = user.interceptor

    

    # Specify the hardware device to capture.  Options include:

    #   acurite-bridge - acurite internet bridge, smarthub, or access

    #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902

    #   lw30x - oregon scientific LW301/LW302

    #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge

    #   wu-client - any hardware that uses the weather underground protocol

    device_type = wu-client

Currently installed extensions

Extension Name    Version   Description

interceptor       0.45      Capture weather data from HTTP requests

Archive info

  Database name:        weewx.sdb

  Table name:           archive

  Version               2.0

  Unit system:          1 (US)

  First good timestamp: 2019-02-17 21:45:00 PST (1550468700)

  Last good timestamp:  2019-02-18 10:35:00 PST (1550514900)

  Number of records:    3

  weewx (weewx.conf) is set to use an archive interval of 300 seconds.

  The station hardware was not interrogated in determining archive interval.

Databases configured in weewx.conf

  Database name:        weewx.sdb

  Database driver:      weedb.sqlite

  Database name:        weewx

  Database driver:      weedb.mysql

  Database host:        localhost

Any suggestions?

Thanks,

Chris Maness

[mwall]

On Monday, February 18, 2019 at 5:20:12 PM UTC-5, Chris Maness wrote:

I am new to weewx.  I am trying to use a ecowitt GW1000 bridge to set up CWOP reporting.  I have my station reporting to WU with weewx running on raspberry pi as a hotspot.  The GW1000 is connecting through my Pi.  I am trying to use wu-intercept, but no joy.  "I get: weewx[2692]: interceptor: MainThread: empty queue" in the syslog.

 

Any suggestions?

your configuration says that you are using the interceptor in 'listen' mode (that is the default configuration, and you have not specified anything else).  so you must make the GW1000 direct its traffic to the port on which the interceptor is listening (by default that is port 80).  the standard way of doing this is to hijack the dns on the subnet to which the GW1000 is connected so that when it does dns queries for the wu server, it gets the ip address of the pi.  if dhcp is being done by the pi, then add the dns entry to the dhcp configuration on the pi.  otherwise, add it to the dns server or dhcp server on your local network.

alternatively, instead of listening, you could configure the interceptor to sniff.  in that case the GW1000 traffic will go to wu, but the pi will intercept it as it goes from the wifi interface to the wired interface.

m

[Chris Maness]

I could not get it to work with the GW1000 driver. I started using
wu-client again in sniff mode with wlan0 and the IP of the GW, and now
I see data. Now I need to get CWOP going. Also lighthttp is
configured to port 8080 for this thing to work on port 80. I set up
the hotspot using RaspAP, and I tried uninstalling and keeping the
hotspot configuration , but it did not work. Can lighthttpd be
configured to serve up only on the eth0 side (to see my weather data)?
That way it doesn't interfere with RaspAP. Not sure that is
possible.

Thanks,
Chris Maness

> --
> 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.
> For more options, visit https://groups.google.com/d/optout.

[mwall]

On Monday, February 18, 2019 at 7:24:19 PM UTC-5, Chris Maness wrote:

I could not get it to work with the GW1000 driver.  I started using
wu-client again in sniff mode with wlan0 and the IP of the GW, and now
I see data.  Now I need to get CWOP going.  Also lighthttp is
configured to port 8080 for this thing to work on port 80.  I set up
the hotspot using RaspAP, and I tried uninstalling and keeping the
hotspot configuration , but it did not work.  Can lighthttpd be
configured to serve up only on the eth0 side (to see my weather data)?
 That way it doesn't interfere with RaspAP.  Not sure that is
possible.

the gw1000 mode in the interceptor driver is for the lacrosse gw1000, not the ecowitt gw1000.  the lacrosse gw1000 has a very complicated protocol that is not like any other device.

so you are correct to use the w-client mode with the ecowitt gw1000

as for ports, you could have the rpi listen on port 80 on the wifi interface for communication from the gw1000, then make the apache/nginx/lighttpd on the rpi listen on port 80 on the wired interface for web traffic.

or just make apache/nginx/lighttpd listen on any port other than 80 on both interfaces.

lots of options, i know, so it can be confusing.

maybe someone could create a wiki page with some diagrams that illustrate some of the options described in the interceptor readme?

[Chris Maness]

Yes, some clearer documentation would be super helpful.  I had a hard time finding information to help me troubleshoot the interceptor.  The docs are ok for weewx, but not the interceptor .

Thanks,

Chris Maness

[ch...@chrismaness.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Ok, I have Wunderground working, and the WeeWx status page working
regularly. However, I am not getting any updates with CWOP. This I
remember was easy to set up once the WeeWx status page was running it
was passing info to CWOP. My APRS callsign is KQ6UP. I have the
status set to true with my username and password just like my old
setup. Is there a command I can use that will sniff for packets going
to CWOP to try to diagnose what is going on?

TIA,
Chris KQ6UP
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmzHlvOdIh0ey/XTCFjZDRZ5c+EwFAl6ktU0ACgkQFjZDRZ5c
+EwjrQf8D+RZ1jFx4hFVNUUN1dbiDQMzocjrYewXWVJMJoS9y6buk61Zu+2EW7mL
T8X/pB6iRLfJ/P7tyVx1V/OAf3ZpC/xUz9xgNfhu465EJorER5wQnAoPq6qBusPt
JgOv38aln0kjEbcWF7Mj7gtfwHcNaSPOH2zkiTHyFTP/eKMFTiU9pwZtxPZY6vZy
7UngNmDn6x4G2tp9Vmp8gVTe1VPCikmX/JjOypYuWL8nNMt5nWkhfTdYqBoYnxKZ
JQ9frevkYKf8TWWSdi0ge1ko3A3FCWsFY1K4/FtRjmH+wrMD6qfaXWfy9jsjBCHU
lXpv6UYm6THwYllhr8I11+6ior3q0Q==
=2tiV
-----END PGP SIGNATURE-----

[Dave Webb KB1PVH]

Chris,

Looks like your last weather packet was about an hour ago, not sure when you upgraded. 

https://aprs.fi/weather/a/KQ6UP

Dave-KB1PVH


Sent from my Galaxy S9

--
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 on the web visit https://groups.google.com/d/msgid/weewx-user/32768af7-4ff8-156c-b7cf-fb5fec27ad8e%40gmail.com.

[Dave Webb KB1PVH]

Here's a list with timestamps of your packets.

http://www.findu.com/cgi-bin/wx.cgi?call=kq6up

Dave-KB1PVH


Sent from my Galaxy S9

[ch...@chrismaness.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 4/25/20 3:17 PM, Dave Webb KB1PVH wrote:
> Here's a list with timestamps of your packets.
>
> http://www.findu.com/cgi-bin/wx.cgi?call=kq6up
>
> Dave-KB1PVH

Looks like it just updated again. That is weird.

Chris KQ6UP
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmzHlvOdIh0ey/XTCFjZDRZ5c+EwFAl6kucMACgkQFjZDRZ5c
+EwP/gf+JJVhTxt/DgwRh5AY1CycbOaNj4mumD26ldVD6z58fkP5mk5IhVoFRQbB
lkegPuw9iCpDrO0UZQ3yp17XssiEc1Kn8QePmDhhD82sVtT9O3NhJtpaNBRnGD9v
RMIcmAkow4KKB+8dojYW5X82uTFDLPkIqAngdRZSyr7Vs7CeOe39z7ytGR8bf0Wo
Al9WMcMbMUch4DQjaUNbgSNDo4a/ckNJwteELL0n1OkJnX74Ti+Eirbsh4rMmDb2
ne0XZzGJALA4R+5xb9RYR7MGWQ6WDPXtBWHZq6Jn9y+xD8FWcVl91eAjsWnWcWzJ
E/LvAho0T1pXldbR7AMM8QuYCM7e3A==
=4QpT
-----END PGP SIGNATURE-----

[gjr80]

Yep, the usual, set debug=1, restart Weewx and check the log.

Gary

[ch...@chrismaness.com]

On 4/25/20 3:34 PM, gjr80 wrote:
> Yep, the usual, set debug=1, restart Weewx and check the log.
>
> Gary
>

Ok did it. Here is the syslog output:

https://pastebin.com/m9PL67dt

[Tom Keffer]

You log runs from 15:37:31 to 15:43:10, with a single CWOP post at 15:42:20. Looks pretty normal to me.

If you want even more debug information, you can set debug=2 to have the log include the TNC packets that are sent to the CWOP server.

--
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 on the web visit https://groups.google.com/d/msgid/weewx-user/c345ed1d-4fb6-4dca-4658-6099548b2702%40gmail.com.

[ch...@chrismaness.com]

On 4/25/20 4:34 PM, Tom Keffer wrote:
> You log runs from 15:37:31 to 15:43:10, with a single CWOP post at
> 15:42:20. Looks pretty normal to me.
>
> If you want even more debug information, you can set debug=2 to have the
> log include the TNC packets that are sent to the CWOP server.
>

I will do that. It is hit/miss right now. Sometimes going 20min
without updating CWOP.

Thanks,
Chris KQ6UP

[ch...@chrismaness.com]

On 4/25/20 4:34 PM, Tom Keffer wrote:

> You log runs from 15:37:31 to 15:43:10, with a single CWOP post at
> 15:42:20. Looks pretty normal to me.
>
> If you want even more debug information, you can set debug=2 to have the
> log include the TNC packets that are sent to the CWOP server.
>
> On Sat, Apr 25, 2020 at 3:47 PM <ch...@chrismaness.com

> <mailto:ch...@chrismaness.com>> wrote:
>

Tom, it looks my connections to the CWOP server may be timing out. Can
you have a look?

Here is my debug=2 log:

https://pastebin.com/TkQweD3a

Regards,
Chris KQ6UP

[Dave Webb KB1PVH]

Chris,

 Out of curiosity what's your CWOP section in weewx.conf look like? 

Dave-KB1PVH


Sent from my Galaxy S9

--
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 on the web visit https://groups.google.com/d/msgid/weewx-user/31c114bf-6a8a-ddba-705d-47945f0f9a5f%40gmail.com.

[Christopher Maness]

On 4/25/20 5:41 PM, Dave Webb KB1PVH wrote:
> Chris,
>
>  Out of curiosity what's your CWOP section in weewx.conf look like? 
>
> Dave-KB1PVH
>

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = true
station = kq6up

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
passcode = noneyabeeswax

[Tom Keffer]

Normally, CWOP returns a confirmation after posting the TNC packet, which looks something like: "# logresp KQ6UP unverified, server CWOP-5"

However, according to the CWOP documentation, there is no formal acknowledgement of a successful post, hence the WeeWX code does not actually check for any confirmation.

Looking through your raw packet stream, you are missing a lot of records. Has your weather station been up the whole time?

-tk

[Christopher Maness]

On 4/26/20 5:05 AM, Tom Keffer wrote:
> Normally, CWOP returns a confirmation after posting the TNC packet,
> which looks something like: "# logresp KQ6UP unverified, server CWOP-5"
>
> However, according to the CWOP documentation

> <http://www.wxqa.com/faq.html>, there is no formal acknowledgement of a

> successful post, hence the WeeWX code does not actually check for any
> confirmation.
>
> Looking through your raw packet stream

> <http://www.findu.com/cgi-bin/raw.cgi?call=KQ6UP>, you are missing a lot

> of records. Has your weather station been up the whole time?
>
> -tk
>

It was down for about a week without my knowledge, and since I am home
bored with COVID-19, I have been tinkering with upgrades. That has
taken it offline sporadically. Since I changed some lines in the CWOP
entry for the .conf file, it has not reported. I am going to change it
back and see if at least it works sporadically again.

Regards,
Chris KQ6UP

[ch...@chrismaness.com]

On 4/25/20 6:02 PM, Dave Webb KB1PVH wrote:
> Hey Chris,
>
>  It's actually suggested that us radio geeks use the rotate servers. Try
> something like this

>
> [[CWOP]]
>         # This section is for configuring posts to CWOP.
>
>         # If you wish to do this, set the option 'enable' to true,
>         # and specify the station ID (e.g., CW1234).
>         enable = true

>         station = KB1PVH-13
>         post_interval = 600
>         log_success = True
>         log_failure = True
>         server_list = rotate.aprs.net:14580
> <http://rotate.aprs.net:14580/>, rotate.aprs2.net:14580
> <http://rotate.aprs2.net:14580/>, cwop.aprs.net:14580
> <http://cwop.aprs.net:14580/>, cwop.aprs.net:23 <http://cwop.aprs.net:23/>
>         passcode = your_passcode_here
>
> Dave-KB1PVH

Adding those lines broke it. I did put my correct password. I have
since changed it back to my previous configuration, and it has started
to work again.

Chris KQ6UP

[ch...@chrismaness.com]

On 4/26/20 10:17 AM, Dave Webb KB1PVH wrote:
> Chris,
>

> Have you tried leaving all the existing info and just change the APRS
> server to rotate.aprs.net:14580/ <http://rotate.aprs.net:14580/>
>
> Dave-KB1PVH
>

I will give that a shot.

Chris KQ6UP

[ch...@chrismaness.com]

On 4/26/20 10:56 AM, Dave Webb KB1PVH wrote:
> Using the rotate servers spreads the load and that's why they
> recommend that hams using callsign and passcode use that as opposed to
> the standard server that is getting hammered by all the other weather
> stations. 
>
> Dave-KB1PVH


It does NOT like that line.  It is treating every character as a new
server.  I am using nano and cutting and pasting from my mac if that
makes any difference.  The text looks 100% normal in the ascii file.


Chris KQ6UP


Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@261945z3401.26N/11718.84W_253/006g015t094r000p000P000b10156h24L835.weewx-3.9.2-Interceptor#015
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'c'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'w'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'o'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'p'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: '.'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'a'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'p'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'r'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 's'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: '.'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'n'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 'e'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Bad server
address: 't'; ignored
Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Failed to publish
record 2020-04-26 12:45:00 PDT (1587930300): Tried 13 servers 3 times each

[gjr80]

The problem when using a single entry in the server_list for CWOP uploads is a known issue https://github.com/weewx/weewx/issues/520 refers. It will be fixed in 4.0, in the interim a work around exists, simply place a comma (,) immediately after the last character of the server_list entry.

Gary

[ch...@chrismaness.com]

On 4/26/20 1:05 PM, gjr80 wrote:
> The problem when using a single entry in the server_list for CWOP uploads is a known issue https://github.com/weewx/weewx/issues/520 refers. It will be fixed in 4.0, in the interim a work around exists, simply place a comma (,) immediately after the last character of the server_list entry.
>
> Gary
>

I will try that.  Here is another interesting line:


Apr 26 13:05:34 raspberrypi weewx[11862]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:05:00 PDT (1587931500)


Because of my error I have not had a successful post in a couple hours. 
It saying I have not waited long enough.


Hmmmm

Chris KQ6UP

[Dave Webb KB1PVH]

Chris,

 I find it odd that if you make your CWOP section like mine that weewx falls on it's face unless something is funky when you copy and paste. 

[[CWOP]]
        # This section is for configuring posts to CWOP.

        # If you wish to do this, set the option 'enable' to true,
        # and specify the station ID (e.g., CW1234).
        enable = true
        station = KB1PVH-13
        post_interval = 600
        log_success = True
        log_failure = True

        server_list = rotate.aprs.net:14580, rotate.aprs2.net:14580, cwop.aprs.net:14580, cwop.aprs.net:23
        passcode = xxxxxx

Dave-KB1PVH

--
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 on the web visit https://groups.google.com/d/msgid/weewx-user/c964c99d-f6e4-2ce1-b237-d3a289b7c917%40gmail.com.

[gjr80]

I understand posts to CWOP are to be made no more frequently than every 10 minutes so WeeWX checks before making a post to see if 10 minutes have elapsed since it last made a post. That’s fine, but when coupled with the lack of a documented formal acknowledgment of a post (and hence WeeWX assuming all posts are successful) you can end up in the situation where posts are skipped even though there have been no previous successful posts.

Gary

[ch...@chrismaness.com]

According to Gary, I needed a comma after the single entry.  I did post that line below exactly as you had it but with my personals.  It did not work.  Just having the basic lines that it comes with seems to work, but hit/miss fashion.

Chris KQ6UP

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAEMY9Fdi71osZsGbaFYrz_r3emvPWt7oXef3Y88G7S_Epxs0Pw%40mail.gmail.com.

[ch...@chrismaness.com]

It looks like its posting, but not showing up on the network:

Apr 26 13:25:21 raspberrypi weewx[12252]: restx: CWOP: packet: KQ6UP>APRS,TCPIP*:@262025z3401.26N/11718.84W_352/006g011t096r000p000P000b10153h21L796.weewx-3.9.2-Interceptor#015
Apr 26 13:25:21 raspberrypi weewx[12252]: restx: CWOP: Connected to server rotate.aprs.net:14580
Apr 26 13:25:22 raspberrypi weewx[12252]: restx: CWOP: Published record 2020-04-26 13:25:00 PDT (1587932700)

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAEMY9Fdi71osZsGbaFYrz_r3emvPWt7oXef3Y88G7S_Epxs0Pw%40mail.gmail.com.

[ch...@chrismaness.com]

On 4/26/20 1:16 PM, Dave Webb KB1PVH wrote:

Chris,

 I find it odd that if you make your CWOP section like mine that weewx falls on it's face unless something is funky when you copy and paste. 

[[CWOP]]
        # This section is for configuring posts to CWOP.

        # If you wish to do this, set the option 'enable' to true,
        # and specify the station ID (e.g., CW1234).
        enable = true
        station = KB1PVH-13
        post_interval = 600
        log_success = True
        log_failure = True
        server_list = rotate.aprs.net:14580, rotate.aprs2.net:14580, cwop.aprs.net:14580, cwop.aprs.net:23
        passcode = xxxxxx

Dave-KB1PVH

I am starting to suspect I am having issues out of my network with port 14580.  I tried cwop.aprs.net:23 for a single server, and it seems to be working.

When I tried rotate.aprs.net:14580 all by itself I got a:

Apr 26 00:25:30 raspberrypi weewx[1834]: restx: CWOP: Attempt 1 to rotate.aprs.net:14580. Connection error: [Errno 111] Connection refused

Thanks,

Chris KQ6UP

[ch...@chrismaness.com]

grepped all the whole syslog for relevant lines.  It looks like the
packets are getting posted, but not consistently showing up on the
network.  That is really weird.  Here they are:

Apr 26 12:45:27 raspberrypi weewx[11493]: restx: CWOP: Failed to publish
record 2020-04-26 12:45:00 PDT (1587930300): Tried 13 servers 3 times each

Apr 26 12:50:16 raspberrypi weewx[11493]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 12:50:00 PDT (1587930600)
Apr 26 12:54:54 raspberrypi weewx[11493]: restx: Shut down CWOP thread.
Apr 26 12:55:00 raspberrypi weewx[11862]: engine: Loading service
weewx.restx.StdCWOP
Apr 26 12:55:00 raspberrypi weewx[11862]: restx: CWOP: Data for station
KQ6UP will be posted
Apr 26 12:55:00 raspberrypi weewx[11862]: engine: Finished loading
service weewx.restx.StdCWOP
Apr 26 13:00:28 raspberrypi weewx[11862]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262000z3401.26N/11718.84W_002/002g010t095r000p000P000b10154h22L861.weewx-3.9.2-Interceptor#015
Apr 26 13:00:29 raspberrypi weewx[11862]: restx: CWOP: Connected to
server cwop.aprs.net:14580
Apr 26 13:00:49 raspberrypi weewx[11862]: restx: CWOP: Exception <class
'socket.timeout'> (timed out) when looking for response to packet packet
Apr 26 13:00:49 raspberrypi weewx[11862]: restx: CWOP: Published record
2020-04-26 13:00:00 PDT (1587931200)

Apr 26 13:05:34 raspberrypi weewx[11862]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:05:00 PDT (1587931500)

Apr 26 13:10:40 raspberrypi weewx[11862]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262010z3401.26N/11718.84W_271/002g013t096r000p000P000b10154h22L752.weewx-3.9.2-Interceptor#015
Apr 26 13:10:40 raspberrypi weewx[11862]: restx: CWOP: Connected to
server cwop.aprs.net:14580
Apr 26 13:11:01 raspberrypi weewx[11862]: restx: CWOP: Exception <class
'socket.timeout'> (timed out) when looking for response to packet packet
Apr 26 13:11:01 raspberrypi weewx[11862]: restx: CWOP: Published record
2020-04-26 13:10:00 PDT (1587931800)
Apr 26 13:15:29 raspberrypi weewx[11862]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:15:00 PDT (1587932100)
Apr 26 13:20:16 raspberrypi weewx[11862]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262020z3401.26N/11718.84W_310/006g013t096r000p000P000b10152h21L868.weewx-3.9.2-Interceptor#015
Apr 26 13:20:17 raspberrypi weewx[11862]: restx: CWOP: Connected to
server cwop.aprs.net:14580
Apr 26 13:20:37 raspberrypi weewx[11862]: restx: CWOP: Exception <class
'socket.timeout'> (timed out) when looking for response to packet packet
Apr 26 13:20:37 raspberrypi weewx[11862]: restx: CWOP: Published record
2020-04-26 13:20:00 PDT (1587932400)
Apr 26 13:22:08 raspberrypi weewx[11862]: restx: Shut down CWOP thread.
Apr 26 13:22:14 raspberrypi weewx[12252]: engine: Loading service
weewx.restx.StdCWOP
Apr 26 13:22:14 raspberrypi weewx[12252]: restx: CWOP: Data for station
KQ6UP will be posted
Apr 26 13:22:14 raspberrypi weewx[12252]: engine: Finished loading
service weewx.restx.StdCWOP

Apr 26 13:25:21 raspberrypi weewx[12252]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262025z3401.26N/11718.84W_352/006g011t096r000p000P000b10153h21L796.weewx-3.9.2-Interceptor#015
Apr 26 13:25:21 raspberrypi weewx[12252]: restx: CWOP: Connected to
server rotate.aprs.net:14580
Apr 26 13:25:22 raspberrypi weewx[12252]: restx: CWOP: Published record
2020-04-26 13:25:00 PDT (1587932700)

Apr 26 13:30:26 raspberrypi weewx[12252]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:30:00 PDT (1587933000)
Apr 26 13:35:19 raspberrypi weewx[12252]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262035z3401.26N/11718.84W_261/006g015t097r000p000P000b10152h20L850.weewx-3.9.2-Interceptor#015
Apr 26 13:35:20 raspberrypi weewx[12252]: restx: CWOP: Connected to
server rotate.aprs.net:14580
Apr 26 13:35:20 raspberrypi weewx[12252]: restx: CWOP: Published record
2020-04-26 13:35:00 PDT (1587933300)
Apr 26 13:40:25 raspberrypi weewx[12252]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:40:00 PDT (1587933600)
Apr 26 13:45:31 raspberrypi weewx[12252]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262045z3401.26N/11718.84W_297/006g017t097r000p000P000b10151h20L805.weewx-3.9.2-Interceptor#015
Apr 26 13:45:32 raspberrypi weewx[12252]: restx: CWOP: Connected to
server rotate.aprs.net:14580
Apr 26 13:45:32 raspberrypi weewx[12252]: restx: CWOP: Published record
2020-04-26 13:45:00 PDT (1587933900)
Apr 26 13:50:20 raspberrypi weewx[12252]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 13:50:00 PDT (1587934200)
Apr 26 13:55:26 raspberrypi weewx[12252]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262055z3401.26N/11718.84W_291/001g011t097r000p000P000b10151h21L822.weewx-3.9.2-Interceptor#015
Apr 26 13:55:26 raspberrypi weewx[12252]: restx: CWOP: Connected to
server rotate.aprs.net:14580
Apr 26 13:55:27 raspberrypi weewx[12252]: restx: CWOP: Published record
2020-04-26 13:55:00 PDT (1587934500)
Apr 26 13:58:02 raspberrypi weewx[12252]: restx: Shut down CWOP thread.
Apr 26 13:58:08 raspberrypi weewx[12666]: engine: Loading service
weewx.restx.StdCWOP
Apr 26 13:58:08 raspberrypi weewx[12666]: restx: CWOP: Data for station
KQ6UP will be posted
Apr 26 13:58:08 raspberrypi weewx[12666]: engine: Finished loading
service weewx.restx.StdCWOP
Apr 26 14:00:15 raspberrypi weewx[12666]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262100z3401.26N/11718.84W_242/005g011t097r000p000P000b10151h23L607.weewx-3.9.2-Interceptor#015
Apr 26 14:00:16 raspberrypi weewx[12666]: restx: CWOP: Connected to
server cwop.aprs.net:23
Apr 26 14:00:36 raspberrypi weewx[12666]: restx: CWOP: Exception <class
'socket.timeout'> (timed out) when looking for response to packet packet
Apr 26 14:00:36 raspberrypi weewx[12666]: restx: CWOP: Published record
2020-04-26 14:00:00 PDT (1587934800)
Apr 26 14:05:21 raspberrypi weewx[12666]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 14:05:00 PDT (1587935100)
Apr 26 14:10:27 raspberrypi weewx[12666]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262110z3401.26N/11718.84W_241/007g017t098r000p000P000b10150h22L774.weewx-3.9.2-Interceptor#015
Apr 26 14:10:28 raspberrypi weewx[12666]: restx: CWOP: Connected to
server cwop.aprs.net:23
Apr 26 14:10:28 raspberrypi weewx[12666]: restx: CWOP: Published record
2020-04-26 14:10:00 PDT (1587935400)
Apr 26 14:15:33 raspberrypi weewx[12666]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 14:15:00 PDT (1587935700)
Apr 26 14:20:15 raspberrypi weewx[12666]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262120z3401.26N/11718.84W_329/008g013t098r000p000P000b10149h22L746.weewx-3.9.2-Interceptor#015
Apr 26 14:20:16 raspberrypi weewx[12666]: restx: CWOP: Connected to
server cwop.aprs.net:23
Apr 26 14:20:16 raspberrypi weewx[12666]: restx: CWOP: Published record
2020-04-26 14:20:00 PDT (1587936000)
Apr 26 14:25:20 raspberrypi weewx[12666]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 14:25:00 PDT (1587936300)
Apr 26 14:30:17 raspberrypi weewx[12666]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262130z3401.26N/11718.84W_277/005g019t098r000p000P000b10148h23L750.weewx-3.9.2-Interceptor#015
Apr 26 14:30:38 raspberrypi weewx[12666]: restx: CWOP: Attempt 1 to
cwop.aprs.net:23. Connection error: timed out
Apr 26 14:30:38 raspberrypi weewx[12666]: restx: CWOP: Connected to
server cwop.aprs.net:23
Apr 26 14:30:58 raspberrypi weewx[12666]: restx: CWOP: Exception <class
'socket.timeout'> (timed out) when looking for response to packet packet
Apr 26 14:30:58 raspberrypi weewx[12666]: restx: CWOP: Published record
2020-04-26 14:30:00 PDT (1587936600)
Apr 26 14:35:23 raspberrypi weewx[12666]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 14:35:00 PDT (1587936900)
Apr 26 14:40:29 raspberrypi weewx[12666]: restx: CWOP: packet:
KQ6UP>APRS,TCPIP*:@262140z3401.26N/11718.84W_254/007g028t098r000p000P000b10149h23L732.weewx-3.9.2-Interceptor#015
Apr 26 14:40:30 raspberrypi weewx[12666]: restx: CWOP: Connected to
server cwop.aprs.net:23
Apr 26 14:40:50 raspberrypi weewx[12666]: restx: CWOP: Exception <class
'socket.timeout'> (timed out) when looking for response to packet packet
Apr 26 14:40:50 raspberrypi weewx[12666]: restx: CWOP: Published record
2020-04-26 14:40:00 PDT (1587937200)
Apr 26 14:45:18 raspberrypi weewx[12666]: restx: CWOP: wait interval
(300 < 600) has not passed for record 2020-04-26 14:45:00 PDT (1587937500)


Chris KQ6UP