ejabberd - Comments for "Ejabberd 16.09 Windows Service not start "

Same over here: Service stops

Arkadas — Wed, 23 Nov 2016 12:56:51 +0000

Same over here:
Service stops and displays error:

Error 1067: The procerss terminated unexpectedly

in windows logs i find:

Log Name: System
Source: ErlSrv
Date: 11/23/2016 1:33:22 PM
Event ID: 17
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ***
Description:
ejabberd: Could not start erlang service "ejabberd"with commandline ["C:\Program Files\ejabberd\bin\erl.exe" -service_event ErlSrv_ejabberd -nohup -sname ejabberd-srv@localhost -s win_service].
Event Xml:

17
2
0
0x80000000000000

55023
System
***

ejabberd
Could not start erlang service "ejabberd"with commandline ["C:\Program Files\ejabberd\bin\erl.exe" -service_event ErlSrv_ejabberd -nohup -sname ejabberd-srv@localhost -s win_service].

Changed the sname to ejabberd@localhost, but that did not help either.

regards,

Arkadas

I have the same error. Can

ashum — Wed, 09 Nov 2016 10:50:31 +0000

I have the same error. Can you resolve it?

I try to delete folder

gurarl — Mon, 10 Oct 2016 08:15:35 +0000

I try to delete folder database.
Start the service, folder does not recreate.

When i start ejabberd from desctop shortcut, it start and recreate database.

Can someone help me, please?

Thanks for reply! I got to

gurarl — Fri, 07 Oct 2016 16:13:24 +0000

Thanks for reply!
I got to start the service.
script that I used left below.
but jabberd start fail.
ejabberd.log:
2016-10-07 18:45:25.892 [info] <0.41.0>@cyrsasl_digest:start:60 FQDN used to check DIGEST-MD5 SASL authentication: <<"servername.domainname.ru">>
2016-10-07 18:45:25.892 [info] <0.41.0>@ejabberd_app:add_windows_nameservers:165 Adding machine's DNS IPs to Erlang system:
[]
2016-10-07 18:45:25.892 [error] <0.40.0> CRASH REPORT Process <0.40.0> with 0 neighbours exited with reason: {aborted,{no_exists,passwd,attributes}} in application_master:init/4 line 134
2016-10-07 18:45:25.908 [info] <0.7.0> Application ejabberd exited with reason: {aborted,{no_exists,passwd,attributes}}

crash.log
2016-10-07 18:45:25 =CRASH REPORT====
crasher:
initial call: application_master:init/4
pid: <0.40.0>
registered_name: []
exception exit: {{bad_return,{{ejabberd_app,start,[normal,[]]},{'EXIT',{aborted,{no_exists,passwd,attributes}}}}},[{application_master,init,4,[{file,"application_master.erl"},{line,134}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}
ancestors: [<0.39.0>]
messages: []
links: [<0.39.0>,<0.41.0>,<0.7.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 376
stack_size: 27
reductions: 114
neighbours:

From desctop link it start successful

Script to create erlsrv service ejabberd

erlsrv add ejabberd -sname ejabberd@localhost -w "C:\Program Files\ejabberd-16.09\bin"
erlsrv set ejabberd -ar "-kernel inetrc '\"%APPDATA%/ejabberd/conf/inetrc\"' -mnesia dir '\"%APPDATA%/ejabberd/database/mnesia\"' -sasl sasl_error_logger {file,'\"C:/ejabberd/logs/sasl.log\"'} -setcookie ejabberd -s ejabberd -smp enable +P 250000"
erlsrv set ejabberd -e "EJABBERD_BIN_PATH=C:\Program Files\ejabberd-16.09\lib\ejabberd-16.09\priv\bin"
erlsrv set ejabberd -e "EJABBERD_CONFIG_PATH=%APPDATA%\ejabberd\conf\ejabberd.yml"
erlsrv set ejabberd -e "EJABBERD_DOC_PATH=C:\Program Files\ejabberd-16.09\doc"
erlsrv set ejabberd -e "EJABBERD_LOG_PATH=%APPDATA%\ejabberd\logs\ejabberd.log"
erlsrv set ejabberd -e "EJABBERD_MSGS_PATH=C:\Program Files\ejabberd-16.09\lib\ejabberd-16.09\priv\msgs"
erlsrv set ejabberd -e "ERL_CRASH_DUMP=%APPDATA%\ejabberd\logs\erl_crash.dump"
erlsrv set ejabberd -e "ERL_INETRC=%APPDATA%\ejabberd\conf\inetrc"
erlsrv set ejabberd -e "ERL_LIBS=C:\Program Files\ejabberd-16.09\lib"
erlsrv set ejabberd -e "ERL_MAX_ETS_TABLES=1400"
erlsrv set ejabberd -e "ERL_MAX_PORTS=32000"

If the problem is a conflict

badlop — Fri, 07 Oct 2016 11:48:24 +0000

If the problem is a conflict in the "distribution name", you can try to change the -sname argument to something like ejabberd-srv-gurari@localhost

On the other hand, isn't that service already defined by postinstall, so that you only have to enable it somehow?