emqtt:quic_connect/1 does not work with Erlang/OTP 27 on Debian 12 #14474

SaveMe0 · 2024-12-27T09:32:44Z

SaveMe0
Dec 27, 2024

I have cloned emqtt with quic over mqtt and successfully built it on my:

Debian GNU/Linux 12 (bookworm) server 
hosting Erlang/OTP 27 [erts-15.1.2] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-threads:1]

Yet when I run I run the emqtt:quic_connect/1 function it kills the emqtt process I started with emqtt:start_link/1.

Here is what I would like to know:

has emqtt been tested on
Erlang/OTP 27 [erts-15.1.2] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-threads:1]
Do I have any missing dependencies in rebar.conf file for a rebar3 project I created

   {erl_opts, [debug_info]}.
   {deps, [{emqtt, {git, "https://github.com/emqx/emqtt.git", {branch, "master"}}}]}.

   {shell, [
    %% {config, "config/sys.config"},
    {apps, [testapp]}
   ]}.

You can examine how I am using these functions according the
#14452
com3.erl module below.

-module(com3).
-behaviour(gen_statem).
-define(NAME, com3).

-export([start/0]).
-export([sub/0]).
-export([subState/3]).

-export([init/1,callback_mode/0, handle_event/3, terminate/3, code_change/4]).

start() ->
    gen_statem:start_link({local,?NAME}, ?MODULE, [], []).

sub() ->
    gen_statem:call(?NAME, sub).

-record(comm, {connPid, emqttMsg}).

callback_mode() ->
    [state_functions,state_enter].

init(_Args) ->
    State = subState, Data = #comm{connPid = 0},
    {ok, State, Data}.

subState({call, From}, sub, Data) ->
Properties = #{'Session-Expiry-Interval' => 300,
                    'Server-Keep-Alive' => 30,
                    'Retain-Available' => 1
                },

    Options = [ {host, '192.168.178.33'},
                {port, 14567},
                {keepalive, 30},
                %{clientid, <<"alb65McbrideBCCanada">>}, 
                {proto_ver, v5},
                {reconnect_timeout, 1000},
                %{quic_opts, {quicer:conn_opts(), quicer:stream_opts()}},
                {properties, Properties}
            ],

    {ok, ConnPid} = emqtt:start_link(Options),
    emqtt:quic_connect(ConnPid),

    Properties2 = #{ 'Maximum-Packet-Size' => 1048576,
                    'Receive-Maximum' => 32,
                    'Retain-Available' => 1,
                    'Shared-Subscription-Available' => 1,
                    'Subscription-Identifier-Available' => 1,
                    'Topic-Alias-Maximum' => 65535,
                    'Wildcard-Subscription-Available' => 1,
                    'Payload-Format-Indicator' => 1,
                    'Message-Expiry-Interval' => 10,
                    'Content-Type' => <<"Json">>,
                    'Server-Keep-Alive' => 30,
                    'Maximum-QoS' => 1 },

    SubOpts = [{qos, 1}],
    Subscriptions = [{<<"EK9160/EK-98EFB6/Stream1/Json/Tx/Data">>, SubOpts}],
    _ = emqtt:subscribe(ConnPid, Properties2, Subscriptions),
    {keep_state, Data, [{reply, From, Data}]};

subState(EventType, EventContent, Data) ->
    handle_event(EventType, EventContent, Data). 

handle_event(_, _, Data) ->
    %% Ignore all other events
    {keep_state, Data}.

terminate(_Reason, _State, _Data) ->
    ok.

code_change(_Vsn, State, Data, _Extra) ->
    {ok, State, Data}.

SaveMe0 · 2025-01-02T22:32:24Z

SaveMe0
Jan 2, 2025
Author

To ensure that quic over mqtt works on Debian 12 may, I tested nanomq to find that operating system is not a problem.

