# Goodbye Sidetiq

**URL:** https://meta.discourse.org/t/goodbye-sidetiq/12476
**Category:** Feature
**Created:** [2월 5, 2014, 10:38오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476 "2014-02-05T22:38:31Z")
**Posts on this page:** 20
**Page:** 2

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [2월 8, 2014, 9:17오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/22 "2014-02-08T21:17:33Z")

</div>

Going to checkout master right now, hang on.

---

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [2월 8, 2014, 9:30오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/23 "2014-02-08T21:30:18Z")

</div>

Checking out master (and flushing redis and restarting) didn’t change anything.

I did look through the bugfixes after 0.9.8.4 and I verified that those are now there. Should have gone to master before posting this issue, my apologies for that. But in this case it didn’t solve the problem.

BTW I’m on multisite, since there were a few multisite bugs I’m now going to hack my config and see if this occurs on the main site as well.  
EDIT yes it occurs on the main site as well.

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2월 8, 2014, 9:40오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/24 "2014-02-08T21:40:43Z")

</div>

I’m seeing this Internal Server Error on my test docker setup, too.

---

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [2월 8, 2014, 9:46오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/25 "2014-02-08T21:46:51Z")

</div>

Do you also see the “Not Scheduled Yet” messages @riking?

Flush redis to make the screen work again, or replace

```
      @schedules = Scheduler::Manager.discover_schedules.sort do |a,b|
        a.schedule_info.next_run <=> b.schedule_info.next_run
      end

```

by

```
      @schedules = Scheduler::Manager.discover_schedules

```

in lib/scheduler/web.rb

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2월 8, 2014, 9:50오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/26 "2014-02-08T21:50:28Z")

</div>

Yes, and yes it happened after clicking Schedule. Basically the exact same thing you reported. I haven’t flushed redis yet though.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 8, 2014, 10:16오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/27 "2014-02-08T22:16:41Z")

</div>

(will sort out first thing tomorrow)

curious, can you add a few “puts” statements and find out why its not scheduling stuff? only about 20 lines of code involved in all of this.

---

<div class="post-metadata">

### Author: ![Lee\_Ars](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lee_ars/32/1597_2.png) [@Lee\_Ars](https://meta.discourse.org/u/Lee_Ars)
#### Post date: [2월 9, 2014, 3:19오전 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/28 "2014-02-09T03:19:03Z")

</div>

