WSPR Autorun spots - most not uploading?

Nate_RNate_R
edited July 21 in WSPR, wsprdaemon, kiwirecorder

My WSPR Autorun spots (IWBP rotation) seem to have stopped uploading about 90% of them. Kiwi Admin says ~300 decoded, but only 27 are posted on WSPRnet since last restart of the Kiwi. Still running version 1.690 on a KiwiSDR2.

Now, I'll be clear, I'm running a temporary weird setup in how the Kiwi is connected to the internet, so if that turns out to be the culprit, no problem, I can revert back when I get new parts. But it's odd that it's not all or nothing...

  I'm running the Kiwi temporarily ethernet connected to a wifi repeater (Archer C54), and not to a router in client mode as a Wifi bridge. So port forwarding probably isn't working right...as I can forward from my router to the wifi repeater, but not to the kiwi IP directly. But the proxy seems to work, I can access my Kiwi remotely, etc. My Kiwi had gone offline a couple weeks ago, turns out it was my Wifi bridge dying (TP Link WR802N only lasted a couple months!), so I switched to this one since I had it on hand (only temporary.) BUT, the thing is, it uploaded spots just fine all day yesterday, and overnight, stopped. I messed around with settings and such today, but no dice. But it gets SOME spots through... the 27 out of 300+ decodes.

Looking at the log, it decodes the spots, and then I see upload attempts. But should I see a response from WSPRnet, or is the blank normal?

Example below, I show several decodes from 2 cycles, and then tries to start uploading them. Not sure about the child_task warning...

Sun Jul 21 22:16:00 06:39:27.899 0... 0      IWBP DECODE: 2214   3  0.1 21.096035  0  NJ6E   CM88  2959   23 (200 mW)
Sun Jul 21 22:16:06 06:39:33.947 0... 0      IWBP DECODE: 2214  -5  0.1 21.096124  0  WB6NGC DM04  2869   37 (5.0 W)
Sun Jul 21 22:16:07 06:39:34.671 0... 0      IWBP DECODE: 2214  -7 -0.0 21.096156  0  W6VYC  CM87  3009   23 (200 mW)
Sun Jul 21 22:16:08 06:39:36.243 0... 0      IWBP DECODE: 2214 -12  0.1 21.096111  0  AF6RF  DM03  2932   23 (200 mW)
Sun Jul 21 22:16:09 06:39:36.962 0... 0      IWBP DECODE: 2214 -17 -0.1 21.096062  0  W3AVV  DM26  2444   23 (200 mW)
Sun Jul 21 22:16:10 06:39:38.138 0... 0      WSPR DECODE:  UTC  dB   dT      Freq dF  Call   Grid    km  dBm
Sun Jul 21 22:16:10 06:39:38.138 0... 0      IWBP DECODE: 2214 -17  0.5 21.096050  0  WW0WWV DN70  1468   30 (1.0 W)
Sun Jul 21 22:16:11 06:39:39.131 0... 0      IWBP DECODE: 2214 -21 -0.2 21.096171  0  CS5TRG IN50  6207   23 (200 mW)
Sun Jul 21 22:16:12 06:39:39.853 0... 0      IWBP DECODE: 2214 -24  0.2 21.095996  0  CE7FMP FE34 10194   23 (200 mW)
Sun Jul 21 22:16:18 06:39:46.131 0... 0      IWBP DECODE: 2214 -24  0.3 21.096187 -2  LU4AA  GF05  9334   23 (200 mW)
Sun Jul 21 22:17:13 06:40:41.336 0... 0      IWBP DECODE: 2214 -25 -0.2 21.096101  0  KD7UHR EM58   748   40 (10 W)
Sun Jul 21 22:17:59 06:41:26.551 0...        child_task WARNING: child returned without WIFEXITED status=0x0000008b WIFEXITED=0 WEXITSTATUS=0
Sun Jul 21 22:17:59 06:41:26.551 0... 0      IWBP UPLOAD: curl -sL 'http://wsprnet.org/post?function=wspr&rcall=N8BTR&rgrid=EN55we&rqrg=21.096100&date=240721&time=2214&sig=3&dt=0.1&drift=0&tqrg=21.096035&tcall=NJ6E&tgrid=CM88&dbm=23&version=1.4A+Kiwi'
Sun Jul 21 22:17:59 06:41:26.551 0... 0      IWBP UPLOAD: wsprnet.org said: ""
Sun Jul 21 22:18:45 06:42:12.603 0...        child_task WARNING: child returned without WIFEXITED status=0x0000008b WIFEXITED=0 WEXITSTATUS=0
Sun Jul 21 22:18:45 06:42:12.603 0... 0      IWBP UPLOAD: curl -sL 'http://wsprnet.org/post?function=wspr&rcall=N8BTR&rgrid=EN55we&rqrg=21.096100&date=240721&time=2214&sig=-5&dt=0.1&drift=0&tqrg=21.096124&tcall=WB6NGC&tgrid=DM04&dbm=37&version=1.4A+Kiwi'
Sun Jul 21 22:18:45 06:42:12.603 0... 0      IWBP UPLOAD: wsprnet.org said: ""
Sun Jul 21 22:19:31 06:42:58.922 0...        child_task WARNING: child returned without WIFEXITED status=0x0000008b WIFEXITED=0 WEXITSTATUS=0
Sun Jul 21 22:19:31 06:42:58.922 0... 0      IWBP UPLOAD: curl -sL 'http://wsprnet.org/post?function=wspr&rcall=N8BTR&rgrid=EN55we&rqrg=21.096100&date=240721&time=2214&sig=-7&dt=-0.0&drift=0&tqrg=21.096156&tcall=W6VYC&tgrid=CM87&dbm=23&version=1.4A+Kiwi'
Sun Jul 21 22:19:31 06:42:58.922 0... 0      IWBP UPLOAD: wsprnet.org said: ""


