From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Packages for next Core Update
Date: Sun, 27 Jan 2019 10:06:30 +0100 [thread overview]
Message-ID: <cd064fae-ae5e-e41d-4d88-4c6dc6b01202@ipfire.org> (raw)
In-Reply-To: <9fe16d86-f1c7-d104-a100-05311cd150b5@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
On 23.01.2019 14:55, Peter Müller wrote:
> Hello,
Hi,
> just a quick footnote:
>
> I am currently building
> - OpenSSH 7.9p1
> - Apache 2.4.38
> ...
FYI:
While building Apache 2.4.38 I encountered a problem that I can't really
explain to myself.
I started the first build under current 'next', adjusted the 'rootfile'
and tested it on my testmachine. Logically 'httpd' refused to start -
system is too old.
So I changed 'Devel'-branch to current 'Core 126', built again with a
clean build and 'httpd' started. GUI came up - everything seemed to be
OK. But looking at '/var/log/httpd/error_log' I found:
...
[Sat Jan 26 17:20:47.617067 2019] [ssl:warn] [pid 3574:tid 1275335360]
AH01882: Init: this version of mod_ssl was compiled against a newer
library (OpenSSL 1.1.0j 20 Nov 2018, version currently loaded is
OpenSSL 1.1.0i 14 Aug 2018) - may result in undefined or erroneous behavior
...
The next try with Core 125 was successful, no errors in log anymore. Now
this version - built under Core *125* - is running on my productive
machine (Core *126*) without *seen* problems.
The 'openssl' version check on this machine gives me:
...
OpenSSL 1.1.0j 20 Nov 2018 (Library: OpenSSL 1.1.0i 14 Aug 2018)
...
Output in 'error_log':
..
Apache/2.4.38 (Unix) OpenSSL/1.1.0i configured -- resuming normal operations
...
I a bit puzzled because of the two different OpenSSL version-numbers.
Did I miss something?
Best,
Matthias
next prev parent reply other threads:[~2019-01-27 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 13:55 Peter Müller
2019-01-23 17:42 ` Matthias Fischer
2019-01-27 9:06 ` Matthias Fischer [this message]
2019-01-28 11:39 ` Michael Tremer
2019-01-28 17:17 ` Matthias Fischer
2019-01-28 18:32 ` Matthias Fischer
2019-01-29 16:00 ` Michael Tremer
2019-01-29 17:39 ` Matthias Fischer
2019-01-29 17:57 ` Arne Fitzenreiter
2019-01-29 18:15 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd064fae-ae5e-e41d-4d88-4c6dc6b01202@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox