Bug 975047
Summary: | Bad log level for messages | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Lon Hohberger <lhh> |
Component: | openstack-swift | Assignee: | Pete Zaitcev <zaitcev> |
Status: | CLOSED DUPLICATE | QA Contact: | Haim <hateya> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | derekh, jhenner, yeylon, zaitcev |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-17 13:53:26 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: |
Description
Lon Hohberger
2013-06-17 13:48:38 UTC
ssh $HOST "killall -9 swift-proxy-server" made the madness end. *** This bug has been marked as a duplicate of bug 967631 *** Lon, please don't touch anything, if you can. I was unable to extract the following two things from Jaroslav - How the wrong permissions occur in the first place. He alluded that "Swift changed the permissions", which sounds too crazy. A spec that specifies that in %dir? I can't find anything like that! So I need your /var/log/yum.log (I know that you mentioned precise rpm versions in the report, thanks a lot) - How the heck the console spam happens to begin with. We never dump at LOG_EMERG. Very puzzling! I thought his rsyslog config was screwed, but perhaps not? If swift is not changing anything, how do you explain the following? [root@folsom-rhel6 ~]# ll -d /etc/swift drwx------. 4 swift swift 4096 16. čen 10.21 /etc/swift [root@folsom-rhel6 ~]# chmod u-r /etc/swift [root@folsom-rhel6 ~]# ll -d /etc/swift d-wx------. 4 swift swift 4096 16. čen 10.21 /etc/swift [root@folsom-rhel6 ~]# /etc/init.d/openstack-swift-proxy restart Stopping openstack-swift-proxy: [ OK ] Starting openstack-swift-proxy: [ OK ] [root@folsom-rhel6 ~]# ll -d /etc/swift drwx------. 4 swift swift 4096 16. čen 10.21 /etc/swift Yes, It is quite crazy, I agree. Day's result 6/19, again on Lon's VM: rsyslog receives message with BOM, looking like this by strace: recvmsg(0, {msg_name(0)=NULL, msg_iov(1)=[{"\357\273\277<146>proxy-server UNCAUGHT EX"..., 2048}] ...... Perhaps there's a unicode-type string in the traceback, causing this behaviour. Still no clue why or how Keystone middleware triggers it. URL: http://docs.python.org/2/howto/logging-cookbook.html#inserting-a-bom-into-messages-sent-to-a-sysloghandler |