Was the behavior of rsyslog prior to this fix as described in 1683075,
by any chance? Did the resolution wrt the storage issue affect the rsyslog
frequent stoppage? I'm trying to determine if 1683075 is still an issue..
--
You received this bug notification because you are a member of Ubuntu
Bugs
This bug was fixed in the package swift - 2.7.1-0ubuntu2~cloud0
---
swift (2.7.1-0ubuntu2~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
swift (2.7.1-0ubuntu2) xenial; urgency=medium
.
* Fix issue where swift daemons crash while writing
This bug was fixed in the package swift - 2.2.2-0ubuntu1.3~cloud1
---
swift (2.2.2-0ubuntu1.3~cloud1) trusty-kilo; urgency=medium
.
* Fix issue where swift daemons crash while writing logs to a stopped
rsyslogd /dev/log socket. (LP: #1683076)
- d/patches/fix-infinite-rec
I was able to finish verification for trusty-proposed/kilo cloud archive
pocket this evening. Stop rsyslogd while swift services are running and
verify the {object,account,container}-replicator services do not die due
to the inability to write to the logs.
** Tags removed: verification-kilo-needed
This bug was fixed in the package swift - 1.13.1-0ubuntu1.3
---
swift (1.13.1-0ubuntu1.3) trusty; urgency=medium
* Fix issue where swift daemons crash while writing logs to a stopped
rsyslogd /dev/log socket. (LP: #1683076)
- d/patches/fix-infinite-recursion-logging.patch: C
This bug was fixed in the package swift - 2.7.1-0ubuntu2
---
swift (2.7.1-0ubuntu2) xenial; urgency=medium
* Fix issue where swift daemons crash while writing logs to a stopped
rsyslogd /dev/log socket. (LP: #1683076)
- d/patches/fix-infinite-recursion-logging.patch: Cherry-
** Changed in: cloud-archive/icehouse
Status: Triaged => Won't Fix
--
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 notificatio
I have completed the verification of this bug fix for trusty-proposed
and xenial-proposed packages in the Ubuntu project. Tests involve
stopping the logging services (e.g. rsyslog) and ensuring that the
services continue to run.
I have also completed the verification of this bug fix for the trusty
** Tags removed: verification-mitaka-needed
** Tags added: verification-mitaka-done
--
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 n
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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 n
Hello Jill, or anyone else affected,
Accepted swift into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/swift/1.13.1-0ubuntu1.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Thanks Billy. I've uploaded to trusty (unapproved queue), kilo-staging,
and xenial (unapproved queue).
--
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 s
** Changed in: cloud-archive/kilo
Status: New => Triaged
** Changed in: cloud-archive/mitaka
Status: New => Triaged
** Changed in: swift (Ubuntu Trusty)
Status: New => Triaged
** Changed in: swift (Ubuntu Xenial)
Status: New => Triaged
** Changed in: cloud-archive
Updated trusty-mitaka patch with corrected DEP-3 headers
** Patch added: "trusty-mitaka patch"
https://bugs.launchpad.net/charm-swift-storage/+bug/1683076/+attachment/4913506/+files/trusty-mitaka-lp1683076.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Updated trusty-kilo patch with corrected DEP-3 headers
** Patch removed: "trusty-kilo patch"
https://bugs.launchpad.net/charm-swift-storage/+bug/1683076/+attachment/4882216/+files/trusty-kilo.patch
** Patch removed: "trusty-mitaka patch"
https://bugs.launchpad.net/charm-swift-storage/+bug
Updated Origin field to in patch to indicate the patch for xenial is a
clean cherry-pick (e.g. upstream instead of backport per DEP-3
guidelines).
** Patch added: "xenial patch"
https://bugs.launchpad.net/charm-swift-storage/+bug/1683076/+attachment/4913488/+files/xenial2-lp1683076.debdiff
**
Here's a patch for trusty with updated DEP-3 headers and white space
change log removal. I'll seek an additional sponsor for trusty per:
wolsen: since you've rewritten the Trusty patch I don't feel
that I can accept it myself as the SRU reviewer - it needs another
sponsor +1.
** Patch added: "
Hey Robie, here's an updated patch for Xenial. I'll update the patch for
Trusty next and find an additional sponsor to review it.
** Patch added: "xenial patch - take 2"
https://bugs.launchpad.net/charm-swift-storage/+bug/1683076/+attachment/4913483/+files/xenial2-lp1683076.debdiff
** Patch r
15:07 wolsen: around? You need a sponsor for bug 1683076 I
think?
15:08 wolsen: I suggest three minor changes to your trusty
debdiff:
https://git.launchpad.net/~racb/ubuntu/+source/swift/log/?h=lp1683076-trusty
15:09 The dep3 changes apply to your xenial debdiff too I
think. But I'll accept wi
** Patch removed: "trusty patch"
https://bugs.launchpad.net/ubuntu/trusty/+source/swift/+bug/1683076/+attachment/4882251/+files/trusty-lp1683076.debdiff
** Patch added: "trusty patch"
https://bugs.launchpad.net/ubuntu/trusty/+source/swift/+bug/1683076/+attachment/4909084/+files/lp1683076-t
@Robie - sorry the trusty patch was indeed messed up. I've rebuilt and
retested the patch with appropriate dep3 headers and such and you'll
find it more inline with the other patch versions. The trusty one varies
slightly due to the unit test import differences (I tried to keep the
same style) and
The patches look superfluously different between Trusty and Xenial, and
there are no dep3 headers in the Trusty patch. Was this backported, and
if so by whom? Are they both separate cherry-picks from upstream, or
otherwise what has been done to make the patch for Trusty work?
--
You received this
Confirmed this is already fixed in yakkety and later. Reviewed and
sponsored for xenial and trusty.
--
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 sto
This patch is for the icehouse version of swift in Trusty.
** Patch added: "trusty patch"
https://bugs.launchpad.net/ubuntu/trusty/+source/swift/+bug/1683076/+attachment/4882251/+files/trusty-lp1683076.debdiff
** Tags added: ubuntu-sponsors
--
You received this bug notification because you
This patch is for the kilo version of swift for the trusty-kilo Ubuntu
Cloud Archive.
** Patch added: "trusty-kilo patch"
https://bugs.launchpad.net/ubuntu/trusty/+source/swift/+bug/1683076/+attachment/4882216/+files/trusty-kilo.patch
--
You received this bug notification because you are a m
This patch is for the trusty-mitaka version of swift for the trusty-
mitaka Ubuntu Cloud Archive
** Patch added: "trusty-mitaka patch"
https://bugs.launchpad.net/charm-swift-storage/+bug/1683076/+attachment/4882209/+files/lp1683076-trusty-mitaka.debdiff
** Changed in: cloud-archive/icehouse
This patch is for the xenial version of swift.
** Description changed:
Trusty, Mitaka, Juju 1.25.11
We have a cloud where swift replicators are constantly falling over on 2
nodes. This occurs whenever rsyslog restarts, as in
https://bugs.launchpad.net/swift/+bug/1094230
https://r
** Tags added: sts
--
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/cha
** Also affects: cloud-archive/icehouse
Importance: Undecided
Status: New
** Also affects: cloud-archive/kilo
Importance: Undecided
Status: New
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Also affects: cloud-archive/newton
Importanc
** Changed in: cloud-archive/newton
Status: New => Fix Released
--
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
** Also affects: swift (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: swift (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: swift (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubu
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
32 matches
Mail list logo
