High CPU usage after updating to Chatwoot 2.17.0

[Kinzi]

It's "bundle"

[Kinzi]

The process kinda comes and goes every second with verious high CPU usages.

[oj6o3ij5345asd]

Same issue after last update. Always 100% CPU usage.
Also stopped working system notifications in the chat that the operator has assigned himself a dialog or the dialog is closed.
Also stopped working "Automations".
Everything started after last update.

[msbt]

same here on 2 different servers, seems to be a restart loop of sidekiq

[humptydumpty]

I reverted to 1.17.1 and CPU usage went back to normal. I disabled updates for now. Thanks for the heads-up @Kinzi

[oj6o3ij5345asd]

@humptydumpty said in High CPU usage after updating to Chatwoot 2.17.0:

I reverted to 1.17.1

Can you please advise how to do this without losing data?
Since it is impossible to work...

UPDATE: No longer relevant. Restored from backup. Unfortunately, all chats since the update were lost. But better that than work with a lot of problems.

[humptydumpty]

@oj6o3ij5345asd I also restored a backup. I had no data loss because of the short window between the time the update applied and when I restored the previous backup. I just use the live chat feature with business hours and none of the other inbox integrations like email so no harm done.

[timconsidine]

@Kinzi good info
I am confused : is this an upstream issue ? or a Cloudron package update issue ?

[msbt]

Since it also happens with a fresh installation, this release should be revoked. I'm guessing it's a packaging issue, but my ruby knowledge is nonexistant, so not a 100% sure

[sparkwise]

A Redis version issue? Three notes:

1. Logs have error message popping up repeatedly: "You are connecting to Redis 6.0.16, Sidekiq requires Redis 6.2.0 or greater"
2. Images are no longer loading. (server returns 500 error.)
3. Chatwoot 2.1.7 release notes mention new requirements: Rails 7, Redis 7

[nebulon]

Indeed, while running the app package tests, I didn't realize it was running against redis 7 already. The app ends up in a restart loop, causing the high cpu load.

The package version is revoked now and will make it compatible with both if possible. For the moment, you have to restore to the backup made prior to the update.

[nebulon]

So yes it seems we can't update the app now until we release redis 7. Apparently the mentioned recommended version is actually a required version https://www.chatwoot.com/docs/self-hosted/deployment/requirements#redis

[nebulon]

I've published a new app package, which will require Redis 7 and thus Cloudron 7.5, which is the next Cloudron version with an updated Redis. Just mentioning this here, since the chatwoot update will not be advertised until that.

[Latinosnctv]

@nebulon just when I was going to start using the OpenAI api (trial period)

[chris]

@nebulon or @girish we depend on chatwoot for sms business needs, i was not aware of an issue with this update of chatwoot, but i def missed some texts. I visited my cloudron instance a few times but not once did i see a message or warning or error, ideally when a package or update is known to cause issues, we had a way to see that in cloudron. is that possible now? if not can you consider it a feature request. (notfication or alert in dashboard when a rollback is suggested)

[girish]

@chris I think that's a good idea. We revoked (unpublished) the package and this stopped the rollout. But some of them already updated. So, the idea here is to inform people who have revoked packages installed.

Are you able to open a separate feature request thread to track this?

[Kinzi]

@nebulon so this is fixed with the latest update I guess?

[girish]

I think this is fixed, yes. The issue was the redis 7 requirement. So, we revoked the previous package and published a new package with minBoxVersion as 7.5.

[psifertex]

@girish Is there an estimated timeline for 7.5's release? I'm waiting for an upstream fix in 2.18.0 of chatwoot and it sounds like that's blocked on the cloudron update then?