Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 228278 - Luci service should not start until after luci_admin init is run
Luci service should not start until after luci_admin init is run
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: conga (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Stanko Kupcevic
Corey Marthaler
Depends On:
  Show dependency treegraph
Reported: 2007-02-12 09:18 EST by Len DiMaggio
Modified: 2009-04-16 18:35 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-12 13:39:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Len DiMaggio 2007-02-12 09:18:04 EST
Description of problem:
Luci service should not start until after luci_admin init is run

If the service is run before the 'luci_admin init' command is first run, an
error occurs. We should have the service fail to start, or return an error.

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

How reproducible:

Steps to Reproduce:
1. On a new install, start the luci service before first running luci_admin init -
2. Then access https://host:8084 - this error is returned:

The Luci server has not been initialized. To initialize it, log in in to the
server as root and run the command
luci_admin init

Actual results:
The above error

Expected results:
An error returned if the luci service is started before it has been initialized

Additional info:
Comment 1 Stanko Kupcevic 2007-02-12 13:39:50 EST
This is an intended behavior. 

It was chosen with a premise that it is better to guide users thru
initialization ("initialize me" message), rather than making them debug the
problem (service failing to start). 

Closing as NOTABUG 

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