Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > muc.lists.qmail > #3292 > unrolled thread

Difficulties bringing up s/qmail: sslserver is segfaulting.

Started byAlan Mackenzie <acm@muc.de>
First post2024-09-05 20:47 +0000
Last post2024-09-08 12:10 +0000
Articles 2 — 1 participant

Back to article view | Back to muc.lists.qmail


Contents

  Difficulties bringing up s/qmail: sslserver is segfaulting. Alan Mackenzie <acm@muc.de> - 2024-09-05 20:47 +0000
    Re: Difficulties bringing up s/qmail: sslserver is segfaulting. Alan Mackenzie <acm@muc.de> - 2024-09-08 12:10 +0000

#3292 — Difficulties bringing up s/qmail: sslserver is segfaulting.

FromAlan Mackenzie <acm@muc.de>
Date2024-09-05 20:47 +0000
SubjectDifficulties bringing up s/qmail: sslserver is segfaulting.
Message-ID<ZtoY-FhNe10vqIRJ@ACM>
Date: Thu, 5 Sep 2024 20:36:18 +0000
From: Alan Mackenzie <acm@muc.de>
To: qmail@list.cr.yp.to
Subject: Difficulties bringing up s/qmail: sslserver is segfaulting.

Hello, qmail.

I'm in the process of installing s/qmail on my new desktop machine, and
am experiencing more difficulty than I usually do with this program.

I have daemontools-0.76-r11 installed from Gentoo's package repository
(I am unable to build it from the original source).  At boot up time
daemontools is trying to start sslserver, I believe as a component of
qmail-smtpd.

This attempt to start sslserver is occurring every second, so I have a
fairly full /var/log/messages by now.  ;-(  A typical pair of lines from
that log file look like:


Sep  5 20:19:00 MAC kernel: sslserver[10531]: segfault at 0 ip 000056285f7a6c04 sp 00007ffdbda3f0c8 error 4 in sslserver[56285f796000+14000] likely on CPU 10 (core 12, socket 0)
Sep  5 20:19:00 MAC kernel: Code: eb c3 0f 1f 40 00 0f b6 47 01 41 bb 01 00 00 00 41 ba ff ff ff ff 41 b9 01 00 00 00 e9 73 ff ff ff 0f 1f 44 00 00 f3 0f 1e fa <0f> b6 07 31 c9 31 d2 83 e8 30 44 0f b6 c0 3c 09 77 27 66 2e 0f 1f

Could somebody give me some hint as to what I'm doing wrong, please?
Otherwise, what would be the best way for me to start debugging this
problem?

Thanks!

-- 
Alan Mackenzie (Nuremberg, Germany).

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [next] | [standalone]


#3293

FromAlan Mackenzie <acm@muc.de>
Date2024-09-08 12:10 +0000
Message-ID<Zt2USRSoD_cLxuMU@ACM>
In reply to#3292
Hello, Shepherd.

On Fri, Sep 06, 2024 at 08:21:36 +0200, Shepherd Nhongo wrote:
>    The server rejected the connection thus why you get ssl /tls error 4 .
>    First check the permissions & availability of the ssl/tls certificates

The actual cause of the segfault, which I sorted out in private email,
was my building ucspi-ssl with the wrong version of fehQlibs.  I now
know that using the latest version all the time is not the right thing
to do.

I've now managed to deliver a test message from my new s/qmail.

Thanks!

>    Sent from my iPhone

>      On 05 Sep 2024, at 22:55, Alan Mackenzie <acm@muc.de> wrote:

>    error 4 in sslserver[

-- 
Alan Mackenzie (Nuremberg, Germany).

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

[toc] | [prev] | [standalone]


Back to top | Article view | muc.lists.qmail


csiph-web