-
-
Notifications
You must be signed in to change notification settings - Fork 387
Did any one deploy Vernemq on IPv6 in Kubernetes deployment? #2249
Replies: 1 comment · 1 reply
-
@nivasvarma do you have the IPv6 listeners running, though? This looks like the listeners configured as services trying to start while you already have the IPv6 ones running on those ports. |
Beta Was this translation helpful? Give feedback.
All reactions
-
@ioolkos Even though the pod is up and in running state, vmq-admin connection not happening. See all the logs below LOGS$ date;kubectl get pod -o wide |grep -i vern vernemq@vernemq-0:~$ date;vmq-admin session show --client_id --topic $ kubectl logs -f vernemq-0 10:13:44.834 [debug] Replica meta2: Can't initialize AE exchange due to no peer available |
Beta Was this translation helpful? Give feedback.
-
I am trying to deploy Vernemq on IPv6 network with kubernetes and can see below errors.
LOGS
kubectl get pod -n ns-nk-4gc-niot1|grep -i vern
vernemq-0 0/1 Running 2 (21s ago) 4m24s
[chetan.verma@uhn5klbjhmgmt-s ~]$
Pod logs also we have captured.
11:48:19.248 [info] Try to start vmq_generic_msg_store: ok
11:48:19.379 [info] loaded 0 subscriptions into vmq_reg_trie
11:48:19.385 [info] cluster event handler 'vmq_cluster' registered
11:48:19.414 [error] can't reconfigure mqtt listener({127,0,0,1}, 1883) with Options [{max_connections,10000},{nr_of_acceptors,10},{mountpoint,[]},{proxy_protocol,false},{allowed_protocol_versions,[3,4,5,131]},{allow_anonymous_override,false}] due to {already_started,<0.436.0>}
11:48:19.415 [error] can't reconfigure mqtt listener({127,0,0,1}, 1883) with Options [{max_connections,10000},{nr_of_acceptors,10},{mountpoint,[]},{proxy_protocol,false},{allowed_protocol_versions,[3,4,5,131]},{allow_anonymous_override,false}] due to {already_started,<0.436.0>}
11:48:19.457 [error] can't reconfigure http listener({127,0,0,1}, 8888) with Options [{max_connections,10000},{nr_of_acceptors,10},{config_mod,vmq_http_config},{config_fun,config},{http_modules,"[]"},{listener_name,"default"},{proxy_protocol,false}] due to {already_started,<0.530.0>}
11:48:20.022 [debug] Replica meta1: Can't initialize AE exchange due to no peer available
11:48:20.034 [debug] Replica meta2: Can't initialize AE exchange due to no peer available
11:48:20.043 [debug] Replica meta3: Can't initialize AE exchange due to no peer available
11:48:20.050 [debug] Replica meta4: Can't initialize AE exchange due to no peer available
11:48:20.057 [debug] Replica meta5: Can't initialize AE exchange due to no peer available
Beta Was this translation helpful? Give feedback.
All reactions