Message-ID: <568A77D6.2060101@posteo.de>
Date: Mon, 04 Jan 2016 14:47:02 +0100
From: DK7FC <selberdenken@posteo.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
References: <579355A36AEE9D4FA555C45D556003AB25317862@servigilant.vigilant.local> <5255CDA8464845A3B8937A641180CFA4@White> <2965301451575717@web29m.yandex.ru> <579355A36AEE9D4FA555C45D556003AB25318D11@servigilant.vigilant.local> <5688037E.6050803@posteo.de> <56880784.8090105@posteo.de> <ABB310FFCEF84A4D922E5FB9AB37D3C1@IBM7FFA209F07C> <56892CF0.6080102@posteo.de> <04E680673AD94D1F82ED0C52D9A5A9D6@MichaelSappPC> <56897DFF.1060601@gmx.net> <16BB43E0F7E4409A8635FC75DFF064AA@MichaelSappPC>
In-Reply-To: <16BB43E0F7E4409A8635FC75DFF064AA@MichaelSappPC>
Subject: Re: LF: Re: Incomplete uploads on WSPR database
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

Hi Mike,

Thanks for the hint. My ALL_WSPR files were 3.8 MB / 2.8 MB and even 15 
MB. I saved them in a copy now and then removed the content of the main 
file.
Will see if that helps...

73, Stefan

Am 04.01.2016 02:31, schrieb Michael Sapp:
> Tobias: I'm not sure why it made a difference, but I do not seem to 
> have upload issues with wspr-x since making the change.
>
> 73, Mike wa3tts
>
>
> ----- Original Message ----- From: "Tobias DG3LV" <DG3LV@gmx.net>
> To: <rsgb_lf_group@blacksheep.org>
> Sent: Sunday, January 03, 2016 3:01 PM
> Subject: Re: LF: Re: Incomplete uploads on WSPR database
>
>
>> 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:selberdenken@posteo.de>
>>>     *To:* rsgb_lf_group@blacksheep.org
>>> <mailto:rsgb_lf_group@blacksheep.org>
>>>     *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:selberdenken@posteo.de>
>>>>         *To:* rsgb_lf_group@blacksheep.org
>>>> <mailto:rsgb_lf_group@blacksheep.org>
>>>>         *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
>>>>
>>>>
>>>>
>>>>
>>
>
>