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=-2.4 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_MESSAGE 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 u03H598V032163 for ; Sun, 3 Jan 2016 18:05:09 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1aFm0b-00039D-PO for rs_out_1@blacksheep.org; Sun, 03 Jan 2016 16:59:57 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1aFm0b-000394-AR for rsgb_lf_group@blacksheep.org; Sun, 03 Jan 2016 16:59:57 +0000 Received: from vms173023pub.verizon.net ([206.46.173.23]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.86) (envelope-from ) id 1aFlzX-0003im-AR for rsgb_lf_group@blacksheep.org; Sun, 03 Jan 2016 16:59:56 +0000 Received: from MichaelSappPC ([96.236.217.27]) by vms173023.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0O0D00BW1Z5BNZD0@vms173023.mailsrvcs.net> for rsgb_lf_group@blacksheep.org; Sun, 03 Jan 2016 10:58:24 -0600 (CST) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=WcjxEBVX c=1 sm=1 tr=0 a=sG/YOSdHsUNiiEgoQbtjEg==:117 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=7aQ_Q-yQQ-AA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=F3M5lZpKAAAA:8 a=pmXx-AoGAAAA:8 a=sqrhGSPt4WZWMOzuZewA:9 a=wPNLvfGTeEIA:10 a=o4AKhQAmJprLTtNethMA:9 a=SfJcDjds6jEz-Z7W:21 a=_W_S_7VecoQA:10 Message-id: <04E680673AD94D1F82ED0C52D9A5A9D6@MichaelSappPC> From: "Michael Sapp" To: 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> In-reply-to: <56892CF0.6080102@posteo.de> Date: Sun, 03 Jan 2016 11:58:21 -0500 MIME-version: 1.0 X-Priority: 3 X-MSMail-priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18197 X-MIMEOLE: Produced By Microsoft MimeOLE V6.0.6002.18463 X-Scan-Signature: 8c16534bff9e7be1d3e99d60b0efbf3e Subject: Re: LF: Re: Incomplete uploads on WSPR database Content-type: multipart/alternative; boundary="----=_NextPart_000_000B_01D1461E.0B069900" 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: 6083 This is a multi-part message in MIME format. ------=_NextPart_000_000B_01D1461E.0B069900 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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. =20 73 Mike wa3tts ----- Original Message -----=20 From: DK7FC=20 To: rsgb_lf_group@blacksheep.org=20 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:=20 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 -----=20 From: DK7FC=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, January 02, 2016 5:23 PM Subject: LF: Incomplete uploads on WSPR database Hi all,=20 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 =20 2016-01-02 16:58 DL2WB 0.475777 -15 0 JN39qh = 0.2 DK7FC/NW JN49ik 98 81 =20 However the actual decodes were: DK7FC/NW: 1658 -6 5.7 0.475712 0 HB9ASB JN36 50=20 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=20 1658 8 -0.6 0.475754 0 DH5RAE JN68 17 DK7FC: 1658 -7 6.4 0.475714 0 HB9ASB JN36 50=20 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 ------=_NextPart_000_000B_01D1461E.0B069900 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Stefan & All:  If you use = wsprx, try=20 limiting the size of your ALL_WSPR txt file. W1VD pointed this out as = the file=20 contains a record of all of your captures. Rename the file as = ALL_WSPR_OLD and=20 then edit the ALL_WSPR file to a few weeks of data. My ALL_WSPR file had = grown=20 to 6.5MB which is a sizeable upload. I try to keep my ALL_WSPR file to = under=20 250KB. 
 
73 Mike wa3tts
----- Original Message -----
From:=20 DK7FC=20
Sent: Sunday, January 03, 2016 = 9:15=20 AM
Subject: Re: LF: Re: Incomplete = uploads=20 on WSPR database

R Chris, thanks for the feedback.

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

73, Stefan

Am=20 03.01.2016 12:55, schrieb Chris:=20
I frequently get the same problem = Stefan. The=20 program eventually gives up trying to send the spots to the website = and you=20 get a 'timed out' message in the shell. Just before Christmas it was = loading=20 up less than half the spots I was getting, so turned it off, = couldn't=20 see the point if the reports weren't being sent!!
Vy 73 es HNY to All,
Chris, G4AYT.
-----=20 Original Message ----- From:=20 DK7FC To:=20 rsgb_lf_group@blacksheep.org Sent:=20 Saturday, January 02, 2016 5:23 PM Subject:=20 LF: Incomplete uploads on WSPR database

Hi all,

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

For example, this was uploaded from my 3 = stations=20 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=20 actual decodes were:

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

1658 6 -1.0 0.475754 0 = DH5RAE=20 JN68 17

1658 -15 -1.4 0.475777 = 0 DL2WB=20 JN39 23


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

1658 8 -0.6 0.475754 0 = DH5RAE=20 JN68 17


DK7FC:
1658 -7 = 6.4=20 0.475714 0 HB9ASB JN36 50

1658 4 -0.2 0.475757 0 = DH5RAE=20 JN68 17


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


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


73, Stefan




------=_NextPart_000_000B_01D1461E.0B069900--