CentOS 7.4 (1708)

Erulezz

Verified User
Joined
Sep 14, 2015
Messages
905
Location
🇳🇱
https://lists.centos.org/pipermail/centos-announce/2017-September/022532.html

I am pleased to announce the general availability of CentOS Linux 7
(1708) for 64 bit x86 compatible machines. Effectively immediately, this
is the current release for CentOS Linux 7 and is tagged as 1708, derived
from Red Hat Enterprise Linux 7.4

As always, read through the Release Notes at :
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes
contain important information about the release and details about some
of the content inside the release from the CentOS QA team. These notes
are updated constantly to include issues and incorporate feedback from
the users.

Has anybody upgraded yet? Is DirectAdmin fully compatible?
 
Hi,

After update my 3 servers to 7.4, letsencrypt does not work. Get this error: "Getting challenge for domain.com from acme-server... Error: http://domain.com/.well-known/acme-challenge/letsencrypt_1505726864 is not reachable. Aborting the script. dig output for domain.com: IPv4 Please make sure /.well-known alias is setup in WWW server."

I follow this guide to debug it https://help.directadmin.com/item.php?id=646

I create a test.txt in /var/www/html/.well-known/acme-challenge, and can access it via browser.

And seem there is a problem with curl. curl does not output any result but only 3 "???" (attachment)da.PNG

On my other Ubuntu server, I can curl it da.PNG

Same error on my 2 others centos 7.4 servers.

Do you got the same problem?

I still leave the file test.txt, you can help me test ti @ [FONT=&quot]curl -I -L -k -X GET http://[/FONT][FONT=&quot]locthosoft.com[/FONT][FONT=&quot]/.well-known/acme-challenge/test.txt[/FONT]
 
Last edited:
Let's Encrypt works correct on my servers with CentOS 7.4. I would suggest you do:

Code:
./build update
./build rewrite_confs
./build curl
./build php n
 
Let's Encrypt works correct on my servers with CentOS 7.4. I would suggest you do:

Code:
./build update
./build rewrite_confs
./build curl
./build php n

After update curl, got this error: curl: (8) Weird server reply

This is output from curl -V


curl 7.55.1 (x86_64-pc-linux-gnu) libcurl/7.55.1 OpenSSL/1.0.2k zlib/1.2.7
Release-Date: 2017-08-14
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile NTLM NTLM_WB SSL libz UnixSockets HTTPS-proxy

Am I missing something?
 
I found the problem.

This is DirectAdmin http2 config problem, |LINKEDIP| in nginx-vhost.conf add http2 in port 80 cause curl error.

I added a custom template that replace LINKEDIP with my ipv6 like this:

listen [2400:8901:0:0:f03c:91ff:fe59:xxxx]:80;

|LINKEDIPSSL| works fine as http2 works only on port 443.
 
ISSUE not booting in combination with Xen PV BUG

BUG
Take care not installing the default CENTOS 7.4 kernel if possible or before reboot/restart delete and install the kernel-plus while with the normal kernel and XEN PV the BOX isn't rebooting anymore!

https://bugs.centos.org/view.php?id=13763#c30014
0013763: CentOS 7.4 kernel (3.10.0-693*) fails to boot as Xen PV guest
Description After a mailing list post indicating Xen PV guest not booting with CR kernel for 7.4:

Someone knows from DIRECTADMIN support the kernel-plus is OK to use with DIRECTADMIN?

With many thanks to hughesjr and toracat, the patch indicated in my previous comment is now in CentOS Plus kernel 3.10.0-693.2.1. I've asked Red Hat to apply it to some future kernel update, but that is only a dream for now.

In the meantime, if anyone who has been experiencing the issue with PV domains can try out the CentOS Plus kernel here and provide feedback, I'd appreciate it!

https://buildlogs.centos.org/c7-plu...163005/3.10.0-693.2.1.el7.centos.plus.x86_64/


For the record, those 3.10.0-693.* CentOS Plus kernels are now available via the regular centosplus repository.

https://wiki.centos.org/AdditionalResources/Repositories/CentOSPlus
http://mirror.centos.org/centos/7.4.1708/centosplus/x86_64/Packages/


Kevin, thanks for managing this bug for us - saved my bacon. I ran into it when rebooting a database server and have proactively switched to kernel-plus on a dozen other VM's, both in-house and cloud-hosted (on XenPV). They have been fully updated and rebooted successfully. I've started a blog entry/howto on this issue, which is really major IMO <https://www.bfccomputing.com/2017/09/15/centos-plus-kernel-for-xen.html> - if you can add me to the RHBZ, I'll verify that my claims are accurate. RHBZ id is [email protected] .
Today I spent the day debugging why a database server wouldn’t boot and, eventually, removing the Redhat kernel from all of our CentOS 7 virtual machines.
Why would I go and do a damn fool thing like that? Well, it turns out that that the RHEL/CentOS 7.4 kernel doesn’t work with XenPV virtualization, which we use in-house and some of our cloud providers use. Not just small ones either - Amazon’s M3 and C3 instances are likely affected.

Take care with this Kernel guys!
Besides the Xen bug, if you do rpm -q --changelog kernel-plus you’ll see there are a few other bugs fixed in kernel-plus that aren’t available in kernel, even on the CR channel. A bug like this one is evidence enough for me that the CentOS team is trustworthy and they are getting bug fixes out to community users much more rapidly than commercial users get. Did I mention they are really doing Open Source right? For this reason I am going to be using the kernel-plus kernel preferentially over the stock kernel in the future. Timely bug fixes are critical to productivity
 
Last edited:
Someone knows from DIRECTADMIN support the kernel-plus is OK to use with DIRECTADMIN?


As far as I know Directadmin does not really care of your kernel version. We've got various combinations here:


- CentOS 6 running as a container on CentOS 5 host with a kernel 2.6.18-417.el5
- CentOS 6 running with 4.13.3-1.el6.elrepo.x86_64 kernel.


and other various combinations with CentOS 7.

And kernel-plus is fine here too.
 
Back
Top