alberto@debian:~$ nanomq start --url nmq-tcp://192.168.178.33:14567 --conf /nanomq/etc/nanomq.conf
2025-01-02 23:25:36 [29555] ERROR /home/alberto/nanomq/nng/src/supplemental/nanolib/conf_ver2.c:1977 conf_parse_ver2: Configure file [/nanomq/etc/nanomq.conf] or [/etc/nanomq.conf] not found or unreadable
NanoMQ Broker is started successfully!

alberto@debian:~$ nanomq_cli sub -h "192.168.178.33" -p 14567 -t "EK9160/EK-98EFB6/Stream1/Json/Tx/Data" -q 1  --quic true --payload-format-indicator --content-type application/json –session-expiry-interval 300
quic_connect_cb: mqtt-quic://192.168.178.33:14567 connect
EK9160/EK-98EFB6/Stream1/Json/Tx/Data: {"Timestamp":"2025-01-02T22:22:32.193Z","Values":{"Slave 1 (EL1008).Channel 1.Input":true,"Slave 1 (EL1008).Channel 2.Input":false},"MetaData":{}}
EK9160/EK-98EFB6/Stream1/Json/Tx/Data: {"Timestamp":"2025-01-02T22:22:33.193Z","Values":{"Slave 1 (EL1008).Channel 1.Input":true,"Slave 1 (EL1008).Channel 2.Input":false},"MetaData":{}}
EK9160/EK-98EFB6/Stream1/Json/Tx/Data: {"Timestamp":"2025-01-02T22:22:34.193Z","Values":{"Slave 1 (EL1008).Channel 1.Input":true,"Slave 1 (EL1008).Channel 2.Input":false},"MetaData":{}}

0 replies

SaveMe0 · 2025-01-02T22:56:45Z

SaveMe0
Jan 2, 2025
Author

And to ensure my emqx.conf file is configure correctly as shown below

alberto@debian:/etc/emqx$ cat emqx.conf
## NOTE:
## This config file overrides data/configs/cluster.hocon,
## and is merged with environment variables which start with 'EMQX_' prefix.
##
## Config changes made from EMQX dashboard UI, management HTTP API, or CLI
## are stored in data/configs/cluster.hocon.
## To avoid confusion, please do not store the same configs in both files.
##
## See https://www.emqx.io/docs/en/latest/configuration/configuration.html for more details.
## Configuration full example can be found in etc/examples

node {
  name = "emqx@127.0.0.1"
  cookie = "emqxsecretcookie"
  data_dir = "/var/lib/emqx"
}

cluster {
  name = emqxcl
  discovery_strategy = manual
}

## EMQX provides support for two primary log handlers: `file` and `console`, with an additional `audit` handler specifically designed to always direct logs to files.
## The system's default log handling behavior can be configured via the environment variable `EMQX_DEFAULT_LOG_HANDLER`, which accepts the following settings:
##
##   - `file`: Directs log output exclusively to files.
##   - `console`: Channels log output solely to the console.
##
## It's noteworthy that `EMQX_DEFAULT_LOG_HANDLER` is set to `file` when EMQX is initiated via systemd `emqx.service` file.
## In scenarios outside systemd initiation, `console` serves as the default log handler.

## Read more about configs here: https://www.emqx.io/docs/en/latest/configuration/logs.html

log {
    # file {
    #     level = warning
    # }
    # console {
    #     level = warning
    # }
}
dashboard {
    listeners {
        http {
            ## Comment out 'bind' (or set bind=0) to disable listener.
            bind = 18083
        }
        https {
            ## Uncomment to enable
            # bind = 18084
            ssl_options {
                certfile = "${EMQX_ETC_DIR}/certs/cert.pem"
                keyfile = "${EMQX_ETC_DIR}/certs/key.pem"
            }
        }
    }
}


listeners.quic.default {
    enabled = true
    bind = "0.0.0.0:14567"
    max_connections = 1024000
    ## keyfile = "etc/certs/key.pem"
    ## certfile = "etc/certs/cert.pem"
    keyfile = "etc/certs/server.key"
    certfile = "etc/certs/server.crt"
}

I tested subscriptions against to prove it

