We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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
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
Bug description
The text was updated successfully, but these errors were encountered: