|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Windows, install ejabberd using the Windows binary installer
|
|
Issue Links:
|
Solution
|
|
This issue solves:
|
|
EJAB-589
ejabberdctl fails to connect to running ejabberd with 'nodedown' error when ejabberd is running as Windows service
|
|
|
|
|
|
|
|
|
The linux source package, Linux binary installer and Mac binary installer use ejabberdctl to start ejabberd. This script passes some options to the erlang machine, and also reads ejabberdctl.cfg. This allows the administrator to customize some Erlang options.
The Windows binary installer allows to start ejabberd in two ways: with a Desktop shortcut or a Windows service. The shortcut uses ejabberdctl. But the windows service is created using erlsrv, and it doesn't use ejabberdctl at all.
As a summary: in Windows, the changes in ejabberdctl.cfg are not read if ejabberd is started using the windows service.
|
|
Description
|
The linux source package, Linux binary installer and Mac binary installer use ejabberdctl to start ejabberd. This script passes some options to the erlang machine, and also reads ejabberdctl.cfg. This allows the administrator to customize some Erlang options.
The Windows binary installer allows to start ejabberd in two ways: with a Desktop shortcut or a Windows service. The shortcut uses ejabberdctl. But the windows service is created using erlsrv, and it doesn't use ejabberdctl at all.
As a summary: in Windows, the changes in ejabberdctl.cfg are not read if ejabberd is started using the windows service. |
Show » |
|
Bug
Minor
1) find a way to declare a service that can call start/stop batch script if possible
2) use erlsrv to start a service node without arguments. from that node we can :
- cd to the ejabberd directory
- os:cmd("bash ejabberdctl start").
- loop on receiving the node kill
- os:cmd("bash ejabberdctl stop").
- quit