Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

Re: LF: Re: Incomplete uploads on WSPR database

To: [email protected]
Subject: Re: LF: Re: Incomplete uploads on WSPR database
From: Tobias DG3LV <[email protected]>
Date: Sun, 3 Jan 2016 21:01:03 +0100
In-reply-to: <04E680673AD94D1F82ED0C52D9A5A9D6@MichaelSappPC>
References: <579355A36AEE9D4FA555C45D556003AB25317862@servigilant.vigilant.local> <5255CDA8464845A3B8937A641180CFA4@White> <[email protected]> <579355A36AEE9D4FA555C45D556003AB25318D11@servigilant.vigilant.local> <[email protected]> <[email protected]> <ABB310FFCEF84A4D922E5FB9AB37D3C1@IBM7FFA209F07C> <[email protected]> <04E680673AD94D1F82ED0C52D9A5A9D6@MichaelSappPC>
Reply-to: [email protected]
Sender: [email protected]
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
Hi Mike !

This file is never uploaded (to the WSPR servers), so for what reason we should keep it small?

HNY & 73 de dg3lv Tobias

Am 03.01.2016 um 17:58 schrieb Michael Sapp:
Stefan & All:  If you use wsprx, try limiting the size of your ALL_WSPR
txt file. W1VD pointed this out as the file contains a record of all of
your captures. Rename the file as ALL_WSPR_OLD and then edit the
ALL_WSPR file to a few weeks of data. My ALL_WSPR file had grown to
6.5MB which is a sizeable upload. I try to keep my ALL_WSPR file to
under 250KB.
73 Mike wa3tts

    ----- Original Message -----
    *From:* DK7FC <mailto:[email protected]>
    *To:* [email protected]
    <mailto:[email protected]>
    *Sent:* Sunday, January 03, 2016 9:15 AM
    *Subject:* Re: LF: Re: Incomplete uploads on WSPR database

    R Chris, thanks for the feedback.

    Well that problem does exist just since a few months. Good to know
    that it is not local.
    Maybe it's due to the permanantly rising usage of the software /
    increasing number of uploaded spots and requested website update?
    See the plot "stations participating per day" at
    http://wsprnet.org/drupal/wsprnet/stats
    Maybe they need a new faster server hardware...

    73, Stefan

    Am 03.01.2016 12:55, schrieb Chris:
    I frequently get the same problem Stefan. The program eventually
    gives up trying to send the spots to the website and you get a
    'timed out' message in the shell. Just before Christmas it was
    loading up less than half the spots I was getting, so turned it
    off, couldn't see the point if the reports weren't being sent!!
    Vy 73 es HNY to All,
    Chris, G4AYT.

        ----- Original Message -----
        *From:* DK7FC <mailto:[email protected]>
        *To:* [email protected]
        <mailto:[email protected]>
        *Sent:* Saturday, January 02, 2016 5:23 PM
        *Subject:* LF: Incomplete uploads on WSPR database

        Hi all,

        For a few times i see now that my local WSPR decodes are not
        completely uploaded to the database. Furthermore it often
        takes very long (> 15 seconds) until the WSPR map or database
        site is loaded.

        For example, this was uploaded from my 3 stations on 16:58 UTC:

        2016-01-02 16:58         HB9ASB          0.475712        +3      0      
 JN36nu          100
         DK7FC/NE        JN49ik          310     22
         2016-01-02 16:58        DL2WB   0.475777        -15     0       JN39qh
         0.2     DK7FC/NW        JN49ik          98      81


        However the actual decodes were:

        DK7FC/NW:
        1658 -6 5.7 0.475712 0 HB9ASB JN36 50

        1658 6 -1.0 0.475754 0 DH5RAE JN68 17

        1658 -15 -1.4 0.475777 0 DL2WB JN39 23


        DK7FC/NE:
        1658 3 6.0 0.475712 0 HB9ASB JN36 50

        1658 8 -0.6 0.475754 0 DH5RAE JN68 17


        DK7FC:
        1658 -7 6.4 0.475714 0 HB9ASB JN36 50

        1658 4 -0.2 0.475757 0 DH5RAE JN68 17


        So 2 decodes are displayed, 7 were made. What happened to the
        other 5? I can see in other time slots that the WSPR instance
        did not hang up, i.e. there are uploads for other decodes. But
        randamly some are lost regularly.


        Do some of you observe similar behaviour of the software? Is
        the problem on my side or does the database somehow have
        problems during the last months?


        73, Stefan





<Prev in Thread] Current Thread [Next in Thread>