search

european-dynamics-rnd / OneNet

8 stars 1 forks source link

Data App connection error. Install or configure it properly #13

Closed cvidalomie closed 1 year ago

cvidalomie commented 1 year ago

We are having this issue since the last update. image Everything seems to be installed propertly and running. image image And everything is running on the docker too: image

Have anyone else experienced something similar?

HeliasEurodyn commented 1 year ago

Hello cvidalomie.

Login again on the "Connector Settings"

  1. Use your local User Interface which is the "onenet-ui container" so it should be accesible through the 30003 port. In stead of the https://onenet-ngsi-ld.eurodyn.com The url should be like http://your_ip_where_the_containers_are:30003 (You can even see it on the docker picture that you send on the previous post, it is the last container shown)

  2. On the "Connector Settings" switch the "Local Api Url" From http://localhost:30001/api To http://your_ip_where_the_containers_are:30001 (You can even see it on the docker picture that you send on the previous post, it is the 10th container shown)

  3. Save the "Connector Settings", Refersh the Page. Click the "Check Connection" and "Url" bottons.

It is pretty straight forward so it must work fine, but in case you face any issues please let us know.
Best Regards , Helias.

cvidalomie commented 1 year ago

Hello Helias,

  1. When trying to connect through http://194.224.33.29:30003 or http://onenet-prb.omie.es:30003 we get this: image image
  2. We switch the 'Local Api Url' in our user on https://onenet-ngsi-ld.eurodyn.com/ image

And now we have this issue with the mongo-db container: 2023-03-15 09:34:27 2023-03-15T08:34:27.252+0000 I CONTROL  [initandlisten] db version v3.6.23 2023-03-15 09:34:27 2023-03-15T08:34:27.266+0000 I CONTROL  [initandlisten] git version: d352e6a4764659e0d0350ce77279de3c1f243e5c 2023-03-15 09:34:27 2023-03-15T08:34:27.269+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016 2023-03-15 09:34:27 2023-03-15T08:34:27.272+0000 I CONTROL  [initandlisten] allocator: tcmalloc 2023-03-15 09:34:27 2023-03-15T08:34:27.280+0000 I CONTROL  [initandlisten] modules: none 2023-03-15 09:34:27 2023-03-15T08:34:27.280+0000 I CONTROL  [initandlisten] build environment: 2023-03-15 09:34:27 2023-03-15T08:34:27.280+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604 2023-03-15 09:34:27 2023-03-15T08:34:27.280+0000 I CONTROL  [initandlisten]     distarch: x86_64 2023-03-15 09:34:27 2023-03-15T08:34:27.280+0000 I CONTROL  [initandlisten]     target_arch: x86_64 2023-03-15 09:34:27 2023-03-15T08:34:27.280+0000 I CONTROL  [initandlisten] options: { net: { bindIpAll: true }, security: { authorization: "enabled" }, storage: { journal: { enabled: false } } } 2023-03-15 09:34:27 2023-03-15T08:34:27.331+0000 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2023-03-15 09:34:27 2023-03-15T08:34:27.410+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=464M,cache_overflow=(file_max=0M),session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),compatibility=(release="3.0",require_max="3.0"),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),,log=(enabled=false), 2023-03-15 09:34:30 2023-03-15T08:34:30.188+0000 E STORAGE  [initandlisten] WiredTiger error (1) [1678869270:188843][1:0x7f1be589ea40], file:WiredTiger.wt, connection: posix_open_file, 715: /data/db/WiredTiger.wt: handle-open: open: Operation not permitted Raw: [1678869270:188843][1:0x7f1be589ea40], file:WiredTiger.wt, connection: posix_open_file, 715: /data/db/WiredTiger.wt: handle-open: open: Operation not permitted 2023-03-15 09:34:30 2023-03-15T08:34:30.190+0000 E -        [initandlisten] Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 488 2023-03-15 09:34:30 2023-03-15T08:34:30.211+0000 I STORAGE  [initandlisten] exception in initAndListen: Location28595: 1: Operation not permitted, terminating 2023-03-15 09:34:30 2023-03-15T08:34:30.212+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets... 2023-03-15 09:34:30 2023-03-15T08:34:30.212+0000 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock 2023-03-15 09:34:30 2023-03-15T08:34:30.212+0000 I CONTROL  [initandlisten] now exiting 2023-03-15 09:34:30 2023-03-15T08:34:30.213+0000 I CONTROL  [initandlisten] shutting down with code:100

cvidalomie commented 1 year ago

UPDATE: mongo-db container is now running after restarting the services but now we see this: image We are not connected to hub but he icon of the docker indicates that is running

cvidalomie commented 1 year ago

NEW UPDATE: The db-mongo container continues to shut down after a while. Not able to get it up. Same error than before.