Skip to content
New issue

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

S2S connection between two ejabberd's fails #2219

Closed
wornet-mwo opened this issue Jan 12, 2018 · 5 comments
Closed

S2S connection between two ejabberd's fails #2219

wornet-mwo opened this issue Jan 12, 2018 · 5 comments
Assignees

Comments

@wornet-mwo
Copy link

The problem is based on connection between two hosts.

What version of ejabberd are you using?

17.12 in both setups

What operating system (version) are you using?

alpine, both setups based on the docker image ejabberd/ecs:17:12, running on ubuntu-docker-host

How did you install ejabberd (source, package, distribution)?

ejabberd/ecs:17:12 from hub.docker.com

What did not work as expected? Are there error messages in the log? What
was the unexpected behavior? What was the expected result?

S2S connections fail from both sides. The receiving side logs this:

2018-01-12 09:11:28.728 [error] <0.1725.0> gen_server <0.1725.0> terminated with reason: {'module could not be loaded',[{regexp,sh_to_awk,["*"],[]},{ejabberd_regexp,sh_to_awk,1,[{file,"src/ejabberd_regexp.erl"},{line,91}]},{xmpp_stream_pkix,match_labels,2,[{file,"src/xmpp_stream_pkix.erl"},{line,235}]},{lists,any,2,[{file,"lists.erl"},{line,1225}]},{xmpp_stream_pkix,authenticate,2,[{file,"src/xmpp_stream_pkix.erl"},{line,52}]},{xmpp_stream_in,process_sasl_request,2,[{file,"src/xmpp_stream_in.erl"},{line,788}]},{xmpp_stream_in,handle_info,2,[{file,"src/xmpp_stream_in.erl"},{line,...}]},...]}
2018-01-12 09:11:28.729 [error] <0.1725.0>@regexp:sh_to_awk CRASH REPORT Process <0.1725.0> with 0 neighbours exited with reason: call to undefined function regexp:sh_to_awk("*") in p1_server:terminate/7 line 878
2018-01-12 09:11:28.730 [error] <0.1541.0>@regexp:sh_to_awk Supervisor ejabberd_s2s_in_sup had child undefined started with {ejabberd_s2s_in,start_link,undefined} at <0.1725.0> exit with reason call to undefined function regexp:sh_to_awk("*") in context child_terminated

The connecting side:

2018-01-12 09:08:53.227 [info] <0.1733.0>@ejabberd_s2s_out:init:277 Outbound s2s connection started: CCC.de -> YYY.net
2018-01-12 09:08:53.273 [info] <0.1733.0>@ejabberd_s2s_out:process_closed:161 Failed to establish outbound s2s connection CCC.de -> YYY.net: Stream reset by peer; bouncing for 89 seconds

Connections from other domains servers (non ejabberd) are working.

Maybe related settings:

´´´
s2s_use_starttls: optional
´´´

Additionally on CCC.de:

acl:
  good_s2s_peers:
    server:
      - "YYY.net"
      - "jabber.YYY.net"
acccess:
  s2s:
    good_s2s_peers: allow
    all: deny

I'll provide additional config etc. anonymized on request (as there is a customers system involved) and this is quite hard to do in advance. Thanks in advance for help.

@zinid
Copy link
Contributor

zinid commented Jan 12, 2018

Clearly installation problem: some bytecode files are missing.

@cromain
Copy link
Contributor

cromain commented Jan 12, 2018

mix.exs lacks xmerl application

@cromain cromain added this to the ejabberd 18.x milestone Jan 12, 2018
@cromain cromain self-assigned this Jan 12, 2018
@cromain
Copy link
Contributor

cromain commented Jan 12, 2018

xmerl is used only to call xmerl_regexp:sh_to_awk/1. maybe this can be rewritten to avoid need to include all xmerl by the way.

@cromain cromain modified the milestones: ejabberd 18.x, ejabberd 18.03 Jan 12, 2018
@cromain
Copy link
Contributor

cromain commented Jan 15, 2018

fixed by 3df78d3. We removed xmerl dependency.

@cromain cromain closed this as completed Jan 15, 2018
@lock
Copy link

lock bot commented Jun 9, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants