Bug 859750

Summary: dirsrv-admin do not start on F18
Product: [Fedora] Fedora Reporter: Michael S. <misc>
Component: 389-adminAssignee: Rich Megginson <rmeggins>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: nhosoi, nkinder, rmeggins, wielkipiec
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-admin-1.1.31-1.fc18.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-04 22:41: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:
Attachments:
Description Flags
patch adding the missing directory, preventing the package from starting. none

Description Michael S. 2012-09-23 18:40:37 UTC
Created attachment 616196 [details]
patch adding the missing directory, preventing the package from starting.

Description of problem:

389-ds refuse to start on fedora 18.

First, there is a issue with apache ( see https://fedorahosted.org/389/ticket/476 for a fix ).


Then I have seen this :
(2)No such file or directory: AH02291: Cannot access directory '/var/log/dirsrv/admin-serv/' for main error log

And indeed, the file is not present in any package, patch attached.



Next issue is with selinux :
(13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:9830

I had to use setenforce 0 to have it started, so I suspect the issue is that httpd is not started under the proper label.
I didn't found anything about port 9830 in selinux configuration.



( then it fail for another reason, likely the lack of servers :

[Sun Sep 23 20:28:15.010799 2012] [:crit] [pid 8842:tid 3071645568] do_admserv_post_config(): unable to create AdmldapInfo
AH00016: Configuration Failed

Comment 1 Kamil J. Dudek 2012-12-18 01:39:02 UTC
Currently, the dirsrv-admin service cannot start because of the httpd error "No MPM loaded". Manual configuration of httpd modules(which should not be required, and it has never been before) leads to the aforementrioned ":crit" with do_admserv_post_config().

Comment 2 Nathan Kinder 2013-03-04 22:41:50 UTC
This was fixed in 389-admin-1.1.31-1.fc18.1.  Closing.