Hi, > could you please supply corresponding logs?
Here is the crash dump:
2018-04-14 19:50:16 =CRASH REPORT====
crasher:
initial call: pgsql_proto:init/1
pid: <0.516.0>
registered_name: []
exception exit:
{{init,{error,nxdomain}},[{gen_server,init_it,6,[{file,"gen_server.erl"},{line,344}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}
ancestors:
[<0.481.0>,'ejabberd_sql_sup_mercurius.teckids.org',ejabberd_rdbms,ejabberd_sup,<0.62.0>]
messages: []
links: []
dictionary: []
trap_exit: false
status: running
heap_size: 610
stack_size: 27
reductions: 349
neighbours:
Error log:
2018-04-14 19:52:06.522 [error] <0.648.0>@eldap:connect_bind:1083 LDAP
connection failed:
** Server: db.teckids.org:636
** Reason: nxdomain
** Socket options: [{packet,asn1},{active,true},{keepalive,true},binary]
ejabberd.log has nothing different.
> Also, have you tried configuring IPv6 addresses directly instead of AAAA
> records to rule out wonky DNS?
See my initial report ;). Putting an IPv6 address leads to the same error,
and ejabberd even seems to try to resolve it via a DNS forward query because
with an IPv6 address, the error also is nxdomain.
-nik
signature.asc
Description: PGP signature
