# Sidekiq is not running, probably after upgrade

**URL:** https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135
**Category:** Support
**Created:** [September 23, 2020, 7:41pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135 "2020-09-23T19:41:09Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![HeyRR](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heyrr/32/192157_2.png) [@HeyRR](https://meta.discourse.org/u/HeyRR)
#### Post date: [September 23, 2020, 7:41pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/1 "2020-09-23T19:41:09Z")

</div>

Site advise shows:

> “Sidekiq is not running. Many tasks, like sending emails, are executed asynchronously by sidekiq. Please ensure at least one sidekiq process is running. [Learn about Sidekiq here](https://github.com/mperham/sidekiq).”

Manually trigger jobs in sidekiq seems does not work either( I tried return heartbeat task but looks like it failed.  
 ![image](https://global.discourse-cdn.com/meta/optimized/3X/d/b/db95b7e8746a9bdcec5236b814c1174c0da3e691_2_690x31.png)  
Also upgrade discourse gives me a blank page forever.

 ![image](https://global.discourse-cdn.com/meta/original/3X/c/1/c18304e267d1908eea7b2c734c53ad2939c8bb9f.png)

Any suggestion on how to bring my site back to normal?

---

<div class="post-metadata">

### Author: ![IAmGav](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iamgav/32/235598_2.png) [@IAmGav](https://meta.discourse.org/u/IAmGav)
#### Post date: [September 23, 2020, 8:33pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/2 "2020-09-23T20:33:32Z")

</div>

try a rebuild via the command line and not the web interface

---

<div class="post-metadata">

### Author: ![HeyRR](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heyrr/32/192157_2.png) [@HeyRR](https://meta.discourse.org/u/HeyRR)
#### Post date: [September 23, 2020, 9:05pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/3 "2020-09-23T21:05:11Z")

</div>

Thanks! I just tried a few commands:

`./launcher rebuild app`  
 → Cannot connect to the docker daemon - verify it is running and you have access

`service docker start`  
 → return nothing

`docker info`  
 → `fatal error: runtime: out of memory`

> **runtime stack**
>
> ```plaintext
> runtime.throw(0x561377414b98, 0x16)
> /usr/local/go/src/runtime/panic.go:774 +0x74 fp=0x7ffc1cb23058 sp=0x7ffc1cb23028 pc=0x561375eccf24
> runtime.sysMap(0xc000000000, 0x4000000, 0x56137903e658)
> /usr/local/go/src/runtime/mem_linux.go:169 +0xc7 fp=0x7ffc1cb23098 sp=0x7ffc1cb23058 pc=0x561375eb6a67
> runtime.(*mheap).sysAlloc(0x5613790252c0, 0x2000, 0x0, 0x0)
> /usr/local/go/src/runtime/malloc.go:701 +0x1cf fp=0x7ffc1cb23140 sp=0x7ffc1cb23098 pc=0x561375ea996f
> runtime.(*mheap).grow(0x5613790252c0, 0x1, 0xffffffff)
> /usr/local/go/src/runtime/mheap.go:1255 +0xa5 fp=0x7ffc1cb23190 sp=0x7ffc1cb23140 pc=0x561375ec4c05
> runtime.(*mheap).allocSpanLocked(0x5613790252c0, 0x1, 0x56137903e668, 0x1)
> /usr/local/go/src/runtime/mheap.go:1170 +0x268 fp=0x7ffc1cb23210 sp=0x7ffc1cb23190 pc=0x561375ec4a98
> runtime.(*mheap).alloc_m(0x5613790252c0, 0x1, 0x561375ef002a, 0x0)
> /usr/local/go/src/runtime/mheap.go:1022 +0xc6 fp=0x7ffc1cb23260 sp=0x7ffc1cb23210 pc=0x561375ec4336
> runtime.(*mheap).alloc.func1()
> /usr/local/go/src/runtime/mheap.go:1093 +0x4e fp=0x7ffc1cb23298 sp=0x7ffc1cb23260 pc=0x561375ef642e
> runtime.(*mheap).alloc(0x5613790252c0, 0x1, 0x1002a, 0x40000)
> /usr/local/go/src/runtime/mheap.go:1092 +0x8c fp=0x7ffc1cb232e8 sp=0x7ffc1cb23298 pc=0x561375ec461c
> runtime.(*mcentral).grow(0x5613790260f8, 0x0)
> /usr/local/go/src/runtime/mcentral.go:255 +0x7d fp=0x7ffc1cb23328 sp=0x7ffc1cb232e8 pc=0x561375eb648d
> runtime.(*mcentral).cacheSpan(0x5613790260f8, 0x7fb47f218000)
> /usr/local/go/src/runtime/mcentral.go:106 +0x300 fp=0x7ffc1cb23388 sp=0x7ffc1cb23328 pc=0x561375eb5fb0
> runtime.(*mcache).refill(0x7fb47f218008, 0x2a)
> /usr/local/go/src/runtime/mcache.go:138 +0x87 fp=0x7ffc1cb233a8 sp=0x7ffc1cb23388 pc=0x561375eb5a47
> runtime.(*mcache).nextFree(0x7fb47f218008, 0x56137903e62a, 0x7fb47f218008, 0x8, 0xfffffffffffffff8)
> /usr/local/go/src/runtime/malloc.go:854 +0x89 fp=0x7ffc1cb233e0 sp=0x7ffc1cb233a8 pc=0x561375eaa199
> runtime.mallocgc(0x180, 0x561378084760, 0x1, 0x56137903e6c0)
> /usr/local/go/src/runtime/malloc.go:1022 +0x7a5 fp=0x7ffc1cb23480 sp=0x7ffc1cb233e0 pc=0x561375eaaae5
> runtime.newobject(0x561378084760, 0x4000)
> /usr/local/go/src/runtime/malloc.go:1151 +0x3a fp=0x7ffc1cb234b0 sp=0x7ffc1cb23480 pc=0x561375eaaeea
> runtime.malg(0x33eb6a00008000, 0x561379027968)
> /usr/local/go/src/runtime/proc.go:3232 +0x33 fp=0x7ffc1cb234f0 sp=0x7ffc1cb234b0 pc=0x561375ed63f3
> runtime.mpreinit(...)
> /usr/local/go/src/runtime/os_linux.go:324
> runtime.mcommoninit(0x56137901f580)
> /usr/local/go/src/runtime/proc.go:626 +0xc6 fp=0x7ffc1cb23528 sp=0x7ffc1cb234f0 pc=0x561375ecfd26
> runtime.schedinit()
> /usr/local/go/src/runtime/proc.go:543 +0x76 fp=0x7ffc1cb23580 sp=0x7ffc1cb23528 pc=0x561375ecf986
> runtime.rt0_go(0x7ffc1cb23688, 0x2, 0x7ffc1cb23688, 0x0, 0x7fb47e84ab97, 0x2, 0x7ffc1cb23688, 0x200008000, 0x561375ef8780, 0x0, ...)
> /usr/local/go/src/runtime/asm_amd64.s:214 +0x129 fp=0x7ffc1cb23588 sp=0x7ffc1cb23580 pc=0x561375ef88b9
> 
> ```

What information I need or what can I do to further investigate this?

---

<div class="post-metadata">

### Author: ![IAmGav](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iamgav/32/235598_2.png) [@IAmGav](https://meta.discourse.org/u/IAmGav)
#### Post date: [September 23, 2020, 9:11pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/4 "2020-09-23T21:11:16Z")

</div>

try

`./launcher destroy app`  
`./launcher start app`

---

<div class="post-metadata">

### Author: ![HeyRR](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heyrr/32/192157_2.png) [@HeyRR](https://meta.discourse.org/u/HeyRR)
#### Post date: [September 23, 2020, 9:13pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/5 "2020-09-23T21:13:41Z")

</div>

both commands give me `Cannot connect to the docker daemon - verify it is running and you have access`

---

<div class="post-metadata">

### Author: ![IAmGav](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iamgav/32/235598_2.png) [@IAmGav](https://meta.discourse.org/u/IAmGav)
#### Post date: [September 23, 2020, 9:16pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/6 "2020-09-23T21:16:30Z")

</div>

then use sudo to run the docker

`sudo service docker start`

---

<div class="post-metadata">

### Author: ![HeyRR](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heyrr/32/192157_2.png) [@HeyRR](https://meta.discourse.org/u/HeyRR)
#### Post date: [September 23, 2020, 9:53pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/7 "2020-09-23T21:53:18Z")

</div>

> [@IAmGav](#):
>
> sudo service docker start

this returns nothing and rerun `./launcher start app` still shows same " `Cannot connect to the docker daemon`" error.

BTW, `free -h` result, I experienced one error update 4 days ago and from that time disk and cpu shows spike metrics.

```plaintext
+-------+-------+------+------+--------+------------+-----------+
| | total | used | free | shared | buff/cache | available |
+-------+-------+------+------+--------+------------+-----------+
| Mem: | 1.9G | 1.6G | 78M | 194M | 246M | 30M |
+-------+-------+------+------+--------+------------+-----------+
| Swap: | 2.0G | 2.0G | 0B | | | |
+-------+-------+------+------+--------+------------+-----------+

```

 ![image](https://global.discourse-cdn.com/meta/original/3X/f/d/fd00328920548d5054d3e805a80a8d3e9b913ce4.png)

will I lost all data if I just restart my instance?

---

<div class="post-metadata">

### Author: ![IAmGav](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iamgav/32/235598_2.png) [@IAmGav](https://meta.discourse.org/u/IAmGav)
#### Post date: [September 23, 2020, 10:00pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/8 "2020-09-23T22:00:28Z")

</div>

> [@HeyRR](#):
>
> will I lost all data if I just restart my instance?

Not sure anyone can 100% answer this question, but the only thing todo is a reboot.

---

<div class="post-metadata">

### Author: ![HeyRR](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heyrr/32/192157_2.png) [@HeyRR](https://meta.discourse.org/u/HeyRR)
#### Post date: [September 23, 2020, 10:21pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/9 "2020-09-23T22:21:36Z")

</div>

For anyone who has the same issue, an instance reboot works for me and RAM/Swap back to normal:

```plaintext
+-------+-------+------+------+--------+------------+-----------+
| | total | used | free | shared | buff/cache | available |
+-------+-------+------+------+--------+------------+-----------+
| Mem: | 1.9G | 985M | 76M | 40M | 931M | 785M |
+-------+-------+------+------+--------+------------+-----------+
| Swap: | 2.0G | 6.8M | 2.0G | | | |
+-------+-------+------+------+--------+------------+-----------+

```

then I just rerun `./launcher rebuild app` and everything works again, sidekiq starts to work.

---

<div class="post-metadata">

### Author: ![HeyRR](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heyrr/32/192157_2.png) [@HeyRR](https://meta.discourse.org/u/HeyRR)
#### Post date: [September 23, 2020, 10:23pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/10 "2020-09-23T22:23:32Z")

</div>

Thank you so much for all your help! 🎉

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [October 23, 2020, 10:34pm UTC](https://meta.discourse.org/t/sidekiq-is-not-running-probably-after-upgrade/165135/11 "2020-10-23T22:34:19Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
