Comment 1 for bug 1683076

This appears to be a bug in the Swift logging behavior not in the charm itself.

There's an upstream commit located at [0] which fixes the problem. In a nutshell, the stopping of rsyslogd in an upstart system removes the /dev/log socket, which causes the swift service's attempt to log a message to fail - which it then proceeds to attempt to log, in the syslog. This spirals out and causes the program to crash due to the infinite recursion overflowing the call stack.

[0] https://github.com/openstack/swift/commit/95efd3f9035ec4141e1b182516f040a59a3e5aa6