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=1.8 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, FORGED_MUA_OUTLOOK,HTML_50_60,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 u03C1EG7031659 for ; Sun, 3 Jan 2016 13:01:14 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1aFhGu-0002kG-JK for rs_out_1@blacksheep.org; Sun, 03 Jan 2016 11:56:28 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1aFhGu-0002k7-52 for rsgb_lf_group@blacksheep.org; Sun, 03 Jan 2016 11:56:28 +0000 Received: from rgout0307.bt.lon5.cpcloud.co.uk ([65.20.0.213]) by relay1.thorcom.net with esmtp (Exim 4.86) (envelope-from ) id 1aFhFq-0003IM-0j for rsgb_lf_group@blacksheep.org; Sun, 03 Jan 2016 11:56:27 +0000 X-OWM-Source-IP: 86.154.133.164 (GB) X-OWM-Env-Sender: c.ashby435@btinternet.com X-CTCH-RefID: str=0001.0A090202.56890C19.0093,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-Junkmail-Premium-Raw: score=29/50,refid=2.7.2:2015.12.19.122116:17:29.943,ip=86.154.133.164,rules=__HAS_MSGID, __SANE_MSGID, INVALID_MSGID_NO_FQDN, __MSGID_32HEX, __HAS_FROM, __PHISH_FROM2, __FRAUD_WEBMAIL_FROM, FROM_NAME_ONE_WORD, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, __CTYPE_MULTIPART_ALT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, __SUBJ_ALPHA_NEGATE, SUPERLONG_LINE, __HTML_AHREF_TAG, __HAS_HTML, HTML_NO_HTTP, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_6000_6999, BODYTEXTH_SIZE_10000_LESS, __MIME_HTML, __TAG_EXISTS_HTML, RDNS_GENERIC_POOLED, __URI_NS, SXL_IP_DYNAMIC[164.133.154.86.fur], HTML_50_70, RDNS_SUSP_GENERIC, __PHISH_FROM, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, FORGED_MUA_OUTLOOK, BODY_SIZE_7000_LESS, NO_URI_HTTPS X-CTCH-Spam: Unknown Received: from IBM7FFA209F07C (86.154.133.164) by rgout03.bt.lon5.cpcloud.co.uk (8.6.122.06) (authenticated as c.ashby435@btinternet.com) id 566CFEA60211CF81 for rsgb_lf_group@blacksheep.org; Sun, 3 Jan 2016 11:55:05 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1451822122; bh=Yjjer5m0/2uQfGKkYE2fIYS45AB9wD0MQNMjDktOZ5Q=; h=Message-ID:From:To:References:Subject:Date:MIME-Version:X-Mailer; b=hCu17FrZ1DkWCxO89Am72paz4ch5dhZAuHZkbviDP4bmOdmRf+PRSJru3bQ/RleuO+nSigv1z1JhTzYYJ29biR8aYj3alUxGyAiUJ1yPlBN35GLDLOAUUGzMQrBAYtD0zcoRngj6IGb+7sfIZcLbq7uirzTyphcSnWU19L3W9l4= Message-ID: From: "Chris" To: References: <579355A36AEE9D4FA555C45D556003AB25317862@servigilant.vigilant.local> <5255CDA8464845A3B8937A641180CFA4@White>,<2965301451575717@web29m.yandex.ru> <579355A36AEE9D4FA555C45D556003AB25318D11@servigilant.vigilant.local> <5688037E.6050803@posteo.de> <56880784.8090105@posteo.de> Date: Sun, 3 Jan 2016 11:55:05 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-Scan-Signature: a44b221381f32eba3e5127fadf77bc3d Subject: LF: Re: Incomplete uploads on WSPR database Content-Type: multipart/alternative; boundary="----=_NextPart_000_002B_01D1461D.95FE6C50" 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: 6081 This is a multi-part message in MIME format. ------=_NextPart_000_002B_01D1461D.95FE6C50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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_002B_01D1461D.95FE6C50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I frequently get the same problem = Stefan. The=20 program eventually gives up trying to send the spots to the website and = you get=20 a 'timed out' message in the shell. Just before Christmas it was loading = up less=20 than half the spots I was getting, so turned it off, couldn't see = the point=20 if the reports weren't being sent!!
Vy 73 es HNY to All,
Chris, G4AYT.
----- Original Message -----
From:=20 DK7FC=20
Sent: Saturday, January 02, = 2016 5:23=20 PM
Subject: LF: Incomplete uploads = on WSPR=20 database

Hi all,

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

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

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

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

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


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

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


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

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


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


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


73, Stefan




------=_NextPart_000_002B_01D1461D.95FE6C50--