alberto@debian:~/emqtt/_build/emqtt/rel/emqtt/bin$ ./emqtt sub -h '192.168.178.33' -p '14567' --enable-quic=true -q '1' -k '300' -t 'EK9160/EK-98EFB6/Stream1/Json/Tx/Data'
2025-01-02T23:39:08.678+01:00 Generated clientid: emqtt-debian-311fa4c47a9d472c192b
2025-01-02T23:39:08.730+01:00 Connected:
#{'Maximum-Packet-Size' => 1048576,'Receive-Maximum' => 32,
  'Retain-Available' => 1,'Shared-Subscription-Available' => 1,
  'Subscription-Identifier-Available' => 1,'Topic-Alias-Maximum' => 65535,
  'Wildcard-Subscription-Available' => 1}
2025-01-02T23:39:08.739+01:00 Subscribed to: EK9160/EK-98EFB6/Stream1/Json/Tx/Data
2025-01-02T23:39:09.030+01:00 {"Timestamp":"2025-01-02T22:39:08.193Z","Values":{"Slave 1 (EL1008).Channel 1.Input":true,"Slave 1 (EL1008).Channel 2.Input":false},"MetaData":{}}
2025-01-02T23:39:10.030+01:00 {"Timestamp":"2025-01-02T22:39:09.193Z","Values":{"Slave 1 (EL1008).Channel 1.Input":true,"Slave 1 (EL1008).Channel 2.Input":false},"MetaData":{}}

However running the subscription on the command line in the testapp I created with rebar3 does not work

alberto@debian:~/testapp/_build/default/lib/emqtt/bin$ ./emqtt sub -h '192.168.178.33' -p '14567' --enable-quic=true -q '1' -k '300' -t 'EK9160/EK-98EFB6/Stream1/Json/Tx/Data'
./emqtt: 11: exec: {{: not found

Here the contents of the emqtt script

alberto@debian:~/testapp/_build/default/lib/emqtt/bin$ cat emqtt 
#!/bin/sh
set -e

## constants from relx template
RUNNER_ROOT_DIR="{{ runner_root_dir }}"
RUNNER_BIN_DIR="{{ runner_bin_dir }}"
ERTS_VSN="{{ erts_vsn }}"

ERTS_PATH=$RUNNER_ROOT_DIR/erts-$ERTS_VSN/bin

This could mean that there could be dependencies missing in testapp rebar.config file. It looks like this

{erl_opts, [debug_info]}.
{deps, [{emqtt, {git, "https://github.com/emqx/emqtt.git", {branch, "master"}}},
        {emqtt, {git, "https://github.com/emqx/emqtt", {tag, "v1.2.0"}}}]}.

{shell, [
    %% {config, "config/sys.config"},
    {apps, [testapp]}
]}.

0 replies

SaveMe0 · 2025-01-03T20:15:56Z

SaveMe0
Jan 3, 2025
Author

I got emqtt:quic_connect/1 to work, but have no idea why it didn't work before. As I already state earlier in this discussion I'm using Erlang/OTP 27 hosted on Debian 12. The problem now emqtt:subscribe/3 - it doesn't return anything. Could someone in the emqtt group please test this code and let me know why emqtt:subscribe/3 does not return anything.

-module(com2).
-behaviour(gen_statem).
-define(NAME, com2).

-export([start/0, stop/0]).
-export([cnct/0, sub/0]).
-export([cnctState/3, subState/3]).

-export([init/1,callback_mode/0, handle_event/3, terminate/3, code_change/4]).

start() ->
    {ok, Pid} = gen_statem:start_link({local,?NAME}, ?MODULE, [], []),
    io:format("My proccess Pid ~p~n", [Pid]).

cnct() ->
    gen_statem:cast(?NAME, cnct).

sub() ->
    %gen_statem:call(?NAME, sub).
    gen_statem:cast(?NAME, sub).

stop() ->
    gen_statem:stop(?NAME).

-record(comm, {connPid, emqttMsg}).

callback_mode() ->
    [state_functions,state_enter].

init(_Args) ->
    process_flag(trap_exit, true),
    Properties = #{'Session-Expiry-Interval' => 300,
                    'Server-Keep-Alive' => 30,
                    'Retain-Available' => 1
                },

    Options = [ {host, "192.168.178.33"},
                {port, 14567},
                {keepalive, 30},
                %{clientid, <<"alb65McbrideBCCanada">>}, 
                {proto_ver, v5},
                {reconnect_timeout, 1000},
                %{quic_opts, {quicer:conn_opts(), quicer:stream_opts()}},
                {properties, Properties}
            ],

    {ok, ConnPid} = emqtt:start_link(Options),
    io:format("ConnPid from emqtt:start_link/1 ~p~n", [ConnPid]),
    State = cnctState, Data = #comm{connPid = ConnPid},
    %io:format("Data ~p~n", [Data]),
    {ok, State, Data}.


cnctState(cast, cnct, Data) ->
    ConnPid = Data#comm.connPid,
    io:format("ConnPid for emqtt:quic_connect/1 ~p~n", [ConnPid]),
    ConnPid = Data#comm.connPid,
    emqtt:quic_connect(ConnPid),
    {next_state, subState, Data};
cnctState(EventType, EventContent, Data) ->
    handle_event(EventType, EventContent, Data).   

%subState({call, From}, sub, Data) ->
subState(cast, sub, Data) ->
    ConnPid = Data#comm.connPid,
    io:format("CommPid for emqtt:subscribe/3 ~p~n", [ConnPid]),
    %Properties = #{},
    Properties = #{ %'Maximum-Packet-Size' => 1048576,
                    %'Receive-Maximum' => 32,
                    %'Retain-Available' => 1,
                    %'Shared-Subscription-Available' => 1,
                    %'Subscription-Identifier-Available' => 1,
                    %'Topic-Alias-Maximum' => 65535,
                    %'Wildcard-Subscription-Available' => 1,
                    'Message-Expiry-Interval' => 10,
                    %'Content-Type' => <<"Json">>,
                    'Payload-Format-Indicator' => 1,
                    'Content-Type' => <<"application/json">>,
                    'Server-Keep-Alive' => 30
                    %'Maximum-QoS' => 1
                    },
   SubOpts = [qos1],
    Subscriptions = [{<<"EK9160/EK-98EFB6/Stream1/Json/Tx/Data">>, SubOpts}],
    _ = emqtt:subscribe(ConnPid, Properties, Subscriptions),
    %io:format("Subscription~p~n", [Reply]),
    %{keep_state,Data, [{noreply, From, Data}]};
    {next_state, subState, Data};
