Wondering if I can resolve this issue by either flushing Redis or updating it; it hasn’t really been touched in the last 8+ months. I have not personally dealt with Redis before, but our Tests-Pass Discourse instance was setup using local_discourse rather than the Discourse Docker that is now recom…

If it makes sense to migrate, I’m open to suggestions.

[이미지] sunjam: but our Tests-Pass Discourse instance was setup using local_discourse rather than the Discourse Docker that is now recommended on this forum. That’s been the recommendation for at least the last 4 years. I’d second Rafael’s suggestion.

Would it help for me to use launcher to rebuilt or restart the redis container? Usage: launcher COMMAND CONFIG [–skip-prereqs] [–docker-args STRING] Commands: start: Start/initialize a container stop: Stop a running container restart: Restart a container destroy: Stop and…

Did you install following the Discourse official Standard Installation guide or some other way? If you have a standard installation, then yes, doing a ./launcher rebuild app will likely solve whatever your problem is.

Not yet, but we’re setting a time to migrate. Our Discourse has been running for almost three years and I just don’t want to add any unnecessary downtime. :slight_smile: Our instance is entirely maintained by volunteers so I’ve been teaching myself how to maintain it in the last month. If a quick…

If you didn’t do a standard install to begin with, it’s anyone’s guess about what might fix your current problem. I’d set up a new VM and do a test install there to make sure it works. When you do the transfer, you can put the old forum in read-only mode, take a backup, restore it to the new VM, an…

Thank you, the Let’s Encrypt should actually be quite easy since it has been setup to be a simple nginx reverse proxy edit. Good to hear, and expect, there will be some downtime. Just need to schedule this on an off hour.

I’m about to migrate and restore the backup into official images. Is there anything I should know regarding clearing out backed emails, etc. that would spam the users once sidekiq, etc. is running properly. Thanks!

The sidekiq job queue won’t move over, so a lot of emails will be dropped, while digests will resume sending normally.

So, attempting to follow the documentation for installing official Discourse docker images and running into trouble. We concluded we are missing the redis container, mail-receiver container and data container we’d had previously in Docker. Seems our previous installation includes: app.yml data.y…

Sidekiq 실행되지 않음. Sidekiq 하트비트 테스트 실패, 재시작 중

지원 자체 호스팅

Falco (Falco) 3월 31, 2020, 7:42오후 3

I suggest taking a backup of your current install and creating a brand new one following the Discourse official Standard Installation

글		댓글	조회수
"Ensure sidekiq is running." when it is definitely running Self-hosting	18	7981	10월 2, 2015
Sidekiq heartbeat test failed, restarting Self-hosting	11	2228	1월 12, 2020
"Sidekiq is not running" Self-hosting	6	3125	2월 7, 2016
Could sidekiq queue be reason for 500 errors? Self-hosting server-resources	30	4169	6월 13, 2018
Sidekiq not working Self-hosting	9	1261	9월 2, 2023

Sidekiq 실행되지 않음. Sidekiq 하트비트 테스트 실패, 재시작 중

Related topics