> [@codinghorror](#):
>
> Yes. We also want to have a “howto convert from regular to Docker install” posted soon. @sam has done a number of conversions from old-style Discourse install to new Docker installs now and has documented the process internally.
> 
> @zogstrip and @sam are working on necessary import/export improvements and once that is ready, it should go up.

If you need an external guinea pig, I’m happy to volunteer. I know I’m somewhat of an odd duck since I’m banging along with Passenger, but I’m happy to help if there’s any way I can be useful.

---

<div class="post-metadata">

### Author: ![MpaK](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpak/32/108025_2.png) [@MpaK](https://meta.discourse.org/u/MpaK)
#### Post date: [2월 9, 2014, 3:58오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/29 "2014-02-09T15:58:43Z")

</div>

hi!  
I think my problem with deployment through the capistrano related to this topic, yes or not?

when I try to deploy I see these error:

```
uninitialized constant IceCube::ValidatedRule
/home/deployer/hanuman/releases/20140209154603/lib/freedom_patches/ice_cube.rb:2:in `<module:IceCube>'
/home/deployer/hanuman/releases/20140209154603/lib/freedom_patches/ice_cube.rb:1:in `<top (required)>'
 /home/deployer/hanuman/releases/20140209154603/config/initializers/02-freedom_patches.rb:2:in `block in <top (required)>'

```

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 9, 2014, 10:09오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/30 "2014-02-09T22:09:00Z")

</div>

This is totally unrelated @MpaK we no longer have this gem installed, looks  
like a bad merge of a fork or something

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 9, 2014, 10:33오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/31 "2014-02-09T22:33:24Z")

</div>

> [@Lee\_Ars](#):
>
> If you need an external guinea pig,

we sure do, but its going to have to wait till @zogstrip finalizes the import / export stuff

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 9, 2014, 10:36오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/32 "2014-02-09T22:36:56Z")

</div>

I fixed the sorting issue, but am unable to reproduce the issue where the scheduler does not run at all.

on a clean docker install my scheduler is firing fine.

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2월 9, 2014, 11:18오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/33 "2014-02-09T23:18:17Z")

</div>

Oh yeah, it was running. I’ve got a happy face on the update check.

---

<div class="post-metadata">

### Author: ![Lee\_Ars](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lee_ars/32/1597_2.png) [@Lee\_Ars](https://meta.discourse.org/u/Lee_Ars)
#### Post date: [2월 10, 2014, 1:07오전 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/34 "2014-02-10T01:07:35Z")

</div>

> [@sam](#):
>
> we sure do, but its going to have to wait till @zogstrip finalizes the import / export stuff

LMK whenever. This ought to be an interesting test case, considering how much my install has been through since, uh…(checks)…March 2013 😃

---

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [2월 10, 2014, 7:53오전 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/35 "2014-02-10T07:53:26Z")

</div>

Sorting issue is gone, when I hit Trigger then a job is scheduled, and it looks like it is re-scheduled after it has ran.

So there is only an initialization issue left. I’ll have a further look tonight, @sam can you give me some pointers where to look?

---

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [2월 10, 2014, 10:13오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/36 "2014-02-10T22:13:05Z")

</div>

> [@sam](#):
>
> I fixed the sorting issue, but am unable to reproduce the issue where the scheduler does not run at all

Ok. Found it. Just to share our shame:

After endless debugging, it seemed like Redis was not storing anything upon startup.  
Then we finally remembered the following line in our startup script, right AFTER starting sidekiq.

```
echo flushdb | /usr/bin/redis-cli

```

It was put there many, many months ago, trying to work around a totally different and long, long forgotten issue. 😢

This is the first time that Discourse ever _relied_ on redis. Before this change, redis was ‘just’ a cache.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 10, 2014, 11:17오후 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/37 "2014-02-10T23:17:58Z")

</div>

> [@michaeld](#):
>
> This is the first time that Discourse ever relied on redis.

Actually it always sort of relies on Redis, when you nuke you would miss out on a pile of scheduled jobs, emails would go missing for example. message bus would also play up.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 11, 2014, 12:15오전 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/39 "2014-02-11T00:15:54Z")

</div>



---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 11, 2014, 12:16오전 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/40 "2014-02-11T00:16:22Z")

</div>

Just unpinned this, no serious issues were found.

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [2월 14, 2014, 12:33오전 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/41 "2014-02-14T00:33:44Z")

</div>

Backup/Restore is now available in master. Please try it out 😄

**WARNING** : backups are safe, but restore might require a server restart (just kill the thins/unicorns).

---

<div class="post-metadata">

### Author: ![Lee\_Ars](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lee_ars/32/1597_2.png) [@Lee\_Ars](https://meta.discourse.org/u/Lee_Ars)
#### Post date: [2월 15, 2014, 2:59오전 UTC](https://meta.discourse.org/t/goodbye-sidetiq/12476/42 "2014-02-15T02:59:56Z")

</div>

Backup generates [this log](http://www.bigdinosaur.org/r/discoursebackup.txt) (password redacted!) and completes successfully. I now have a 15MB .tar.gz backup file under `/public/backup/defaults`

Read-only mode appears to work correctly.

However, the “Restore” and “Rollback” buttons are grayed out and display the “No” cursor when I attempt to click them.

 ![](https://global.discourse-cdn.com/meta/original/2X/3/3003a1d56d54a8255e66e7751051170160e7aa34.png) 

edit - @zogstrip or @sam, happy to grant you guys temporary admin accounts if you want to look at anything.

[이전 페이지](https://meta.discourse.org/t/goodbye-sidetiq/12476.md?page=1)

[다음 페이지](https://meta.discourse.org/t/goodbye-sidetiq/12476.md?page=3)