You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm upgrading from 0d35a4763e4bb0df0721a5495f6e58bf412f92ee (0.21.5) to 0d35a4763e4bb0df0721a5495f6e58bf412f92ee (0.21.8). On the latest version, it appears TLS is not supported, and I'm getting the following logs:
$ nanomq start
Config file is not specified, use default config file: /etc/nanomq.conf
2024-04-18 18:49:54 [1105] FATAL /usr/src/debug/nanomq/0.21.8-r0/git/nanomq/apps/broker.c:1122 broker: nng_listener_create tls
nng_listener_create tls: Not supported
Expected behavior
I'm able to start the nanomq server while hosting only an SSL listener.
Actual Behavior
I encounter a fatal error.
To Reproduce
Compile nanoMQ for 0.21.8 with -DNNG_ENABLE_TLS=ON -DNNG_ENABLE_SQLITE=ON -DCMAKE_BUILD_TYPE=Debug.
Whoops, perhaps there is sth wrong with CMake configuration of mebdtls after Garrett made some changes on NNG.
Will look into it now.
BTW, I see you are using Yocto, is nanomq working fine on yocto? I am at EOSS of seattle now, people asking about the compatibility, I assumed it is fine.
Describe the bug
I'm upgrading from
0d35a4763e4bb0df0721a5495f6e58bf412f92ee
(0.21.5) to0d35a4763e4bb0df0721a5495f6e58bf412f92ee
(0.21.8). On the latest version, it appears TLS is not supported, and I'm getting the following logs:Expected behavior
I'm able to start the nanomq server while hosting only an SSL listener.
Actual Behavior
I encounter a fatal error.
To Reproduce
Compile nanoMQ for
0.21.8
with-DNNG_ENABLE_TLS=ON -DNNG_ENABLE_SQLITE=ON -DCMAKE_BUILD_TYPE=Debug
.Run NanoMQ with the following in
/etc/nanomq.conf
Environment Details
Linux aarch64
- custom with linux kernel of5.15.120-yocto-standard
OECMake
Client SDK
N/A
Additional context
This also fails with the default config, when uncommenting the
ssl
section, and I'm seeing the same error in pre-release0.21.9
The text was updated successfully, but these errors were encountered: