Redis::TimeoutError : Waited 1.0 seconds / Job exception: MiniScheduler::DistributedMutex::Timeout

Support
,
1

J’ai changé de serveur et je suis passé à un serveur cloud. Je n’ai jamais vu les erreurs suivantes auparavant, je me demande ce qui pourrait les causer et si elles ont un impact négatif sur l’interaction de l’utilisateur ?

Il est possible que cela puisse entraîner des problèmes lors de l’utilisation de l’IA dans l’éditeur. Par exemple, lorsque je l’essaie sur discourse.org, il se bloque pendant la traduction, comme dans l’image ci-dessous :

image
image1150×827 112 KB

Unexpected error while processing cached counts : Redis::TimeoutError : Waited 1.0 seconds
Job exception: Waited 1.0 seconds (redis://localhost:6379/1)
Failed to process job: Waited 1.0 seconds \[“/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-client-0.24.0/lib/redis_client/ruby_connection/buffered_io.rb:214:in block in fill_buffer'", "<inter Failed to process job: Waited 1.0 seconds \["/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-client-0.24.0/lib/redis_client/ruby_connection/buffered_io.rb:214:in block in fill_buffer’”, "<inter
Unexpected error while processing cached counts : Redis::TimeoutError : Waited 1.0 seconds
Job exception: MiniScheduler::DistributedMutex::Timeout
Job exception: Waited 1.0 seconds (redis://localhost:6379/1)
5 Redis::TimeoutError (Waited 1.0 seconds)
4 Unexpected error while processing cached counts : Redis::TimeoutError : Waited 1.0 seconds
1 Like
2

Is this a standard install?

3

yes: discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub

Afterwards, I completed the installation by loading the backup. However, when I tried to correct what I wrote with artificial intelligence, it got stuck and did not open, the same applies here:

image
image1920×1080 234 KB

4

Hmm.

What did you try to correct?

5

I am writing in Turkish while replying to you and when I ask the artificial intelligence assistant to translate it into English, it gets stuck as in the picture.

image
image1514×716 55.7 KB

2 Likes
6

Oh. Sorry. I didn’t understand.

What do you get from

free -h
df -h
7 
               total        used        free      shared  buff/cache   available
Mem:           7.6Gi       6.2Gi       1.3Gi       1.2Gi       1.6Gi       1.4Gi
Swap:             0B          0B          0B

Filesystem      Size  Used Avail Use% Mounted on
tmpfs           775M  956K  774M   1% /run
efivarfs        256K   27K  225K  11% /sys/firmware/efi/efivars
/dev/sda1        75G   21G   51G  30% /
tmpfs           3.8G     0  3.8G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sda15      253M  6.2M  246M   3% /boot/efi
overlay          75G   21G   51G  30% /var/lib/docker/overlay2/*****************/merged
tmpfs           775M   12K  775M   1% /run/user/0
8

Sorry. I don’t have any other ideas.

1 Like
9

At least I’m relieved that it’s not just me :slight_smile: Maybe it’s a browser issue. I’ll watch it a little more. Thanks.

10

Be sure to rebuild, I did fix a “getting stuck” issue.

That said we try to maintain language when we proof read and somehow in your case it is not working.

Which LLM are you using?

1 Like
11

chatgpt 4 omnio mini :slight_smile: