Hide Forgot
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:
Can't debug bug 752111 without spice-xpi logging.
(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.
please make sure the Spice ActiveX gets the same level of logging
devel acked. considering 6.3 and not 6.2.z due to the time and resources limitationsl
Fixed.
Fixed in spice-xpi-2.7-13.el6.x86_64.
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)
Created attachment 588854 [details] spice-xpi add logging messages patch
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