search

helm / monocular

⚠️(OBSOLETE) Search and discovery UI for Helm Chart repositories
Apache License 2.0
1.42k stars 220 forks source link

Monocular UI in custtom cluster w/ flannel network and external mongo DB hangs fetching charts #634

Open Shark-y opened 5 years ago

Shark-y commented 5 years ago

Hi,

I installed your SW using your instructions in my own custom cluster using the flannel network with my own mongodb instance runing as a NodePort service

1) All pods install OK 3) Charts SVC connects to mongo DB - OK 2) The sync pod uploads charts to the mongo DB - OK (I can see the docs using Compass) 3) UI installs OK 4) When I access the UI using the node port the paciefier hangs unable to display the charts - INGESS PROBLEM?

Everything seems ok but the ingress looks all messed up. Here is the ingress log:

kubectl --namespace default get ingress nonexistent-robin-monocular NAME HOSTS ADDRESS PORTS AGE nonexistent-robin-monocular * 80 103s larot@kubemaster helm_charts]# kubectl describe ingress nonexistent-robin-monocu Name: nonexistent-robin-monocular Namespace: default Address:
Default backend: default-http-backend:80 () Rules: Host Path Backends

--- HERE ARE THE LOGS FOR ALL PODS ------------------- MONGO DB LOG------------------------------------

