Project

General

Profile

Actions
Copy link

Bug #2174

closed

Wrong log settings should have the proxy terminate on startup

Added by Dennis Jacobfeuerborn over 11 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

When specifying "STDOUT" which is mentioned as a possibility in the settings file the proxy starts fine but apparently all calls to it from the web UI result in a 500 internal server error.

The proxy should fail to start up in such a case with an appropriate error so this can be caught easier as the 500 errors are not easy to correlate to the log settings of the proxy.

Related issues 2 (0 open — 2 closed)

Related to Smart Proxy - Refactor #11323: Refactor PID writing, interrupt trap and daemon loggingClosedLukas Zapletal08/11/2015Actions
Has duplicate Smart Proxy - Bug #2173: "500 internal error" when proxy log file is invalidClosed02/03/2013Actions
Actions
Copy link

Also available in: Atom PDF