Return-Path: X-Spam-DCC: paranoid 1290; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, RATWARE_GECKO_BUILD autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id u03K7xQn032513 for ; Sun, 3 Jan 2016 21:07:59 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1aForO-0003X9-S2 for rs_out_1@blacksheep.org; Sun, 03 Jan 2016 20:02:38 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1aForO-0003X0-9U for rsgb_lf_group@blacksheep.org; Sun, 03 Jan 2016 20:02:38 +0000 Received: from mout.gmx.net ([212.227.15.19]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86) (envelope-from ) id 1aFoqK-00041S-5q for rsgb_lf_group@blacksheep.org; Sun, 03 Jan 2016 20:02:37 +0000 Received: from [192.168.0.100] ([185.78.62.74]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0LdZAI-1Zq4Xm09dC-00ijL5 for ; Sun, 03 Jan 2016 21:01:16 +0100 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> <56892CF0.6080102@posteo.de> <04E680673AD94D1F82ED0C52D9A5A9D6@MichaelSappPC> From: Tobias DG3LV Message-ID: <56897DFF.1060601@gmx.net> Date: Sun, 3 Jan 2016 21:01:03 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <04E680673AD94D1F82ED0C52D9A5A9D6@MichaelSappPC> X-Provags-ID: V03:K0:cjzaa0INg7xV8WOK0joHgw8TI3gdcNq5LpprAekYK77YS0M+Qk9 uJrI9RRsro5pVPfTopFpeb+YWLnUgEbJyETzUyMjzmHqkt/mdMXiOxOa4Yzvk1C5djiubwE i354vWchemFGmD1R5At+kW0ITgieIs9uQB4Fk+p1CHYl8UEi7QSv5GND+PYI7gw1U1sK225 0n7dXQzwQ2iznqsge9DLw== X-UI-Out-Filterresults: notjunk:1;V01:K0:dVzZOwwmyFg=:ujAigG227EqsQwCFhI5tf8 YsL4rgkNvB6aKOvJ2x2i+LN6kqUxiEWIkC6wifQqp8pZkfeA6uG6y2jv0t20sHdBQ12fpSouJ vuIqpJP0O8Nk/FFP5rcNtSS5MBPnotIaKrQVR4Rk4K1t8+WFUsN56FAnaSpEi5waFFYShBR9I tzRY9NDA4XUPETO+Nzr4N2oWNId5H6RSkbAkw5DmZGf1jRqRvCytIj44/uX2p0kQS45qpA9dJ 3Fi95TA48UohBxRVGSlCY4FanJ/2aTAgO/wGwILRXejEMw/jL6mtJeo0mlEQsvHmoGXi81kpR jAjChrkRKjhTX93P5qEnjd1jHT9HV8JxxiaBLccsTK4dkQJuHoAspHxGjLYysdqf4jZuKMxKs dHtTbyz2Mte+PWP+devmTDObDfULhDFgIG+Ue1PrtcaNh69P908us3Q9Sfs9X93jgnqzavGM5 YRUNwcimRDzIfQJGNt276unOrMWb8hhZPlNu3qg70bkAONTcHmh7UMEGoXCpKk6Vdou0u7DHF ph7Ti3Yda17zDp2uV2AcyxuUUrnxEuBCEn2N2bWytOe8SPBF6cCjZ35zyxQpn9JJ10WFHGGvb b5fOt70U2wDuvzgu2Yn+3nWQaI9z+Xb1HsAUFMhK2ANgD0A45UDUeoX6rUgElPJMfAkMt+sft 9LT/7kMK6f7Y5hdB3pPjWFud481bmfHyVlcJ8JneiZtcAHVGY+QVJT9ziFlhAv4vaIBjvgZ5v QnC+0KlQvIkRuRZQLuaqiEgqS1Wlbv3gZgvEWvIWcGzLE46kQIlaijrG8lp7U2sBy9x1jmJJm ecDhvkC X-Scan-Signature: 2ee80849a5d572dbc974bb207a527753 Subject: Re: LF: Re: Incomplete uploads on WSPR database Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Scanned-By: MIMEDefang 2.56 on 10.1.3.10 Status: O X-Status: X-Keywords: X-UID: 6086 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 > *To:* 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 >> *To:* 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 >> >> >> >>