[0m [1mWelcome to the Bitnami mongodb container [0mSubscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mongodb [0mSubmit issues and feature requests at https://github.com/bitnami/bitnami-docker-mongodb/issues [0m nami INFO Initializing mongodb mongodb INFO ==> Deploying MongoDB from scratch... mongodb INFO ==> No injected configuration files found. Creating default config files... mongodb INFO ==> Creating root user... mongodb INFO ==> Creating user user... mongodb INFO ==> Enabling authentication... mongodb INFO mongodb INFO ######################################################################## mongodb INFO Installation parameters for mongodb: mongodb INFO Root Password: ** mongodb INFO Username: user mongodb INFO Password: ** mongodb INFO Database: local mongodb INFO (Passwords are not shown for security reasons) mongodb INFO ######################################################################## mongodb INFO nami INFO mongodb successfully initialized INFO  ==> Starting mongodb... INFO  ==> Starting mongod... 2019-06-10T13:44:02.604+0000 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none' 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] MongoDB starting : pid=90 port=27017 dbpath=/opt/bitnami/mongodb/data/db 64-bit host=calico-termite-mongodb-5d6fbfdb44-srnhn 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] db version v4.0.3 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] git version: 7ea530946fa7880364d88c8d8b6026bbc9ffa48c 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.1.0j 20 Nov 2018 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] allocator: tcmalloc 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] modules: none 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] build environment: 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] distmod: debian92 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] distarch: x86_64 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] target_arch: x86_64 2019-06-10T13:44:02.613+0000 I CONTROL [initandlisten] options: { config: "/opt/bitnami/mongodb/conf/mongodb.conf", net: { bindIpAll: true, ipv6: true, port: 27017, unixDomainSocket: { enabled: true, pathPrefix: "/opt/bitnami/mongodb/tmp" } }, processManagement: { fork: false, pidFilePath: "/opt/bitnami/mongodb/tmp/mongodb.pid" }, security: { authorization: "enabled" }, setParameter: { enableLocalhostAuthBypass: "false" }, storage: { dbPath: "/opt/bitnami/mongodb/data/db", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, logRotate: "reopen", path: true, quiet: false, verbosity: 0 } } 2019-06-10T13:44:02.614+0000 I STORAGE [initandlisten] Detected data files in /opt/bitnami/mongodb/data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2019-06-10T13:44:02.614+0000 I STORAGE [initandlisten] 2019-06-10T13:44:02.614+0000 I STORAGE [initandlisten] WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine 2019-06-10T13:44:02.614+0000 I STORAGE [initandlisten] See http://dochub.mongodb.org/core/prodnotes-filesystem 2019-06-10T13:44:02.614+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=407M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress), 2019-06-10T13:44:03.570+0000 I STORAGE [initandlisten] WiredTiger message [1560174243:570574][90:0x7f168c6b09c0], txn-recover: Main recovery loop: starting at 1/28800 2019-06-10T13:44:03.703+0000 I STORAGE [initandlisten] WiredTiger message [1560174243:703400][90:0x7f168c6b09c0], txn-recover: Recovering log 1 through 2 2019-06-10T13:44:03.803+0000 I STORAGE [initandlisten] WiredTiger message [1560174243:803303][90:0x7f168c6b09c0], txn-recover: Recovering log 2 through 2 2019-06-10T13:44:03.919+0000 I STORAGE [initandlisten] WiredTiger message [1560174243:919708][90:0x7f168c6b09c0], txn-recover: Set global recovery timestamp: 0 2019-06-10T13:44:03.944+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0) 2019-06-10T13:44:03.961+0000 I CONTROL [initandlisten] 2019-06-10T13:44:03.961+0000 I CONTROL [initandlisten] WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'. 2019-06-10T13:44:03.961+0000 I CONTROL [initandlisten] We suggest setting it to 'never' 2019-06-10T13:44:03.962+0000 I CONTROL [initandlisten] 2019-06-10T13:44:03.962+0000 I CONTROL [initandlisten] WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'. 2019-06-10T13:44:03.962+0000 I CONTROL [initandlisten] We suggest setting it to 'never' 2019-06-10T13:44:03.962+0000 I CONTROL [initandlisten] 2019-06-10T13:44:03.992+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory '/opt/bitnami/mongodb/data/db/diagnostic.data' 2019-06-10T13:44:03.998+0000 I NETWORK [initandlisten] waiting for connections on port 27017 2019-06-10T13:44:13.091+0000 I NETWORK [listener] connection accepted from 127.0.0.1:49524 #1 (1 connection now open) 2019-06-10T13:44:13.093+0000 I NETWORK [conn1] received client metadata from 127.0.0.1:49524 conn1: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:44:13.102+0000 I NETWORK [conn1] end connection 127.0.0.1:49524 (0 connections now open) 2019-06-10T13:46:18.314+0000 I ACCESS [conn26] Successfully authenticated as principal root on admin 2019-06-10T13:46:18.443+0000 I NETWORK [listener] connection accepted from 10.244.0.0:59683 #27 (2 connections now open) 2019-06-10T13:46:18.464+0000 I ACCESS [conn27] Successfully authenticated as principal root on admin 2019-06-10T13:46:18.481+0000 I NETWORK [listener] connection accepted from 10.244.0.0:59684 #28 (3 connections now open) 2019-06-10T13:46:18.498+0000 I ACCESS [conn28] Successfully authenticated as principal root on admin 2019-06-10T13:46:23.101+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50016 #29 (4 connections now open) 2019-06-10T13:46:23.102+0000 I NETWORK [conn29] received client metadata from 127.0.0.1:50016 conn29: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:46:23.111+0000 I NETWORK [conn29] end connection 127.0.0.1:50016 (3 connections now open) 2019-06-10T13:46:25.516+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50024 #30 (4 connections now open) 2019-06-10T13:46:25.516+0000 I NETWORK [conn30] received client metadata from 127.0.0.1:50024 conn30: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:46:25.524+0000 I NETWORK [conn30] end connection 127.0.0.1:50024 (3 connections now open) 2019-06-10T13:46:29.931+0000 I NETWORK [conn26] end connection 10.244.0.0:59682 (2 connections now open) 2019-06-10T13:46:29.931+0000 I NETWORK [conn27] end connection 10.244.0.0:59683 (1 connection now open) 2019-06-10T13:46:29.931+0000 I NETWORK [conn28] end connection 10.244.0.0:59684 (0 connections now open) 2019-06-10T13:46:33.111+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50054 #31 (1 connection now open) 2019-06-10T13:47:46.761+0000 I NETWORK [conn47] received client metadata from 10.244.0.0:59850 conn47: { driver: { name: "nodejs", version: "3.1.13" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "6.1.7601" }, platform: "Node.js v10.2.0, LE, mongodb-core: 3.1.11" } 2019-06-10T13:47:46.794+0000 I ACCESS [conn47] Successfully authenticated as principal root on admin 2019-06-10T13:47:46.846+0000 I NETWORK [listener] connection accepted from 10.244.0.0:59851 #48 (2 connections now open) 2019-06-10T13:47:46.865+0000 I ACCESS [conn48] Successfully authenticated as principal root on admin 2019-06-10T13:47:46.882+0000 I NETWORK [listener] connection accepted from 10.244.0.0:59852 #49 (3 connections now open) 2019-06-10T13:47:46.897+0000 I ACCESS [conn49] Successfully authenticated as principal root on admin 2019-06-10T13:47:53.107+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50358 #50 (4 connections now open) 2019-06-10T13:47:53.109+0000 I NETWORK [conn50] received client metadata from 127.0.0.1:50358 conn50: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:47:53.119+0000 I NETWORK [conn50] end connection 127.0.0.1:50358 (3 connections now open) 2019-06-10T13:47:55.531+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50368 #51 (4 connections now open) 2019-06-10T13:47:55.532+0000 I NETWORK [conn51] received client metadata from 127.0.0.1:50368 conn51: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:47:55.541+0000 I NETWORK [conn51] end connection 127.0.0.1:50368 (3 connections now open) 2019-06-10T13:47:56.999+0000 I STORAGE [conn48] createCollection: charts.charts with generated UUID: 7daba187-cd67-4927-aa1d-96ddf7c2715b 2019-06-10T13:47:57.092+0000 I NETWORK [listener] connection accepted from 10.244.0.0:59853 #52 (4 connections now open) 2019-06-10T13:47:57.110+0000 I ACCESS [conn52] Successfully authenticated as principal root on admin 2019-06-10T13:48:03.113+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50396 #53 (5 connections now open) 2019-06-10T13:48:03.114+0000 I NETWORK [conn53] received client metadata from 127.0.0.1:50396 conn53: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:48:03.124+0000 I NETWORK [conn53] end connection 127.0.0.1:50396 (4 connections now open) 2019-06-10T13:48:05.524+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50404 #54 (5 connections now open) 2019-06-10T13:48:05.526+0000 I NETWORK [conn54] received client metadata from 127.0.0.1:50404 conn54: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:48:05.534+0000 I NETWORK [conn54] end connection 127.0.0.1:50404 (4 connections now open) 2019-06-10T13:48:13.103+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50434 #55 (5 connections now open) 2019-06-10T13:48:13.103+0000 I NETWORK [conn55] received client metadata from 127.0.0.1:50434 conn55: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:48:13.113+0000 I NETWORK [conn55] end connection 127.0.0.1:50434 (4 connections now open) 2019-06-10T13:48:15.536+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50444 #56 (5 connections now open) 2019-06-10T13:48:15.538+0000 I NETWORK [conn56] received client metadata from 127.0.0.1:50444 conn56: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:48:15.546+0000 I NETWORK [conn56] end connection 127.0.0.1:50444 (4 connections now open) 2019-06-10T13:48:16.772+0000 I NETWORK [conn47] end connection 10.244.0.0:59850 (3 connections now open) 2019-06-10T13:48:16.849+0000 I NETWORK [conn48] end connection 10.244.0.0:59851 (2 connections now open) 2019-06-10T13:48:16.896+0000 I NETWORK [conn49] end connection 10.244.0.0:59852 (1 connection now open) 2019-06-10T13:48:23.096+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50472 #57 (2 connections now open) 2019-06-10T13:48:23.096+0000 I NETWORK [conn57] received client metadata from 127.0.0.1:50472 conn57: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:48:23.103+0000 I NETWORK [conn57] end connection 127.0.0.1:50472 (1 connection now open) 2019-06-10T13:48:25.530+0000 I NETWORK [listener] connection accepted from 127.0.0.1:50482 #58 (2 connections now open) 2019-06-10T13:48:25.530+0000 I NETWORK [conn58] received client metadata from 127.0.0.1:50482 conn58: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.3" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 3.10.0-957.5.1.el7.x86_64" } } 2019-06-10T13:48:25.542+0000 I NETWORK [conn58] end connection 127.0.0.1:50482 (1 connection now open) 2019-06-10T13:48:27.098+0000 I NETWORK [conn52] end connection 10.244.0.0:59853 (0 connections now open) 2019-06-10T13:48:29.028+0000 I NETWORK [listener] connection accepted from 10.244.0.0:60006 #59 (1 connection now open) 2019-06-10T13:48:29.049+0000 I ACCESS [conn59] Successfully authenticated as principal root on admin

------------------------- INGRESS LOG------------------------------------ I0610 13:38:19.443605 6 flags.go:184] Watching for Ingress class: nginx W0610 13:38:19.444024 6 flags.go:213] SSL certificate chain completion is disabled (--enable-ssl-chain-completion=false)

NGINX Ingress controller Release: 0.23.0 Build: git-be1329b22 Repository: https://github.com/kubernetes/ingress-nginx

nginx version: nginx/1.15.9 W0610 13:38:19.548071 6 client_config.go:549] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I0610 13:38:19.548452 6 main.go:200] Creating API client for https://10.96.0.1:443 I0610 13:38:19.567096 6 main.go:244] Running in Kubernetes cluster version v1.14 (v1.14.1) - git (clean) commit b7394102d6ef778017f2ca4046abbaa23b88c290 - platform linux/amd64 I0610 13:38:19.570731 6 main.go:102] Validated default/original-garfish-nginx-ingress-default-backend as the default backend. I0610 13:38:20.012058 6 nginx.go:261] Starting NGINX Ingress controller I0610 13:38:20.024743 6 event.go:221] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"default", Name:"original-garfish-nginx-ingress-controller", UID:"00fe17fd-8b85-11e9-b2ff-080027e164b0", APIVersion:"v1", ResourceVersion:"7627732", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap default/original-garfish-nginx-ingress-controller I0610 13:38:21.217750 6 nginx.go:282] Starting NGINX process I0610 13:38:21.218337 6 leaderelection.go:205] attempting to acquire leader lease default/ingress-controller-leader-nginx... I0610 13:38:21.219787 6 controller.go:172] Configuration changes detected, backend reload required. I0610 13:38:21.223788 6 status.go:148] new leader elected: womping-starfish-nginx-ingress-controller-7ffd798b8d-dtnrt I0610 13:38:21.644750 6 controller.go:190] Backend successfully reloaded. I0610 13:38:21.644837 6 controller.go:200] Initial sync, sleeping for 1 second. [10/Jun/2019:13:38:22 +0000]TCP200000.000 I0610 13:38:56.922941 6 leaderelection.go:214] successfully acquired lease default/ingress-controller-leader-nginx I0610 13:38:56.923202 6 status.go:148] new leader elected: original-garfish-nginx-ingress-controller-67cbd6df84-dnfqw I0610 13:54:09.012166 6 event.go:221] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"default", Name:"nonexistent-robin-monocular", UID:"381ef081-8b87-11e9-b2ff-080027e164b0", APIVersion:"extensions/v1beta1", ResourceVersion:"7629258", FieldPath:""}): type: 'Normal' reason: 'CREATE' Ingress default/nonexistent-robin-monocular W0610 13:54:12.168198 6 controller.go:846] Service "default/nonexistent-robin-monocular-ui" does not have any active Endpoint. W0610 13:54:12.168257 6 controller.go:846] Service "default/nonexistent-robin-monocular-chartsvc" does not have any active Endpoint. I0610 13:54:12.168322 6 controller.go:172] Configuration changes detected, backend reload required. I0610 13:54:12.740574 6 controller.go:190] Backend successfully reloaded. [10/Jun/2019:13:54:12 +0000]TCP200000.000 W0610 13:54:15.492175 6 controller.go:846] Service "default/nonexistent-robin-monocular-ui" does not have any active Endpoint. W0610 13:54:15.492219 6 controller.go:846] Service "default/nonexistent-robin-monocular-chartsvc" does not have any active Endpoint. [10/Jun/2019:13:54:19 +0000]TCP200000.000 W0610 13:54:19.002987 6 controller.go:846] Service "default/nonexistent-robin-monocular-ui" does not have any active Endpoint. I0610 13:54:56.934701 6 status.go:388] updating Ingress default/nonexistent-robin-monocular status from [] to [{ }] W0610 13:54:56.940670 6 controller.go:846] Service "default/nonexistent-robin-monocular-ui" does not have any active Endpoint. I0610 13:54:56.942685 6 event.go:221] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"default", Name:"nonexistent-robin-monocular", UID:"381ef081-8b87-11e9-b2ff-080027e164b0", APIVersion:"extensions/v1beta1", ResourceVersion:"7629382", FieldPath:""}): type: 'Normal' reason: 'UPDATE' Ingress default/nonexistent-robin-monocular [10/Jun/2019:13:55:06 +0000]TCP200000.000 10.244.0.0 - [10.244.0.0] - - [10/Jun/2019:13:56:52 +0000] "GET / HTTP/1.1" 308 171 "-" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0" 361 0.000 [default-nonexistent-robin-monocular-ui-80] - - - - 0b3427b4e2d69b8869e24498b4ee4f4f

--------------------------- CHART SVC LOG ---------------- time="2019-06-10T13:54:10Z" level=info msg="Started chartsvc" addr=":8080" [negroni] 2019-06-10T13:54:18Z | 200 | 177.956µs | 10.244.1.64:8080 | GET /ready [negroni] 2019-06-10T13:54:28Z | 200 | 154.481µs | 10.244.1.64:8080 | GET /ready [negroni] 2019-06-10T13:54:38Z | 200 | 66.451µs | 10.244.1.64:8080 | GET /ready [negroni] 2019-06-10T13:54:48Z | 200 | 76.573µs | 10.244.1.64:8080 | GET /ready [negroni] 2019-06-10T13:54:58Z | 200 | 71.991µs | 10.244.1.64:8080 | GET /ready

------------------------- SYNC LOG --------------------------------------

time="2019-06-10T13:54:12Z" level=info msg="Successfully added the chart repository c1as to database"

prydonius commented 5 years ago

When I access the UI using the node port

What node port are you using to access the UI? It should be the node port of your ingress controller. Can you see if there are any errors in the Network tab of your browser?