# Sidekiq s'arrête et ne redémarre pas

**URL:** <https://meta.discourse.org/t/sidekiq-dying-and-not-coming-back-up/111267>\
**Category:** Self-hosting\
**Created:** [Mars 11, 2019, 12:51 UTC](https://meta.discourse.org/t/sidekiq-dying-and-not-coming-back-up/111267 "2019-03-11T12:51:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![LeoMcA](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leomca/32/87233_2.png) [@LeoMcA](https://meta.discourse.org/u/LeoMcA)\
**Post date:** [Mars 11, 2019, 5:59 UTC](https://meta.discourse.org/t/sidekiq-dying-and-not-coming-back-up/111267/4 "2019-03-11T17:59:05Z")

</div>

Thanks for the comments, both - I imagine this new log will help a lot!

I’ve currently got it logging active jobs every minute, but I guess I’ll have to be really lucky to find the job that kills sidekiq with it set that high (or the job will have to be running a _really_ long time).

@david what performance impact are we looking at logging every second? I suppose all we’d hang is the sidekiq thread, which is hardly a problem when it’s not working properly anyway.

Log looks great, very nice to see it as JSON. My plan is to convert that to CSV, so I can open it as a spreadsheet and filter by the pid of the sidekiq process which died when that happens.

Perhaps for casual log-viewing, separate files for the finished and pending jobs might be useful, but I don’t think anyone’s likely to be viewing this log without some time on their hands to grep through it.

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-dying-and-not-coming-back-up/111267)._