Config problem? SND Bad params?

[perezoso]

Hi Folks -

My name is Edward (WA3098SWL).  I'm trying to be the newest wsprdaemon user despite the handicap of being a history major.  

I've installed wsprdaemon on a rpi4 and gotten it close enough to working that when the daemon starts I can see 8 wsprdaemon processes connected to the Kiwi on the right bands.

When I type "./wspdaemon.sh -s" the eight processes are there on the rpi and it says the 3 daemon - spots uploading, .org uploading, and watchdog are running.

It would seem like everything is fine, but I'm not getting any spots reported at wsprnet.org. No errors in the wsprdaemon log file. I am guessing that there is something wrong with my config file.  [MAYBE NOT - see below]

My setup is simple but being a history major, I found the config file a little daunting. I have one Kiwi connected at the local IP 192.168.1.82:8073.  I want it to run 24 hours a day on 80m through 17m.  Are there errors in my config?


declare RECEIVER_LIST=(
        "KIWI_0                  192.168.1.82:8073     WA3098SWL         FM28jh    NULL"
)

declare WSPR_SCHEDULE_simple=(
    "00:00                       KIWI_0,80 KIWI_0,80eu KIWI_0,60 KIWI_0,60eu KIWI_0,40 KIWI_0,30 KIWI_0,20 KIWI_0,17"
)

declare WSPR_SCHEDULE=( "${WSPR_SCHEDULE_simple[@]}" )

[perezoso]

Hmm...  well perhaps not the config.  The Kiwi log is telling me this for each channel:

Sat Jul  4 01:21:58 02:51:26.094 0.234567        7 SND BAD PARAMS: sl=19 83|69|84 [SET lms_autonotch=0] ip=192.168.1.90 ####################################

[Rick]

I see spots being reported for callsign WA3098SWL.  Are you still having problems?

[perezoso]

I'm afraid those spots are from the system I was trying to replace.

The wsprdaemon log is now reporting line 1 and 5004 errors like this:

./wsprdaemon.sh: line 1: 12850 Killed                  posting_daemon ${receiver_name} ${receiver_band} "${real_receiver_list}" > ${receiver_posting_dir}/posting.log 2>&1  (wd: /tmp/wsprdaemon/posting.d/KIWI_0/17)

./wsprdaemon.sh: line 5004: 13192 Killed                  posting_daemon ${receiver_name} ${receiver_band} "${real_receiver_list}" > ${receiver_posting_dir}/posting.log 2>&1  (wd: /tmp/wsprdaemon/posting.d/KIWI_0/80)

And these are still showing up in the Kiwi log:

Sat Jul  4 10:45:04 08:18:53.193 01234567 0        SND BAD PARAMS: sl=19 83|69|84 [SET lms_autonotch=0] ip=192.168.1.90 ####################################

[Rob]

Your symptoms suggest that your WD server is failing to connect to the Kiwi.
Make sure you can open a Kiwi listening session from a browser on your WD server.
How is the Kiwi configured?  It should be set up for 8 channel mode and no auto-wspr channels configured.
Log on the Kiwi's admin pages and you should see 8 users 'wsprdaemon v2.9..' listed.

[Rob]

Another possibility is that your server is not in time sync.
Run 'date' and verify the time is correct.

[perezoso]

The Kiwi was configured for the right number of channels, and its status did reflect that wsprdaemon was attaching to them (and there were no autowspr sessions).  Hmmm....

I've had to put this down for a while due to other commitments, but will come back soon!   Thanks.

[Rob]

Cn the browser on the Pi access Internet web sites like google.com?

Is the time accurate on the Pi?  Install NTP on the Pi if it isn't already

On Wed, Jul 8, 2020 at 8:09 AM perezoso [via wsprdaemon] <[hidden email]> wrote:

The Kiwi was configured for the right number of channels, and its status did reflect that wsprdaemon was attaching to them (and there were no autowspr sessions).  Hmmm....

I've had to put this down for a while due to other commitments, but will come back soon!   Thanks.

---

If you reply to this email, your message will be added to the discussion below:

http://wsprdaemon.224604.n8.nabble.com/Config-problem-SND-Bad-params-tp98p114.html

To unsubscribe from Config problem? SND Bad params?, click here.
NAML

--

[perezoso]

Well, I read your message Rob and checked timedatectl. It told me that the time is correct and Pi is connected to a network time server.  The Pi networking has been fine since the beginning.

So I decided I would take another run at figuring this out.  Before starting in on it again, and for about the 32nd time in this process, I rebooted the Pi and Kiwi.

I didn't even get to the point of rebooting the beagle, because when the Pi and Kiwi came back up, it started working.

I have no idea why, because I all I did was run timedatectl!  :-)

Thanks for your help Rob, and for making this great script available.

I'm not going to tempt fate and reboot again to see what happens, I'm happy to be up and running!  Something will cause me to reboot sooner or later and we'll see then.

PS:  And twenty minutes later, I got this spot (though I'm kind of wondering it TX power is accurate :