Sidekiq is consuming too much memory, restarting

(Dandrews) #21

Has the issue resolved after you bumped up to 8gb? I’m considering doing the same as you since we’re still get these sidekiq errors on a 4gb machine.

(Happy Lee) #22

Fortunately, after increasing to 8GB, the problem has not recurred.

(Dandrews) #23

Thanks! I’ll try that approach then.

(Stephen Chung) #24

It suddenly started appearing to me a couple of days ago.

Before I never saw Sidekiq is using too much memory errors in the logs. Now I see them a few times a day.

And today it happened exactly as @pelcami has mentioned: the VM just plainly became unresponsive. SSH didn’t work. No access on HTTP or HTTPS.

The VM is on Azure, so I pulled up the charts, and it showed network activity suddenly dropping down completely to zero (like a cliff) and CPU stuck at around 40% (probably completely using up one core). Restarting the VM solved it.

What I want to say is, it happened so suddenly that it was almost like one minute it was business as usual, normal network traffic, then the next minute it fell off a cliff and dropped to zero. Not gradual at all.

Something is happening to trigger an infinite loop in Sidekiq or something…

(Jeff Atwood) #25

You can follow up with @tgxworld who is working the issue.

(Sam Saffron) #26

Be sure to do a full rebuild we recently bumped ruby version in image

(Stephen Chung) #27

ok. I’ll rebuild and observe.

(Stephen Chung) #28

Just as a reminder to people: If you get a “Docker version too low” error during rebuild, read the following:

(RBoy) #29

I’ve started seeing this after an update a few days ago @sam after the Amazon lifecycle patch I did a complete rebuild and now I’m seeing this everyday. Never happened before that.

I’m on v1.9.0.beta14 +200

(Sam Saffron) #30

When is the last time you did a

git pull
./launcher rebuild app

You could be on an older version of Ruby.

(RBoy) #31

I did this for the build above beta14+200

I didn’t do a git pull, thought that rebuild does that.

EDIT: Okay I’m it again now, lets see how it goes.

(Jay Pfaffman) #32

That’s good to know. Also, I just noticed that vagrant is still on Rails 4.

(RBoy) #33

No issues so far after a git pull + rebuild instead of just a rebuild. Somehow I thought a rebuild would also do a pull

(Tumi) #34

this is the dashboard from what ? pls teach me .

(Andrew Waugh) #35

Go to yourforumurl/sidekiq to see what sidekiq is doing


/logs to see the error log

/admin/upgrade#/processes to see processes

(RBoy) #36

Just thought I’d share that updating to v2.0.0 beta1 a couple of weeks ago this problem started again.

Sidekiq is consuming too much memory (using: 513.13M)

I checked the dashboard and it’s currently using about 6M but somehow it ramps up to 500 about once a day I see this warning in the logs. Oddly it’s always around 4:20am to 4:50am in the mornings.

(Jeff Atwood) #37

Almost certainly a scheduled daily task cc @sam

(Jeff Atwood) #38

Also, if your server has enough total RAM, you can increase the memory allocation for Sidekiq.

Place this in the env: section of app.yml:


The default maximum is, I believe, 500mb.