Univention Bugzilla – Bug 36136
Debug / support via log file
Last modified: 2014-11-26 06:54:03 CET
Currently, the log file contains mostly messages like this:
Exception in update() in thread EC Fail: EC2_EU_WEST
That might be OK if you have full access to the local server and can do research on this server. But if you get only the log file from the customer, you have no chance to investigate the error.
I think we need at least in the error scenario the following information:
- which user
- which connection
- the traceback
r54382 univention-virtual-machine-manager-daemon 4.0.3-4
A traceback is now logged if an error occurs. In addition, the last error message can be queried by the frontend if desired
OK, it looks better. I see some tracebacks in the logfile.
But I see a log of messages in this format by default every 15 seconds:
2014-10-30 05:40:00,962 - uvmmd.cloudconnection - DEBUG - Updating information for OpenStack: http://192.168.0.79:5000
2014-10-30 05:40:01,315 - uvmmd.cloudconnection - DEBUG - Updating took 0.352607011795 seconds for OpenStack
2014-10-30 05:40:01,316 - uvmmd.cloudconnection - DEBUG - Next update for OpenStack: 0:00:15.000
I think we should increase the default log level, currently:
In other modules we use PROCESS but I think UVMM uses different names. Maybe INFO is the right level.
r55169 univention-virtual-machine-manager-daemon 4.0.7-3
UCS 4.0-0 has been released:
If this error occurs again, please use "Clone This Bug".