RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Would like to have an option in the Luci web interface or as a start option for /etc/sysconfig/luci to enable debugging. In addition would like to have various levels of debugging.

Need someway of enabling debugging with minimal editing of configuration files. The current file to edit debug options for luci is in:
/var/lib/luci/etc/luci.ini


Version-Release number of selected component (if applicable):
luci-0.22.2-14.el6_0.1.x86_64

How reproducible:
None

Steps to Reproduce:
1.None
  
Actual results:
None

Expected results:
None

Additional info:

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Luci lacked a way for users to debug problems on the fly if debugging was not enabled prior to starting luci.

Consequence: GSS was not able to debug problems using luci on the fly.

Change: Controls were added that allow admin users to tune the log levels of messages generated by luci by message type while luci is running.

Result: GSS can use the controls that were added to increase log message verbosity after luci has been started.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0766.html