subState(EventType, EventContent, Data) ->
    handle_event(EventType, EventContent, Data). 

handle_event(_, _, Data) ->
    %% Ignore all other events
    {keep_state, Data}.

terminate(_Reason, _State, _Data) ->
    ok.

code_change(_Vsn, State, Data, _Extra) ->
    {ok, State, Data}.

I'm asking because I was informed by

https://github.com/qzhuyan that the minimal stuff you want, assuming you are connecting to "127.0.0.1:14567"

{ok, Pid} = emqtt:start_link([{host, {127,0,0,1}},
                           {port, 14567}
                          ]),
 _ =emqtt:quic_connect(Pid),
emqtt:subscribe(Pid, <<"a/b/c">>, qos0).

Essentially my com2.erl module is using "the minimal stuff", but with the host "192.168.178.33" instead.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

emqtt:quic_connect/1 does not work with Erlang/OTP 27 on Debian 12 #14474

{{title}}

Replies: 3 comments

{{title}}

{{title}}

{{title}}

Select a reply

emqtt:quic_connect/1 does not work with Erlang/OTP 27 on Debian 12 #14474

SaveMe0 Dec 27, 2024

Replies: 3 comments

SaveMe0 Jan 2, 2025 Author

SaveMe0 Jan 2, 2025 Author

SaveMe0 Jan 3, 2025 Author

SaveMe0
Dec 27, 2024

SaveMe0
Jan 2, 2025
Author

SaveMe0
Jan 2, 2025
Author

SaveMe0
Jan 3, 2025
Author