Segmentation fault on startup on raspberry pi

Hi,

I'm trying to run ejabberd on my raspberry pi (raspbian wheezy) but I get a segmentation fault on startup without more information.

I followed instructions here : https://docs.ejabberd.im/admin/guide/installation/#installing-ejabberd-fr...
I use ejabberd.yml example file, and when I start it with : ejabberdctl live
I get :
Erlang/OTP 18 [erts-7.1] [source] [async-threads:10] [hipe] [kernel-poll:true]

Eshell V7.1 (abort with ^G)
(ejabberd@localhost)1> 08:35:53.239 [info] Application lager started on node ejabberd@localhost
08:35:53.527 [info] Application crypto started on node ejabberd@localhost
08:35:53.786 [info] Application sasl started on node ejabberd@localhost
08:35:54.161 [info] Application asn1 started on node ejabberd@localhost
08:35:54.176 [info] Application public_key started on node ejabberd@localhost
08:35:54.653 [info] Application ssl started on node ejabberd@localhost
08:35:54.771 [info] Application p1_yaml started on node ejabberd@localhost
08:35:55.011 [info] Application p1_tls started on node ejabberd@localhost
08:35:55.224 [info] Application p1_xml started on node ejabberd@localhost
08:35:55.697 [info] Application p1_stringprep started on node ejabberd@localhost
08:35:55.837 [info] Application p1_zlib started on node ejabberd@localhost
08:35:56.034 [info] Application cache_tab started on node ejabberd@localhost
08:35:59.993 [info] Application mnesia started on node ejabberd@localhost
08:36:18.326 [info] Application inets started on node ejabberd@localhost
Segmentation fault

Nothing more on log file (/var/log/ejabberd/ejabberd.log), except that the last line "08:36:18.326 [info] Application inets started on node ejabberd@localhost" is missing.

Any idea to help me ?

Thanks.

I can only tell you what

I can only tell you what should go after that line, see in my case:

Erlang/OTP 17 [erts-6.2] [source] [64-bit] [smp:2:2] [async-threads:10] [kernel-poll:true]

Eshell V6.2  (abort with ^G)
22:27:03.952 [info] Application lager started on node ejabberd@localhost
22:27:04.013 [info] Application crypto started on node ejabberd@localhost
22:27:04.093 [info] Application sasl started on node ejabberd@localhost
22:27:04.199 [info] Application asn1 started on node ejabberd@localhost
22:27:04.201 [info] Application public_key started on node ejabberd@localhost
22:27:04.279 [info] Application ssl started on node ejabberd@localhost
22:27:04.309 [info] Application p1_yaml started on node ejabberd@localhost
22:27:04.347 [info] Application p1_tls started on node ejabberd@localhost
22:27:04.375 [info] Application p1_xml started on node ejabberd@localhost
22:27:04.405 [info] Application p1_stringprep started on node ejabberd@localhost
22:27:04.418 [info] Application p1_zlib started on node ejabberd@localhost
22:27:04.442 [info] Application cache_tab started on node ejabberd@localhost
22:27:04.936 [info] Application mnesia started on node ejabberd@localhost
22:27:06.581 [info] Application inets started on node ejabberd@localhost
22:27:08.158 [info] FQDN used to check DIGEST-MD5 SASL authentication: atenea.pike
22:27:08.180 [info] Application oauth2 started on node ejabberd@localhost
22:27:08.258 [info] Application p1_iconv started on node ejabberd@localhost
22:27:08.329 [info] Reusing listening port for {4560,{0,0,0,0},tcp}
22:27:08.330 [info] Reusing listening port for {5222,{0,0,0,0},tcp}
22:27:08.330 [info] Reusing listening port for {5269,{0,0,0,0},tcp}
22:27:08.332 [info] Reusing listening port for {5280,{0,0,0,0},tcp}
22:27:08.333 [info] Reusing listening port for {5281,{0,0,0,0},tcp}
22:27:08.333 [info] ejabberd 15.11.114 is started in the node ejabberd@localhost
22:27:08.333 [info] Application ejabberd started on node ejabberd@localhost
Syndicate content