harbor icon indicating copy to clipboard operation
harbor copied to clipboard

Harbor replication does not give any reason of failed event

Open rajatrj16 opened this issue 10 months ago • 3 comments

There is no proper error message in harbor Why replication fails randomly?

Upon going to logs in failed event there are details which is not clear why the error is {"errors":[{"code":"NOT_FOUND","message":"{\"code\":10010,\"message\":\"object is not found\",\"details\":\"97833e43ff5b2a1e3fa3d790\"}"}]} image

rajatrj16 avatar Apr 15 '24 10:04 rajatrj16

What does it say in the replication logs?

AMC-7 avatar Apr 19 '24 07:04 AMC-7

@AMC-7 This is the error comes in the replication logs {"errors":[{"code":"NOT_FOUND","message":"{\"code\":10010,\"message\":\"object is not found\",\"details\":\"97833e43ff5b2a1e3fa3d790\"}"}]}

rajatrj16 avatar Apr 25 '24 09:04 rajatrj16

same issue in 2.9.4

cataglyphis avatar Jun 12 '24 11:06 cataglyphis

encountered this on v2.10.1 as well

nikokirilenko avatar Jul 17 '24 09:07 nikokirilenko

Im not sure, if you have the same problem or not. But the error is exactly what we received. We had all inodes used in one pod. harbor [ /harbor ]$ df -i /dev/sdc 65536 65536 0 100% /var/log/jobs

This means, there are so many small files, that all inodes are used and no new one can be written. It has the same effect, as when all space is used.

Doriangaensslen avatar Jul 23 '24 08:07 Doriangaensslen