Bug 496951

Summary: Tps server fails to start when CS.cfg is enabling logging with bad log file name
Product: [Retired] Dogtag Certificate System Reporter: Asha Akkiangady <aakkiang>
Component: TPSAssignee: Christina Fu <cfu>
Status: CLOSED WONTFIX QA Contact: Chandrasekar Kannan <ckannan>
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: alee, benl, jgalipea, jmagne
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-11 20:26:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 445047    

Description Asha Akkiangady 2009-04-21 19:01:55 UTC
Description of problem
Tps server fails to start when CS.cfg is enabling logging with bad log file name. 

Version-Release number of selected component (if applicable):
CS 8.0

How reproducible:


Steps to Reproduce:
1. TPS CS.cfg has debug logging enabled and location of the file is non existing ( example: logging.debug.filename=/var/lib/pki-tps/notexist/tps-debug.log)
2. Restart tps server.

  
Actual results:
Unable to start Apache:
    The tps module configuration file called
    '/var/lib/pki-tps/conf/CS.cfg' does not exist!
                                                        
Expected results:
TPS Server should be able to start up without logging.

Additional info:
Same error message is thrown when audit log or error log is enabled and log file name is pointed to a bad location.