Closed tangjiaxing669 closed 1 year ago
It seems your database is in the abnormal status, the db logs shows it tries to recover but failed, the database maybe have the dirty data, so if your harbor is a fresh and no data in it, you could try to clean PVC and re-install it.
@chlins Thank you for your answer. I tried it, I removed all pvc and reinstalled harbor, but the problem is still the same.
It seems your database restart every 20 minutes, do you have any cron jobs do some operations around the terminate time?
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.
I have the exact same issue with the exact same pods.
The behaviour I'm experiencing is that the pods become extremely slow to respond - I believe Kube is killing the pods because they don't respond to the liveness/readiness checks within 1 second.
The weirdest thing is, the pods don't really seem to be doing anything. Almost no CPU/memory usage in metrics yet when I shell into the pod, the database pod in particular, it is very lumpy and slow in performance.
Deploying onto EKS in my case, Kube 1.21.
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.
I use helm to install harbor, I used helm to install harbor, and the next day I found that pods kept restarting. I don't know why, I saw on the Internet that modifying
registry.relativeurls
totrue
can fix the problem (I don't know what this option means), I tried it, but the problem is still the sameThe
values.yaml
:Below is the
harbor-database-0
log information from loki:And
harbor-notary-server
has the same problem, Below is log info: