Unable to locate config for object-expirer

[wangyanhehe41721]

object-auditor running (25856 - /etc/swift/object-server/2.conf)
object-auditor running (25866 - /etc/swift/object-server/3.conf)
object-auditor running (25838 - /etc/swift/object-server/1.conf)
object-auditor running (25908 - /etc/swift/object-server/5.conf)
object-auditor running (25913 - /etc/swift/object-server/6.conf)
object-auditor running (25898 - /etc/swift/object-server/4.conf)
object-auditor already started...
Unable to locate config for object-expirer
container-auditor running (25920 - /etc/swift/container-server/2.conf)
container-auditor running (25921 - /etc/swift/container-server/3.conf)
container-auditor running (25922 - /etc/swift/container-server/4.conf)
container-auditor running (25930 - /etc/swift/container-server/5.conf)
container-auditor running (25936 - /etc/swift/container-server/6.conf)
container-auditor running (25917 - /etc/swift/container-server/1.conf)
container-auditor already started...

[Tom Fifield (fifieldt)]

Hi,

What version of Swift is this?

What is in /etc/swift ?

[wangyanhehe41721 (wangyan4172)]

thank you I have already resolved the problem,in the /etc/swift/object-sevice/1-6.conf add [object-expirer]
and in the /etc/swift/ add object-expirer.conf
[DEFAULT]
# swift_dir = /etc/swift
# user = swift
# You can specify default log routing here if you want:
# log_name = swift
# log_facility = LOG_LOCAL0
# log_level = INFO
[object-expirer]
interval = 300
[pipeline:main]
pipeline = catch_errors cache proxy-server
[app:proxy-server]
use = egg:swift#proxy
# See proxy-server.conf-sample for options

[filter:cache]
use = egg:swift#memcache
# See proxy-server.conf-sample for options

[filter:catch_errors]
use = egg:swift#catch_errors
# See proxy-server.conf-sample for options
~

[Peter Portante (peter-a-portante)]

This is still happening, see:

http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiVW5hYmxlIHRvIGxvY2F0ZSBjb25maWcgZm9yIG9iamVjdC1leHBpcmVyXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImFsbCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzODUyMzQwMTA2MjR9

[Chmouel Boudjnah (chmouel)]

Hello, I think I misclicked this should be more a won't fix, That object-expirer message is just a warning and I didn't configure it on a devstack since it wasn't needed and I was trying to save some memory spaces. We can surely configure in devstack if that's really needed but I don't think that's a error.

[Peter Portante (peter-a-portante)]

Do you think it is worth getting devstack to run all the swift components as many customers do? Or is devstack sufficiently different that it is not worth doing that?