Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Some logging messages were added to spice-xpi, including spice-xpi functions called from the web page (javascript) and command line of processes that spice-xpi runs (e.g. spice-xpi-client)
Description of problem:
SSIA. Current spice-xpi code contains only logging definitions in spice-xpi/SpiceXPI/src/plugin/debug.h lines 90-116, but it is used nowhere else and spice-xpi log is always empty.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
(In reply to comment #1)
> Can't debug bug 752111 without spice-xpi logging.
I found out that some logging can be enabled in /usr/share/spice/logger.ini by raising log level to DEBUG, R:
log4j.rootCategory=DEBUG, R
But it doesn't help with our Guest Hot Name issue though. :(
Peter, at the moment, we basically need logging of two kind of things:
1) whenever a web page calls spice-xpi function, log it including all variables that are passed to spice-xpi
2) when spice-xpi runs any other process (spicec, usbrdrctrl), log it including full command line
Both of these should be in INFO level.
It would be also great if the traffic on the controller could be logged, preferably full messages in DEBUG level. But this is of lower priority, if you don't have enough time, just clone it to some other bug so we have the two points above ASAP.
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:
Some logging messages were added to spice-xpi, including spice-xpi functions called from the web page (javascript) and command line of processes that spice-xpi runs (e.g. spice-xpi-client)
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/RHEA-2012-0956.html