search

OpenVisualCloud / Smart-City-Sample

The smart city reference pipeline shows how to integrate various media building blocks, with analytics powered by the OpenVINO™ Toolkit, for traffic or stadium sensing, analytics and management tasks.
BSD 3-Clause "New" or "Revised" License
198 stars 86 forks source link

Cannot see any office/cameras on Web UI after setup with openness20.06 #576

Closed lvcarry closed 4 years ago

lvcarry commented 4 years ago

I deploy SMTC based on openness20.06 with CIR build. I can get all pods running status without error. But there are no any cameras/offices shown in webui. openness version: https://github.com/open-ness/openness-experience-kits/tree/d12eda43b93b6789f8bdfb23d85c45569227cd28 SMTC branch: openness-k8s Cluster environment: openness controller: 10.166.30.126, cloud master: 10.166.30.50 Logs:

[root@av09-09-wp ~]# kubectl get pods NAME READY STATUS RESTARTS AGE traffic-office1-alert-c7759b46-2k8rr 1/1 Running 0 3m46s traffic-office1-analytics-traffic-78646d66d-5rnw7 1/1 Running 0 3m46s traffic-office1-analytics-traffic-78646d66d-xwm26 1/1 Running 0 3m46s traffic-office1-camera-discovery-86f669d8cf-z22ct 1/1 Running 0 3m46s traffic-office1-db-7d85f6c8b4-xxrbk 1/1 Running 0 3m45s traffic-office1-db-init-mqbld 1/1 Running 0 3m45s traffic-office1-mqtt-799c64c7b8-6xc8v 1/1 Running 0 3m45s traffic-office1-mqtt2db-ffbcdf95c-kpq4h 1/1 Running 1 3m45s traffic-office1-relay-c9f985fc-lz8qj 1/1 Running 0 3m44s traffic-office1-smart-upload-64599744c6-xwspj 1/1 Running 0 3m43s traffic-office1-storage-68578c78d9-9dwbr 1/1 Running 0 3m44s traffic-office1-where-indexing-6fb84d489d-dqklm 1/1 Running 0 3m43s traffic-office2-alert-64b54d44dd-4xmdh 1/1 Running 0 3m46s traffic-office2-analytics-traffic-67d79b49f8-9v9zt 1/1 Running 0 3m46s traffic-office2-analytics-traffic-67d79b49f8-bdf7f 1/1 Running 0 3m46s traffic-office2-camera-discovery-578bfb7dd9-kfpt6 1/1 Running 0 3m45s traffic-office2-db-db6598bd9-bvrhm 1/1 Running 0 3m44s traffic-office2-db-init-hd2mk 1/1 Running 0 3m45s traffic-office2-mqtt-6cdc85699d-vtx44 1/1 Running 0 3m45s traffic-office2-mqtt2db-ccc75b8c8-ffw4f 1/1 Running 1 3m45s traffic-office2-relay-59bfd84796-hgvqc 1/1 Running 1 3m43s traffic-office2-smart-upload-778676d7cc-8t24h 1/1 Running 0 3m43s traffic-office2-storage-8447fb8d58-74rpx 1/1 Running 0 3m44s traffic-office2-where-indexing-6d8468f494-ss5bb 1/1 Running 0 3m43s

[root@av09-09-wp ~]# kubectl logs traffic-office1-db-7d85f6c8b4-xxrbk ........ [2020-08-12T08:10:02,762][INFO ][o.e.t.TransportService ] [traffic-office1] publish_address {10.166.30.50:30301}, bound_addresses {0.0.0.0:9300} [2020-08-12T08:10:02,770][INFO ][o.e.b.BootstrapChecks ] [traffic-office1] bound or publishing to a non-loopback address, enforcing bootstrap checks [2020-08-12T08:10:32,785][WARN ][o.e.n.Node ] [traffic-office1] timed out while waiting for initial discovery state - timeout: 30s [2020-08-12T08:10:32,793][INFO ][o.e.h.n.Netty4HttpServerTransport] [traffic-office1] publish_address {10.16.0.47:9200}, bound_addresses {0.0.0.0:9200} [2020-08-12T08:10:32,793][INFO ][o.e.n.Node ] [traffic-office1] started [2020-08-12T08:10:36,105][INFO ][o.e.d.z.ZenDiscovery ] [traffic-office1] failed to send join request to master [{cloud-db}{q5Kru1cDS4KTx52i0gib3g}{eRn_HSzUSfWh_sLshr3tgg}{10.166.30.50}{10.166.30.50:30300}{zone=cloud}], reason [RemoteTransportException[[cloud-db][10.244.1.22:30300][internal:discovery/zen/join]]; nested: ConnectTransportException[[traffic-office1][10.166.30.50:30301] handshake_timeout[30s]]; ]

lvcarry commented 4 years ago

image-20200804165727472

xwu2git commented 4 years ago

Is this issue still valid?

lvcarry commented 4 years ago

sorry, this issue cannot be reproduced now. Will close this.