Bug 1802299
Summary: | openvpn cannot seem to load updated lzo | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kevin Fenzi <kevin> |
Component: | openvpn | Assignee: | David Sommerseth <dazo> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | atu, dazo, huzaifas, klember, matt.fagnani, motoskov, steve |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-26 21:55:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kevin Fenzi
2020-02-12 20:29:27 UTC
Sounds like openvpn needs to be rebuilt on Fedora Rawhide. I suspect the lzo library should have done a so name bump but didn't. Fedora Rawhide - openvpn-2.4.8-3: https://koji.fedoraproject.org/koji/taskinfo?taskID=41472040 Alas, the rebuild does not help. ;( Perhaps it cannot deal with this new version of lzo? It jumped from 2.08 to 2.10... Confirmed. Just got a chance to test this on a F32 "pre-release" now. Using --comp-lzo breaks it. I've filed an upstream ticket related to this issue: https://community.openvpn.net/openvpn/ticket/1255 With that said, using compression is really not recommended. I don't recall the complete compatibility matrix for --compress, but you might want to consider using '--compress stub' or '--compress stub-v2' instead of --comp-lzo. This will have enable the "compression framing", but no data sent from the client will be compressed - and the server should normally catch that the client doesn't want compression and not do that. Otherwise, there is also the openvpn3 package, currently available from my Copr repository ;-) https://copr.fedorainfracloud.org/coprs/dsommers/openvpn3/ (the v8_beta is really stable now, we're on a good path moving out of beta releases) I've seen the same error messages as Kevin when I used openvpn-2.4.8-2.fc32.x86_64 to connect to an openvpn server with comp-lzo in the configuration file and lzo-2.10-1.fc32.x86_64 installed. I installed lzop-1.04-3.fc32.x86_64. Running lzop with or without a input file and lzo-2.10-1 showed that lzo failed to start due to a library version conflict. lzop Lempel-Ziv-Oberhumer Packer Copyright (C) 1996 - 2017 lzop v1.04 Markus Franz Xaver Johannes Oberhumer Aug 10th 2017 lzo_init() failed - check your LZO installation ! library version conflict (2080, 20a0) - check your LZO installation ! Downgrading to lzo-2.08-16.fc31.x86_64 fixed the openvpn and lzop errors. *** Bug 1806566 has been marked as a duplicate of this bug. *** Julian Sikorski found that building lzo with the gcc flag -fno-strict-aliasing fixed the problem of lzo-2.10-1 failing to start with lzop https://bugzilla.redhat.com/show_bug.cgi?id=1807737#c5 openvpn ran normally with the lzo-2.10-2 rpm I built after adding Julian's changes and comp-lzo in the openvpn configuration file. Applying Julian's patch to the lzo repo could fix this problem. Thanks. Based on further research, it looks like this is an lzo library issue more than an openvpn issue. Since this is already tracked in bug #1807737, I'm closing this one. |