Bug 971424 - [engine-backend] engine.log is flooded with "No string for UNASSIGNED type. Use default Log"
Summary: [engine-backend] engine.log is flooded with "No string for UNASSIGNED type. U...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: unspecified
Hardware: x86_64
OS: Unspecified
high
high
Target Milestone: ---
: 3.2.1
Assignee: Mooli Tayer
QA Contact: Elad
URL:
Whiteboard: infra
Depends On: 962684
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-06 13:24 UTC by Idith Tal-Kohen
Modified: 2016-02-10 19:20 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, after upgrading from 3.1 to more recent versions, the engine log would sometimes become flooded by an error message stating "No string for UNASSIGNED type. Use default Log". This was due to an issue with the mechanism in the audit log that prevents multiple messages under the same logType ( e.g command ) from being printed inside a certain time frame. Now, this has been corrected so that the error message only appears when a message for a logType is not found in AuditLogMessages.properties.
Clone Of: 962684
Environment:
Last Closed: 2013-07-16 13:40:24 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1048 0 normal SHIPPED_LIVE rhevm 3.2.1 bug fix update 2013-07-19 05:45:47 UTC

Comment 3 Leonid Natapov 2013-06-19 11:48:01 UTC 
sf18. fixed. upgrade from 3.1 to 3.2. No flood messages.
Comment 5 errata-xmlrpc 2013-07-16 13:40:24 UTC 
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-2013-1048.html
Note You need to log in before you can comment on or make changes to this bug.