- #Arch linux ejabberd start of supervisor sl failed how to#
- #Arch linux ejabberd start of supervisor sl failed install#
- #Arch linux ejabberd start of supervisor sl failed windows#
And sasl.log had a lot of PROGRESS REPORT.Īn idea: stop ejabberd, kill any process called 'beam', uninstall ejabberd, restart your machine, download the installer, install (put a very easy domain: localhost), start ejabberd. There were two log files: ejabberd.log had similar content to yours.
#Arch linux ejabberd start of supervisor sl failed how to#
The web browser opened telling me where to find log files, and how to login in the web admin.
#Arch linux ejabberd start of supervisor sl failed windows#
I've just downloaded ejabberd 2.0.0 windows installer, and installed it in Windows Vista Home Premium, no problem installing, no problem starting. The server I am running on is a VPS under the Virtuozzo On my local Vista Ultimate (both versions of ejjaberd) and they failed in exactly the I dont know if that makes a difference cause I also tried it I do have all the crash dumps, can i email one to you so that maybe you can help me out? or can you tell me what to look for in them? I(:mod_pubsub:211) : ** init pep I dont know if its waiting for me to do something or if its already dead. ejabberddctl live command and it stopped right afterĮshell V5.5.5 (abort with REPORT= 2::16:43:01 = I did include all the files I found on the previous messages.that includes the log from one of the failed starts. I dont know if it listens to ports or not. *Note: if you need to remove the service you can use the following command: erlsrv remove ejabberd You can also do a NETSTAT -AN at the command prompt to validate port 52 are open. Open a browser to and login with the credentials you set during the original installation.Įverything should be working now and clients should be able to connect. Note this folder down and add that to the registry path inside the manual.vbs. Look in the registry and you will see that there is an extra folder before the Ericsson folder. Run the file manual.vbs and you will get a registry error. Open a command prompt and run the following command (taken from the postinstall.bat) in the bin directory where ejabberd is installed:Įrlsrv add ejabberd -sname -w "C:\Program Files\ejabberd-2.0.1\bin" -ar "-s win_service" -st "win_service:stop()."ħ. Replace the entire contents where ejabberd is installed.ĥ. Copy the ejabberd installation from the working dedicated server to the container.
Just to be safe, make sure ejabberd is not a registered service*.Ĥ. Just kill the erlang process and that should kill the processes. Kill the processes using task manager - make sure you select to Show Process from All Users. Make sure ejabberd processes are not running in the container. Just make sure the install directory from your dedicated install are exactly the same from Step #1.ģ. container) - ignore errors or the fact that it doesn't start.
Install ejabberd in the Parallels VPS (i.e. Install ejabberd on a seperate dedicated system (XP or 2003). Most likely these steps could be simplified but hopefully this can shed some light as to why Parallels has an issue with ejabberd:ġ. I(:mod_pubsub:152) : pubsub init "localhost" [Īny other info that I need to provide so that someone can help me out with this problem?Īfter hacking away at this I finally got it working. ejabberdctl startedĬ:\Program Files\ejabberd-2.0.0\bin>if errorlevel 1 goto errorĬ:\Program Files\ejabberd-2.0.0\bin>echo Cannot start ejabberd ejabberdctl startĬ:\Program Files\ejabberd-2.0.0\bin>bash. formatconfig.shĬ:\Program Files\ejabberd-2.0.0\bin>rem Start ejabberdĬ:\Program Files\ejabberd-2.0.0\bin>bash. Here are the results of the POSTINSTALL bat file.ĭuring installation I named the domain LOCALHOST in all caps.Ĭ:\Program Files\ejabberd-2.0.0\bin>postinstall admin LOCALHOST 123456Ĭ:\Program Files\ejabberd-2.0.0\bin>rem offĬ:\Program Files\ejabberd-2.0.0\bin>cd /D "C:\Program Files\ejabberd-2.0.0\bin"Ĭ:\Program Files\ejabberd-2.0.0\bin>bash.
0 kommentar(er)
