[ejabberd] "bad argument in call to erlang:iolist_to_binary" since 19.09.1

Maximilian Trummer maximilian at trummer.xyz
Tue Dec 10 00:24:28 MSK 2019


Since upgrading from ejabberd 19.08 to 19.09.1, I see the following errors repeatedly:

2019-12-07 14:25:05.927 [error] <0.507.0>@str:format:289 gen_fsm <0.507.0> in state normal_state terminated with reason: bad argument in call to erlang:iolist_to_binary([73,116,32,105,115,32,110,111,116,32,97,108,108,111,119,101,100,32,116,111,32,115,101,110,100,32,...]) in str:format/2 line 289
2019-12-07 14:25:05.927 [error] <0.507.0>@str:format:289 CRASH REPORT Process <0.507.0> with 0 neighbours exited with reason: bad argument in call to erlang:iolist_to_binary([73,116,32,105,115,32,110,111,116,32,97,108,108,111,119,101,100,32,116,111,32,115,101,110,100,32,...]) in str:format/2 line 289
2019-12-07 14:25:05.927 [error] <0.466.0>@str:format:289 Supervisor 'mod_muc_room_sup_mydomain.com' had child undefined started with {mod_muc_room,start_link,undefined} at <0.507.0> exit with reason bad argument in call to erlang:iolist_to_binary([73,116,32,105,115,32,110,111,116,32,97,108,108,111,119,101,100,32,116,111,32,115,101,110,100,32,...]) in str:format/2 line 289 in context child_terminated
2019-12-07 14:50:22.595 [error] <0.474.0>@ejabberd_sql:check_error:1195 SQL query 'Q37448423' at {mod_mam_sql,122} failed: [{severity,'FEHLER'},{86,<<"ERROR">>},{code,<<"22021">>},{message,<<"ungültige Byte-Sequenz für Kodierung »UTF8«: 0x00">>},{file,<<"wchar.c">>},{line,2017},{routine,<<"report_invalid_encoding">>}]
2019-12-07 14:56:23.372 [error] <0.474.0>@ejabberd_sql:check_error:1195 SQL query 'Q37448423' at {mod_mam_sql,122} failed: [{severity,'FEHLER'},{86,<<"ERROR">>},{code,<<"22021">>},{message,<<"ungültige Byte-Sequenz für Kodierung »UTF8«: 0x00">>},{file,<<"wchar.c">>},{line,2017},{routine,<<"report_invalid_encoding">>}]

First there's an error in gen_fsm and then SQL errors about a nullbyte.
This repeats every few hours with the argument in iolist_to_binary
(73,116,32,105,115,32,110...) and the SQL query (Q37448423) always the same.
The database is PostgreSQL 10.
Unfortunately I don't know how to reproduce the errors.
Any ideas what it could be?




More information about the ejabberd mailing list