Project

General

Profile

Bug #2180

httpd failing with Syntax error on line 40 with AMD CPUs

Added by cpg almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
10/30/2016
Due date:
% Done:

0%


Description

We have seen some of these:

[amahi@localhost ~]$ service httpd status -l
Redirecting to /bin/systemctl status  -l httpd.service
‚óŹ httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2016-10-30 21:51:09 CDT; 14min ago
  Process: 796 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 796 (code=exited, status=1/FAILURE)

Oct 30 21:51:07 localhost.localdomain systemd[1]: Starting The Apache HTTP Server...
Oct 30 21:51:09 localhost.localdomain httpd[796]: httpd: Syntax error on line 56 of /etc/httpd/conf/httpd.conf: Syntax error on line 40 of /etc/httpd/conf.modules.d/00-base.conf: Cannot load modules/mod_http2.so into server: /etc/httpd/modules/mod_http2.so: undefined symbol: nghttp2_session_change_stream_priority

however, we're not sure why this happens.

somehow, someone suggested after some search or something that this was related to AMD CPUs.

at least two of the people reporting this had an AMD CPU in the system.

History

#1 Updated by cpg almost 4 years ago

there are "reports in the forums"https://forums.amahi.org/viewtopic.php?t=6547 about a fix to this, which is updating the system, or at least updating openssl and possibly httpd:

dnf update openssl httpd

if that does not work, then this is known to work:

dnf update

#2 Updated by cpg almost 4 years ago

  • Status changed from New to Closed
  • Assignee set to cpg

closing as we will not be able to get to the bottom of this.

#3 Updated by cpg almost 4 years ago

  • Subject changed from httpd failing with Syntax error on line 40 to httpd failing with Syntax error on line 40 with AMD CPUs

updated to reflect that it's openssl apparently where the bug was.

Also available in: Atom