On Mon, Jun 30, 2014 at 09:00:52AM -0400, Sean Dague wrote: > Every time I crack open a nova logs in detail, at least 2 new olso > incubator log issues have been introduced. > > The current ones is clearly someone is over exploding arrays, as we're > getting things like: > 2014-06-29 13:36:41.403 19459 DEBUG nova.openstack.common.processutils > [-] Running cmd (subprocess): [ ' e n v ' , ' L C _ A L L = C ' , ' > L A N G = C ' , ' q e m u - i m g ' , ' i n f o ' , ' / o p t / s > t a c k / d a t a / n o v a / i n s t a n c e s / e f f 7 3 1 3 a - 1 1 > b 2 - 4 0 2 b - 9 c c d - 6 5 7 8 c b 8 7 9 2 d b / d i s k ' ] execute > /opt/stack/new/nova/nova/openstack/common/processutils.py:160 > > (yes all those spaces are in there, which now effectively inhibits search).
Thanks for raising this. I did come across this issue, but missed to raise this. A few days ago, while debugging a snapshots issue, I was looking for `qemu-img` invocations that definitely should be there in the DevStack n-cpu logs, surpised to find nothing from my `grep` results, I opened the log and manually scrolled to find the command logged with a space after each character: --- [. . .] from (pid=15696) log_http_response /opt/stack/python-glanceclient/glanceclient/common/http.py:167 2014-06-30 23:15:19.061 DEBUG nova.openstack.common.processutils [req-70582307-5245-4703-b1be-48a6e88c7285 admin admin] Running cmd (subprocess): [ ' e n v ' , ' L C _ A L L = C ' , ' L A N G = C ' , ' q e m u - i m g ' , ' i n f o ' , ' / h o m e / k a s h y a p c / s r c / o p e n s t a c k / d a t a / n o v a / i n s t a n c e s / _ b a s e / 4 0 2 c e 6 0 7 0 8 0 2 a 6 e 7 c 8 a d 9 4 8 0 0 c 9 d d 5 f 6 8 1 e 7 c d 3 2 . p a r t ' [. . .] --- Happy to test and provide feedback if there's a fix in progress somewhere. -- /kashyap _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
