Issue:
Just the other day, I’ve attempted to run a ‘helm upgrade…’ command on my NextCloud application. I’ve taken care to ensure that the container’s version matches that of the persistent storage’s marking (e.g. image.tag=22.1-fpm) as a variance in that would cause NextCloud not to start. However, there’s another issue that has puzzled me: a 502 Error upon navigating to the URL of the application.
Resolution:
– Check the logs
– Review Kubernetes Ingress documentation
– Realize that this specific issue requires no fixing
Checking the logs:
01 02 03 04 05 06 07 08 09 10 11 12 13 | admin@controller:~$ k logs nextcloud-67855fc94c-lc2xr nextcloud-nginx/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d//docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh/docker-entrypoint.sh: Configuration complete; ready for start up2021/11/01 04:18:37 [error] 34#34: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.16.90.192, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "dragoncoin.com"... Truncated for brevity ...2021/11/01 04:34:20 [error] 34#34: *155 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.100.95, server: , request: "GET /apps/photos/service-worker.js HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "dragoncoin.com", referrer: "https://dragoncoin.com/apps/photos/service-worker.js"172.16.100.95 - - [01/Nov/2021:04:34:20 +0000] "GET /apps/photos/service-worker.js HTTP/1.1" 502 559 "https://dragoncoin.com/apps/photos/service-worker.js" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36" "172.16.100.164" |
001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 | admin@controller:~$ k logs nextcloud-67855fc94c-lc2xr nextcloudInitializing nextcloud 22.1.1.2 ...Upgrading nextcloud from 22.1.0.1 ...Initializing finishedNextcloud or one of the apps require upgrade - only a limited number of commands are availableYou may use your browser or the occ upgrade command to do the upgradeSetting log level to debugTurned on maintenance modeUpdating database schemaUpdated databaseUpdating <workflowengine> ...Updated <workflowengine> to 2.3.1Checking for update of app accessibility in appstoreChecked for update of app "accessibility" in App StoreChecking for update of app activity in appstoreChecked for update of app "activity" in App StoreChecking for update of app audioplayer in appstoreUpdate app audioplayer from App StoreChecked for update of app "audioplayer" in App StoreChecking for update of app breezedark in appstoreUpdate app breezedark from App StoreChecked for update of app "breezedark" in App StoreChecking for update of app bruteforcesettings in appstoreChecked for update of app "bruteforcesettings" in App StoreChecking for update of app camerarawpreviews in appstoreChecked for update of app "camerarawpreviews" in App StoreChecking for update of app cloud_federation_api in appstoreChecked for update of app "cloud_federation_api" in App StoreChecking for update of app cms_pico in appstoreUpdate app cms_pico from App StoreRepair warning: Replacing Pico CMS config file "config.yml.template"Repair warning: Replacing Pico CMS system template "empty"Repair warning: Replacing Pico CMS system template "sample_pico"Repair warning: Replacing Pico CMS system theme "default"Repair warning: Replacing Pico CMS system plugin "PicoDeprecated"Checked for update of app "cms_pico" in App StoreChecking for update of app contactsinteraction in appstoreChecked for update of app "contactsinteraction" in App StoreChecking for update of app dav in appstoreChecked for update of app "dav" in App StoreChecking for update of app documentserver_community in appstoreChecked for update of app "documentserver_community" in App StoreChecking for update of app drawio in appstoreChecked for update of app "drawio" in App StoreChecking for update of app external in appstoreChecked for update of app "external" in App StoreChecking for update of app federatedfilesharing in appstoreChecked for update of app "federatedfilesharing" in App StoreChecking for update of app files in appstoreChecked for update of app "files" in App StoreChecking for update of app files_antivirus in appstoreUpdate app files_antivirus from App StoreChecked for update of app "files_antivirus" in App StoreChecking for update of app files_markdown in appstoreChecked for update of app "files_markdown" in App StoreChecking for update of app files_mindmap in appstoreChecked for update of app "files_mindmap" in App StoreChecking for update of app files_pdfviewer in appstoreChecked for update of app "files_pdfviewer" in App StoreChecking for update of app files_rightclick in appstoreChecked for update of app "files_rightclick" in App StoreChecking for update of app files_sharing in appstoreChecked for update of app "files_sharing" in App StoreChecking for update of app files_trashbin in appstoreChecked for update of app "files_trashbin" in App StoreChecking for update of app files_versions in appstoreChecked for update of app "files_versions" in App StoreChecking for update of app files_videoplayer in appstoreChecked for update of app "files_videoplayer" in App StoreChecking for update of app forms in appstoreChecked for update of app "forms" in App StoreChecking for update of app logreader in appstoreChecked for update of app "logreader" in App StoreChecking for update of app lookup_server_connector in appstoreChecked for update of app "lookup_server_connector" in App StoreChecking for update of app maps in appstoreChecked for update of app "maps" in App StoreChecking for update of app music in appstoreUpdate app music from App StoreChecked for update of app "music" in App StoreChecking for update of app news in appstoreUpdate app news from App StoreChecked for update of app "news" in App StoreChecking for update of app notifications in appstoreChecked for update of app "notifications" in App StoreChecking for update of app oauth2 in appstoreChecked for update of app "oauth2" in App StoreChecking for update of app password_policy in appstoreChecked for update of app "password_policy" in App StoreChecking for update of app photos in appstoreChecked for update of app "photos" in App StoreChecking for update of app privacy in appstoreChecked for update of app "privacy" in App StoreChecking for update of app provisioning_api in appstoreChecked for update of app "provisioning_api" in App StoreChecking for update of app quicknotes in appstoreChecked for update of app "quicknotes" in App StoreChecking for update of app recommendations in appstoreChecked for update of app "recommendations" in App StoreChecking for update of app registration in appstoreChecked for update of app "registration" in App StoreChecking for update of app richdocuments in appstoreUpdate app richdocuments from App StoreChecked for update of app "richdocuments" in App StoreChecking for update of app serverinfo in appstoreChecked for update of app "serverinfo" in App StoreChecking for update of app settings in appstoreChecked for update of app "settings" in App StoreChecking for update of app sharebymail in appstoreChecked for update of app "sharebymail" in App StoreChecking for update of app spreed in appstoreUpdate app spreed from App StoreChecked for update of app "spreed" in App StoreChecking for update of app support in appstoreChecked for update of app "support" in App StoreChecking for update of app survey_client in appstoreChecked for update of app "survey_client" in App StoreChecking for update of app systemtags in appstoreChecked for update of app "systemtags" in App StoreChecking for update of app tasks in appstoreChecked for update of app "tasks" in App StoreChecking for update of app text in appstoreChecked for update of app "text" in App StoreChecking for update of app theming in appstoreChecked for update of app "theming" in App StoreChecking for update of app twofactor_backupcodes in appstoreChecked for update of app "twofactor_backupcodes" in App StoreChecking for update of app updatenotification in appstoreChecked for update of app "updatenotification" in App StoreChecking for update of app user_status in appstoreChecked for update of app "user_status" in App StoreChecking for update of app video_converter in appstoreUpdate app video_converter from App StoreChecked for update of app "video_converter" in App StoreChecking for update of app viewer in appstoreChecked for update of app "viewer" in App StoreChecking for update of app weather_status in appstoreChecked for update of app "weather_status" in App StoreChecking for update of app workflowengine in appstoreChecked for update of app "workflowengine" in App StoreStarting code integrity check... |
Reviewing Documentation:
According to the kubernetes ingress requirements (https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/cluster-loadbalancing/glbc#prerequisites) the application must return a 200 status code at ‘/’. It’s a known behavior that when an application is not in a ‘ready’ state, it would return a 302 (redirect to login). If health checks are configured to run, failing results would cause the ingress resource returns 502. Even if health checks are skipped, the container would that are still in a ‘starting code integrity check…’ state would still relay non-200 statuses, which leads to Ingress to return 502 to the users.
Categories: