-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difficulties getting CGW to run #85
Comments
Hey @ncalad, Let's do the following: Here's the branch: https://github.com/Telecominfraproject/openlan-cgw/tree/feat/all_in_one_make Simply pull the branch and run P.S. this change also means you can drop your zookeeper and kafka that you previously created; |
Few more things:
and
Are safe; We will resolve them in the future; |
We were able to get the cgw container to run. Can we browse to it or perform some other test to see if everything is correct? root@docker-desktop:/# netstat -anp | grep LISTEN |
We noticed a problem with the cert file ... %3|1727202338.058|FAIL|CGW0#consumer-2| [thrd:localhost:9092/bootstrap]: localhost:9092/bootstrap: Connect to ipv6#[::1]:9092 failed: Connection refused (after 59ms in state CONNECT) |
@ncalad could you please post the output you get from running make?
|
Here you go ... |
Are there any certificates at the /home/oguser/OpenLAN/openlan-cgw/utils/cert_generator/certs/server?
Also, few more things: could you please check if your all_in_one_make branch is up to date? I've updated it few times using forcepush, shouldn't affect anything that much, but still; Also, the make should also stop the container, not sure why make failed with that last error; Could you please also post output of the following command please
|
A few minutes ago, we ran the generate_certs script and that directory now contains ... ls /home/oguser/OpenLAN/openlan-cgw/utils/cert_generator/certs/server |
@ncalad please also post output of docker ps command, it seems like either some of the containers are not running or they reside in different networks |
docker ps |
Okay, |
docker inspect docker-broker-1 -f "{{json .NetworkSettings.Networks }}" |
@ncalad First of all, could you please launch the following command:
Just to make sure at least volume got mounted; Also please post you docker / compose version:
Then try to run make stop and then make again to see if that helps; |
docker exec -it openlan_cgw sh -c "ls /etc/cgw/certs" docker --version 2024-09-24T19:43:47Z ERROR ucentral_cgw::cgw_tls] Failed to open TLS private key file: /etc/cgw/certs/key.pem. Error: Permission denied (os error 13) root can't open open key.pem |
Okay, so first note is that we never tried to use this stuff on VM; It shouldn't make any difference, but still, FYI; Second thing is i think restart helped? You can try launching make stop, and changing owner of the files, e.g.
NOTE: you have to launch this from host OS, not container Also, last thing: is this VM you're using - is your HOST OS Windows or Linux? |
@ncalad did you have a chance to look into these steps i've posted? |
We have zookeeper and kafka running but when we try to run the CGW application, the container terminates and the logs show ...
./run_cgw.sh openlan-cgw-img:3d46cc3 ucentral-cgw-container
docker logs 010d7e028b78
[2024-09-23T22:08:40Z INFO ucentral_cgw] Starting CGW application, rev tag:
[2024-09-23T22:08:40Z INFO ucentral_cgw] (1048576, 1048576)
[2024-09-23T22:08:40Z INFO ucentral_cgw] (1048576, 1048576)
%3|1727129320.768|FAIL|rdkafka#producer-1| [thrd:localhost:9092/bootstrap]: localhost:9092/bootstrap: Connect to ipv6#[::1]:9092 failed: Connection refused (after 0ms in state CONNECT)
[2024-09-23T22:08:40Z ERROR ucentral_cgw::cgw_remote_discovery] Can't create CGW Remote Discovery client: Redis client create failed (Connection(ConnectionFailed))
[2024-09-23T22:08:40Z ERROR ucentral_cgw::cgw_connection_server] Can't create CGW Connection server: Remote Discovery create failed: RemoteDiscovery("Redis client create failed")
thread 'main' panicked at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.38.0/src/runtime/blocking/shutdown.rs:51:21:
Cannot drop a runtime in a context where blocking is not allowed. This happens when a runtime is dropped from within an asynchronous context.
note: run with
RUST_BACKTRACE=1
environment variable to display a backtraceThe text was updated successfully, but these errors were encountered: