[pskmail] Re: Problem: server does not always transmit
- From: Pär Crusefalk <per@xxxxxxxxxxxx>
- To: pskmail@xxxxxxxxxxxxx
- Date: Mon, 30 Jun 2014 08:07:16 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Franz,
The problem is actually that Dave, w1hkj, has been looking at crash logs
from fldigi (when used with pskmail) and has been trying to find the
cause of the segfaults we regularly experience. Fldigi 3.21.82AD had an
extra handshake mechanism between it and the pskmail server, he
suspected a too rapid mode change could be the cause. This in turn had
to be implemented in the pskmail server and Rein and I (possibly others
as well) have been testing an experimental server version that handles
that extra handshake. I have not looked at 3.21.83 but I think Dave was
going forward with this extra handshake thing so that fldigi version
3.21.82AD or higher will not work with the older pskmail servers or clients.
I'm extremly glad that Dave is taking the time and helping find the
cause of these crashes, unfortunately they still remain so this extra
handshake does not seem to be the cure.
So, to summarize: Don't use fldigi 3.21.83 with anything less than the
latest experimental server. Also, the changes will break the 1.5 client
as well.
73 de Per, sm0rwo
P.s. For those of you that have these crashes and wonder what a segfault
is I recommend the wikipedia article on the subject. As I am a certified
C/C++ developer that has switched to managed code (c# and java) I got a
kick out of this sentence: "Segmentation faults have various causes, and
are a common problem in programs written in the C programming language,
where they arise primarily due to errors in use of pointers for virtual
memory addressing, particularly illegal access."
Franz Rohrauer skrev 2014-06-29 21:21:
> Per,
>
> you are right, I think, we have a bad problem!
>
> Yesterday I connected TRX to dummy-load and analyzed last nights
fldigi-debuggers output: my server did not send any beacons between
23.00 GMT and 05.00 GMT!
>
> I can not localize and have no idea: is it a rflinkserver (2.2.2)- or
a fldigi (3.21.83)-problem?
>
> see debuggers output in the attachment...
>
> 73, Franz, oe5rtl
>
> Am 2014-06-28 15:53, schrieb Pär Crusefalk:
>>
>> Hi, I'm away on a short trip but perhaps you could upload to
subversion? I can send details as soon as I get home. Regarding pings my
server is testing an experimental fldigi and it does receive but not
always transmit.
>>
>> 73 de Per
>>
>> Skickat från min Sony Xperia™-smartphone
>>
>>
>>
>> ---- Juergen skrev ----
>>
>> Hi Franz,
>> I've downloaded the bug fixed version of pskmailserver from:
http://www.pskmail.org/downloads/pskmail_server-2.2.2.tgz ,
>> because in the former version APRS Email didn't work. I've installed
it but the bug was still there.
>> Rein (see Email below) wrote, that there are problems with the SSL,
smtp code, so I changed the perl source of the rflinkserver to fix it.
>> I've tested it with two big Email providers:
>> smtp.gmail.com, Port 465/SSL, Port 587/TLS, Port25/TLS
>> smtp.mail.yahoo.com, Port 465/SSL, Port 587/TLS, Port25/TLS
>>
>> The connected and the APRS Email worked both now.
>> Unfortunately I didn't find an email adress or server location to
upload the changed rflinkserver in pskmail.org, but I think Rein should
know more about that matter or do you know something ?
>>
>> What new server version do you use ?
>>
>> 73
>> Juergen
>> DL8JF
>>
>> P.S.: In over 90% of all ping requests in pskmail I sent, I got reply
from OE5RTL.
>>
>>
>>
>>
>>
>> On 06/27/2014 10:26 PM, Franz Rohrauer wrote:
>>> Hi Juergen,
>>>
>>> this weekend will I reinstall my server. Can I help you?
>>>
>>> Franz, oe5rtl
>>>
>>> Am 2014-06-27 13:27, schrieb Juergen:
>>>> I have a working solution for the gmail smtp stuff.
>>>> Is there a server or an email adress, where I can upload the files ?
>>>>
>>>> 73
>>>> Juergen
>>>> DL8JF
>>>>
>>>> On 06/17/2014 05:51 PM, Rein Couperus wrote:
>>>>> Perl SSL as been broken since 2011...
>>>>>
>>>>> I have built up a test server to get things going again. If there is
>>>>> somebody with a working solution for gmail smtp I would gratefully
accept it :-)
>>>>>
>>>>> The 2012 workaround does not seem to work anymore.
>>>>>
>>>>> POP mail works, at least on web.de. Should work on gmail as well.
>>>>> For gmail POP, remember to use the full userid, including @gmail...
>>>>>
>>>>> The session password does not have to be changed, as it is only known
>>>>> at the server (encrypted...).
>>>>>
>>>>> Stay tuned...
>>>>>
>>>>> Rein PA0R
>>>>>
>>>>> --
>>>>
>>>
>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTsP6UAAoJENJa8unLWIP2hukH/RJwG/iwLgG4heHSmJOqh8KT
Qt8Gx/dMpSs02cBBvXBF9FnsIv8uJaNgnxdMalSgbYvpif00vWW2vjDUY2Av4j5r
1fIHxRc/IhU3H2i4LhCGUSsYiMAtKAQTPQTVlUd++npAX9fKcJCxDikG7XBRjlj0
gI/q3vsFvnoscybb33GqqLbXpc1BmXHeZZwqqEtqqhc9MRgvF3EDZApZEKr/e2xQ
5K9sXwe/zUBe1x0Epsd+R6pGQVQZr8HnxoJsa9YmELoZbH3QVid9fm/jydNYDoqw
sLMtmbt8HdiG94yvvYGWMjtl0SteMS6/jOAxZ9gCaddrNx7SjXD5KVlUcCdIdGs=
=W0W7
-----END PGP SIGNATURE-----
Other related posts:
