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 ** Also affects: swift (Ubuntu) Importance: Undecided Status: New ** Changed in: charm-swift-storage Status: New => Invalid ** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683076 Title: Swift-storage dies if rsyslog is stopped To manage notifications about this bug go to: https://bugs.launchpad.net/charm-swift-storage/+bug/1683076/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
