{"id":136,"date":"2024-10-22T02:28:00","date_gmt":"2024-10-22T02:28:00","guid":{"rendered":"https:\/\/pickledvm.ovh\/?p=136"},"modified":"2025-01-11T01:34:25","modified_gmt":"2025-01-11T01:34:25","slug":"harbor-rozwiazywanie-problemow-troubleshooting","status":"publish","type":"post","link":"https:\/\/pickledvm.ovh\/?p=136","title":{"rendered":"Harbor – rozwi\u0105zywanie problem\u00f3w (troubleshooting)"},"content":{"rendered":"\n

<\/h3>\n\n\n\n

W poni\u017cszym artykule postaram si\u0119 w kilku s\u0142owach napisa\u0107 jak i gdzie szuka\u0107 przyczyn \u017ale lub niepoprawnie dzia\u0142aj\u0105cej naszej aplikacji Harbor.<\/p>\n\n\n\n

Dost\u0119p do log\u00f3w Harbor<\/h3>\n\n\n\n

<\/p>\n\n\n\n

Domy\u015blnie dane rejestru ka\u017cdego Harbnor’a s\u0105 przechowywane w katalogu \/data\/<\/code> na ho\u015bcie . Wa\u017cne jest to, \u017ce dane te pozostaj\u0105 niezmienione, nawet gdy kontenery Harbor zostan\u0105 usuni\u0119te i\/lub odtworzone. Oczywi\u015bcie mo\u017cna zmieni\u0107 t\u0119 lokalizacj\u0119, edytuj\u0105c warto\u015b\u0107 data_volume<\/code> w pliku harbor.yml<\/code>.<\/p>\n\n\n\n

Dodatkowo Harbor u\u017cywa narz\u0119dzia rsyslog<\/code> do zbierania log\u00f3w z ka\u017cdego kontenera. Domy\u015blnie pliki log\u00f3w s\u0105 przechowywane w katalogu \/var\/log\/harbor\/<\/code> na docelowym ho\u015bcie na potrzeby ewentualnie szukania przyczyn problemu naszej aplikacji. Oczywi\u015bcie i wtym przypadku mo\u017cna zmieni\u0107 lokalizacj\u0119 katalogu log\u00f3w, edytuj\u0105c odpowiedni\u0105 opcj\u0119 w pliku harbor.yml<\/code>.<\/p>\n\n\n\n

\n\n\n\n

Harbor nie uruchamia si\u0119 lub dzia\u0142a nieprawid\u0142owo<\/h3>\n\n\n\n

Je\u015bli Harbor nie uruchamia si\u0119 lub dzia\u0142a nieprawid\u0142owo.
Co mo\u017cemy w takiej sytuacji zarobi\u0107. Nale\u017cy wykona\u0107 nast\u0119puj\u0105ce polecenie, w celu sprawdzania, czy wszystkie kontenery Harbor s\u0105 porwanie uruchomione i wy\u015bwietla si\u0119 stani “Up”.<\/p>\n\n\n\n

bashSkopiuj kodsudo docker compose ps\n<\/code><\/pre>\n\n\n\n
Przyk\u0142ad wyniku naszego polecenia:<\/p>\n\n\n\n
Je\u015bli jaki\u015b kontener nie znajduje si\u0119 w stanie “Up”, sprawd\u017a odpowiedni plik logu tego kontenera w katalogu \/var\/log\/harbor<\/code>. Na przyk\u0142ad, je\u015bli kontener harbor-core<\/code> nie dzia\u0142a, sprawd\u017a plik core.log<\/code>.<\/p>\n\n\n\n
\n\n\n\n
<\/p>\n\n\n\n
root@HARBORPOC01:~\/harbor# \/usr\/libexec\/docker\/cli-plugins\/docker-compose ps
NAME                IMAGE                                   COMMAND                  SERVICE         CREATED        STATUS                  PORTS
harbor-core         goharbor\/harbor-core:v2.10.2            \"\/harbor\/entrypoint.\u2026\"   core            3 months ago   Up 3 months (healthy)
harbor-jobservice   goharbor\/harbor-jobservice:v2.10.2      \"\/harbor\/entrypoint.\u2026\"   jobservice      3 months ago   Up 3 months (healthy)
harbor-log          goharbor\/harbor-log:v2.10.2             \"\/bin\/sh -c \/usr\/loc\u2026\"   log             3 months ago   Up 3 months (healthy)   127.0.0.1:1514->10514\/tcp
harbor-portal       goharbor\/harbor-portal:v2.10.2          \"nginx -g 'daemon of\u2026\"   portal          3 months ago   Up 3 months (healthy)
nginx               goharbor\/nginx-photon:v2.10.2           \"nginx -g 'daemon of\u2026\"   proxy           3 months ago   Up 3 months (healthy)   0.0.0.0:80->8080\/tcp, 0.0.0.0:443->8443\/tcp
redis               goharbor\/redis-photon:v2.10.2           \"redis-server \/etc\/r\u2026\"   redis           3 months ago   Up 3 months (healthy)
registry            goharbor\/registry-photon:v2.10.2        \"\/home\/harbor\/entryp\u2026\"   registry        3 months ago   Up 3 months (healthy)
registryctl         goharbor\/harbor-registryctl:v2.10.2     \"\/home\/harbor\/start.\u2026\"   registryctl     3 months ago   Up 3 months (healthy)
trivy-adapter       goharbor\/trivy-adapter-photon:v2.10.2   \"\/home\/scanner\/entry\u2026\"   trivy-adapter   3 months ago   Up 3 months (healthy)
root@HARBORPOC01:~\/harbor#
<\/code>
<\/code><\/pre>\n\n\n\n
\n\n\n\n
Przegl\u0105dnie log\u00f3w.<\/h3>\n\n\n\n
Je\u015bli kt\u00f3ry\u015b z naszych ma tatus “UP” nasz Harbor nie dzia\u0142a poprawnie nale\u017cy  przej\u015b\u0107 do katalogu z logami i przyjrze\u0107 si\u0119 dog\u0142\u0119bniej, co jest przyczyna zaistnia\u0142ej sytuacji przegl\u0105daj\u0105 ka\u017cdy z log\u00f3w.
<\/p>\n\n\n\n
root@HARBORPOC:01~\/harbor# ls \/var\/log\/harbor\/ -l
total 759416
-rw-r–r– 1 10000 10000 21693623 Jan 11 02:00 core.log
-rw-r–r– 1 10000 10000 7612770 Aug 25 12:01 core.log.1.gz
-rw-r–r– 1 10000 10000 106880832 Jan 11 02:00 jobservice.log
-rw-r–r– 1 10000 10000 5593170 Aug 15 08:00 jobservice.log.1.gz
-rw-r–r– 1 10000 10000 170192668 Jan 11 02:24 portal.log
-rw-r–r– 1 10000 10000 9354051 Sep 20 23:00 portal.log.1.gz
-rw-r–r– 1 10000 10000 97019253 Jan 11 02:24 proxy.log
-rw-r–r– 1 10000 10000 35381855 Jan 11 02:23 redis.log
-rw-r–r– 1 10000 10000 129276075 Jan 11 02:24 registryctl.log
-rw-r–r– 1 10000 10000 9627117 Oct 10 22:00 registryctl.log.1.gz
-rw-r–r– 1 10000 10000 175127441 Jan 11 02:24 registry.log
-rw-r–r– 1 10000 10000 9814850 Sep 17 02:00 registry.log.1.gz
-rw-r–r– 1 10000 10000 14371 Sep 19 00:37 trivy-adapter.log
root@HARBORPOC:01~\/harbor# <\/p>\n","protected":false},"excerpt":{"rendered":"
W poni\u017cszym artykule postaram si\u0119 w kilku s\u0142owach napisa\u0107 jak i gdzie szuka\u0107 przyczyn \u017ale lub niepoprawnie dzia\u0142aj\u0105cej naszej aplikacji Harbor. Dost\u0119p do log\u00f3w Harbor Domy\u015blnie dane rejestru ka\u017cdego Harbnor’a s\u0105 przechowywane w katalogu \/data\/ na ho\u015bcie . Wa\u017cne jest to, \u017ce dane te pozostaj\u0105 niezmienione, nawet gdy kontenery Harbor zostan\u0105 usuni\u0119te i\/lub odtworzone. Oczywi\u015bcie […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-136","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=\/wp\/v2\/posts\/136","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=136"}],"version-history":[{"count":6,"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=\/wp\/v2\/posts\/136\/revisions"}],"predecessor-version":[{"id":144,"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=\/wp\/v2\/posts\/136\/revisions\/144"}],"wp:attachment":[{"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=136"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=136"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pickledvm.ovh\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=136"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}