Bug 1299868 - Syntax error prevents server from starting
Summary: Syntax error prevents server from starting
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mod_auth_openid
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Patrick Uiterwijk
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-19 12:48 UTC by Martin Frodl
Modified: 2020-11-30 15:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 15:55:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin Frodl 2016-01-19 12:48:06 UTC
Description of problem:

With a clean installation of httpd together with mod_auth_openid, the server refuses to start due to the following syntax error in the configuration file:

# service httpd start
Starting httpd: Syntax error on line 2 of /etc/httpd/conf.d/mod_auth_openid.conf:
AuthOpenIDDBLocation not allowed here
                                                           [FAILED]

Version-Release number of selected component (if applicable):
mod_auth_openid-0.7-2.el6.x86_64
httpd-2.2.15-51.el6.x86_64

Comment 1 Kevin Fenzi 2016-01-19 21:27:59 UTC
Yeah, that directive needs to be in a Directory, Location, or File block. 

We should probibly comment it with a note, as we can't tell what Directory, Location or File you might want to protect with OpenID.

...and... we fixed this in a version that never seemed to have gone out as an update. ;( 

Will look and see if we can update things...

Comment 2 Japheth Cleaver 2019-09-27 20:34:45 UTC
This is... still here.

Starting httpd: Syntax error on line 2 of /etc/httpd/conf.d/mod_auth_openid.conf:
AuthOpenIDDBLocation not allowed here
                                                           [FAILED]

Comment 3 Ben Cotton 2020-11-05 16:52:22 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 4 Ben Cotton 2020-11-05 16:55:02 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.

Comment 5 Ben Cotton 2020-11-30 15:55:57 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.