Closed venkateshcontus closed 4 weeks ago
Hi
After upgrage my ejabberd version 23 to 24.04, I try to get the sbin/ejabberdctl --node ejabberd@10.44.0.32 list_cluster
args: [] format: "Can't set long node name!\nPlease check your configuration\n" label: {error_logger,info_msg} =SUPERVISOR REPORT==== 8-Mar-2024::09:23:20.814378 === supervisor: {local,net_sup} errorContext: start_error reason: {'EXIT',nodistribution} offender: [{pid,undefined}, {id,net_kernel}, {mfargs,{net_kernel,start_link, [#{clean_halt => true,name => undefined, name_domain => longnames, supervisor => net_sup}]}}, {restart_type,permanent}, {significant,false}, {shutdown,2000}, {child_type,worker}] {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}}"} Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}}) No errors
I didn't change any configuration in yml file after migrate ejabberd23 to 24.
Quite a strange problem. Do you get the error when running "ejabberdctl list_cluster" and other commands, but no problem starting ejabberd and connecting clients to it?
https://github.com/processone/ejabberd/issues/4184
Hi
After upgrage my ejabberd version 23 to 24.04, I try to get the sbin/ejabberdctl --node ejabberd@10.44.0.32 list_cluster
Environment
Errors from error.log/crash.log
Bug description
I didn't change any configuration in yml file after migrate ejabberd23 to 24.