Any thoughts here? Do I need to uncheck: "Non-Kiwi connections (kiwirecorder, TDoA) can preempt autorun processes"? Or is this looking like a WSPRnet server issue? Or some intermittent problem with my Kiwi to internet setup?

Thanks!

-Nate

N8BTR

Comments

  • Nate_RNate_R

    Further update....I think I only get the "child returned" warning on spots that don't upload properly... the ones I've caught that do upload properly don't seem to have this warning in the log.

    -Nate

    N8BTR

  • jksjks

    Uploads look to be normal from here.

    You shouldn't be getting that "child task" error though. Not sure what that's about. Try rebooting the Beagle and see if it goes away (admin control tab, Beagle reboot button)

  • jksjks
    edited July 22

    Yes, wsprnet.org stopped sending upload confirmation info some time ago. Really unfortunate as it helped with debugging.

  • HB9TMCHB9TMC
    edited July 22

    Still running version 1.690


    That appears to have been fixed in 1.694 though:

       WSPR extension spots will now upload again to wsprnet.org (thanks Nate, et al)
  • Nate_RNate_R

    @HB9TMC , that was in reference to the web-based WSPR decoder versus the autorun version. I'm having issues with the autorun version that runs continuously in the background, basically.


    -Nate

    N8BTR

  • Nate_RNate_R

    @jks Thanks! Rebooted just the Beagle last night, but still got the "child" errors. Unchecked the "Non-Kiwi connections (kiwirecorder, TDoA) can preempt autorun processes" box and that didn't seem to make a difference....although no idea if it would.

    It was the same thing overnight, most spots did not upload, but suddenly this morning it seems to be uploading most again. So, not sure what's up.... I don't understand why it would work sometimes and not others, but the only thing that changed was my connection method.

    Well, given that everything outside of that appears to be OK/normal, I'll sit tight for now. I should be able to get a new TP-Link WR802N going in a couple weeks, and once that's working, I'll upgrade to 1.694 (or 5, or whatever is newest at that time), and I'll whine then only if the errors persist. If that fixes it, I'll report back here too, as I hate finding old threads with no post of the resolution in forums! 😄


    -Nate

    N8BTR

Sign In or Register to comment.