Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1092113

Summary: super long lines in compute.log
Product: Red Hat OpenStack Reporter: Dan Yocum <dyocum>
Component: openstack-novaAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact: Ami Jeain <ajeain>
Severity: low Docs Contact:
Priority: low    
Version: 3.0CC: ndipanov, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-30 08:40:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
super long line from compute.log on comp026.os1.phx2.redhat.com none

Description Dan Yocum 2014-04-28 18:51:10 UTC
Created attachment 890559 [details]
super long line from compute.log on comp026.os1.phx2.redhat.com

Description of problem:
Some lines in the /var/log/nova/compute.log file are extremely long.  49,000+ characters.  

Version-Release number of selected component (if applicable):
openstack-nova-compute-2013.1.5-2.el6ost.noarch

How reproducible:
All the time

See attached line from compute.log

Comment 2 Nikola Dipanov 2014-04-30 08:40:04 UTC
There are two ways to fix this - one is directly where this message gets logged, which since Icehouse (so  5.0 and above) belongs to oslo.messaging library.

The other more general way is to add a setting or a default for auto-wrapping/truncating messages in the logging code. Neither are ideal, for different reasons.

One reasonable solution to mitigate this problem might be making the logging call that actually logs the whole contents of the RPC message be debug instead of warn. However this work needs to happen in oslo.messaging.

I will open an upstream bug for this on oslo.messaging and close this as it should be resolved upstream,

Comment 3 Dan Yocum 2014-05-27 17:09:31 UTC
Upon further reflection and hearing other clouds experience RPC errors - I think this issue is NOT related to the length of the lines in the log file, but rather the length of the amqp message.  I can't imagine that 49,000+ characters is an acceptable amqp message length.