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

[kuaza]

I have changed servers and moved to a cloud server. I have never seen the following errors before, I wonder what could be causing them and if they have a negative impact on user interaction?

It is possible that this could lead to problems when using the AI in the editor. For example, when I try it on discourse.org, it crashes during translation, as in the image below:

Unexpected error while processing cached counts : Redis::TimeoutError : Waited 1.0 seconds : Waited 1.0 seconds (redis://localhost:6379/1)
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

[pfaffman (Jay Pfaffman)]

@kuaza

I switched servers and moved to a cloud server.

Is this a standard install?

[kuaza]

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:

[pfaffman (Jay Pfaffman)]

Hmm.

@kuaza

. However, when I tried to correct what I wrote with artificial intelligence

What did you try to correct?

[kuaza]

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.

[pfaffman (Jay Pfaffman)]

Oh. Sorry. I didn’t understand.

What do you get from

free -h
df -h

[kuaza]

@pfaffman

free -h

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

@pfaffman

df -h

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

[pfaffman (Jay Pfaffman)]

Sorry. I don’t have any other ideas.

[kuaza]

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

[sam (Sam Saffron)]

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?

[kuaza]

chatgpt 4 omnio mini