I tried installing both the v1 and the v2 of ejabberd on both a win2003 server and a vista machine. On two different networks (a machine in a hosted server environment and one in a home network) They install fine but it wont start. I cannot login to the admin either.
The log doesn't mention any error or anything (would it? I am new with this app). All I see as process called ERL.exe running but jabber doesnt work.
I have no firewalls active. I have tried uninstalling and reinstalling several times each one with a different domain..i tried localhost, my machines name (all CAPS and no caps), an actual domain with an A record pointing to the machine,etc. Nothing has worked. It just wont start.
I have also tried loggin in to localhost:5280/admin and do get the http auth window but it never accepts my username and password. I have tried admin, admin@localhost, etc.
any suggestions?
-gk
here are the results of the
here are the results of the POSTINSTALL bat file.
During installation I named the domain LOCALHOST in all caps.
-----------------------------------------------
C:\Program Files\ejabberd-2.0.0\bin>postinstall admin LOCALHOST 123456
C:\Program Files\ejabberd-2.0.0\bin>rem @echo off
C:\Program Files\ejabberd-2.0.0\bin>cd /D "C:\Program Files\ejabberd-2.0.0\bin"
C:\Program Files\ejabberd-2.0.0\bin>bash ./formatconfig.sh
C:\Program Files\ejabberd-2.0.0\bin>rem Start ejabberd
C:\Program Files\ejabberd-2.0.0\bin>bash ./ejabberdctl start
C:\Program Files\ejabberd-2.0.0\bin>bash ./ejabberdctl started
C:\Program Files\ejabberd-2.0.0\bin>if errorlevel 1 goto error
C:\Program Files\ejabberd-2.0.0\bin>echo Cannot start ejabberd
Cannot start ejabberd
C:\Program Files\ejabberd-2.0.0\bin>
-----------------------------------------------
here is the log
-----------------------------------------------
=INFO REPORT==== 2008-02-22 12:18:13 ===
I(<0.291.0>:mod_pubsub:152) : pubsub init "localhost" [{access_createnode,
pubsub_createnode},
{plugins,
["default","pep"]}]
=INFO REPORT==== 2008-02-22 12:18:13 ===
I(<0.291.0>:mod_pubsub:207) : ** tree plugin is nodetree_default
=INFO REPORT==== 2008-02-22 12:18:13 ===
I(<0.291.0>:mod_pubsub:211) : ** init default plugin
=INFO REPORT==== 2008-02-22 12:18:13 ===
I(<0.291.0>:mod_pubsub:211) : ** init pep plugin
=INFO REPORT==== 2008-02-22 12:31:54 ===
I(<0.254.0>:ejabberd_listener:112) : (#Port<0.374>) Accepted connection {{127,0,0,1},1902} -> {{127,0,0,1},5280}
=INFO REPORT==== 2008-02-22 12:31:54 ===
I(<0.247.0>:ejabberd_http:123) : started: {gen_tcp,#Port<0.374>}
-----------------------------------
any other info that I need to provide so that someone can help me out with this problem?
thanks,
-gk
Getting ejabberd working in Parallels (windows)
After hacking away at this I finally got it working. Most likely these steps could be simplified but hopefully this can shed some light as to why Parallels has an issue with ejabberd:
1. Install ejabberd on a seperate dedicated system (XP or 2003). Make sure it works.
2. Install ejabberd in the Parallels VPS (i.e. container) - ignore errors or the fact that it doesn't start. Just make sure the install directory from your dedicated install are exactly the same from Step #1.
3. Make sure ejabberd processes are not running in the container. Kill the processes using task manager - make sure you select to Show Process from All Users. Just kill the erlang process and that should kill the processes. Just to be safe, make sure ejabberd is not a registered service*.
4. Copy the ejabberd installation from the working dedicated server to the container. Replace the entire contents where ejabberd is installed.
5. Open a command prompt and run the following command (taken from the postinstall.bat) in the bin directory where ejabberd is installed:
erlsrv add ejabberd -sname ejabberd-srv@localhost -w "C:\Program Files\ejabberd-2.0.1\bin" -ar "-s win_service" -st "win_service:stop()."
7. Run the file manual.vbs and you will get a registry error. Look in the registry and you will see that there is an extra folder before the Ericsson folder. Note this folder down and add that to the registry path inside the manual.vbs. Re-run manual.vbs
8. Start the ejabberd Windows service. Don't use the desktop icon.
9. Open a browser to and login with the credentials you set during the original installation.
Everything should be working now and clients should be able to connect. You can also do a NETSTAT -AN at the command prompt to validate port 5222 and 5280 are open.
*Note: if you need to remove the service you can use the following command: erlsrv remove ejabberd
So you tried both ejabberd
So you tried both ejabberd 1.1.4 binary installer installer and the new 2.0.0? And you get the same result: it gets installed (more or less), the Erlang system starts but ejabberd doesn't listen to the ports.
You should have ejabberd.log, or at least a file erl_crash.dump or similar.
You can also try to start ejabberd manually to get some error message. Start the Bash shell (bash.exe) and then: ./ejabberdctl live
I dont know if it listens to
I dont know if it listens to ports or not. How can I tell. I did include all the files I found on the previous messages...that includes the log from one of the failed starts. I just tried running the ./ejabberddctl live command and it stopped right after
-----------------------
Eshell V5.5.5 (abort with ^G)
(ejabberd@localhost)1>
=INFO REPORT==== 26-Feb-2008::16:43:01 ===
I(<0.295.0>:mod_pubsub:152) : pubsub init "localhost" [{access_createnode,
pubsub_createnode},
{plugins,
["default","pep"]}]
(ejabberd@localhost)1>
=INFO REPORT==== 26-Feb-2008::16:43:01 ===
I(<0.295.0>:mod_pubsub:207) : ** tree plugin is nodetree_default
(ejabberd@localhost)1>
=INFO REPORT==== 26-Feb-2008::16:43:01 ===
I(<0.295.0>:mod_pubsub:211) : ** init default plugin
(ejabberd@localhost)1>
=INFO REPORT==== 26-Feb-2008::16:43:01 ===
I(<0.295.0>:mod_pubsub:211) : ** init pep plugin
(ejabberd@localhost)1>
-------------------------------
now I dont know if its waiting for me to do something or if its already dead.
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?
one more piece of data. The server I am running on is a VPS under the Virtuozzo
management console. I dont know if that makes a difference cause I also tried it
on my local Vista Ultimate (both versions of ejjaberd) and they failed in exactly the
same way.
thanks for any help you might provide.
-guillermo
I tried 2.0.0 with Windows Vista, and works
I dont know if it listens to ports or not. How can I tell.
I do a simple test: if the jabber host specified is 'localhost', I try this in a shell (maybe you can't do this in Windows...):
I just tried running the ./ejabberddctl live command and it stopped right after
...
now I dont know if its waiting for me to do something or if its already dead.
Quite probably it started ejabberd, and is waiting for commands. For example you can try:
(ejabberd@localhost)1> 55+12. 67 (ejabberd@localhost)2> ets:tab2list(config). [{config,language,"en"}, {config,{access,c2s,global},[{deny,blocked},{allow,all}]}, {config,{access,pubsub_createnode,global},[{allow,all}]}, {config,{access,s2s_shaper,global},[{fast,all}]}, {config,{access,c2s_shaper,global}, [{none,admin},{normal,all}]}, {config,hosts,["localhost","81.202.78.207"]}, {config,{access,announce,global},[{allow,admin}]}, {config,{access,register,global},[{allow,all}]}, {config,{access,local,global},[{allow,local}]}]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 don't know how to interpret crash dumps.
The server I am running on is a VPS under the Virtuozzo
management console. I dont know if that makes a difference cause I also tried it
on my local Vista Ultimate (both versions of ejjaberd) and they failed in exactly the
same way.
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 web browser opened telling me where to find log files, and how to login in the web admin. I could login in the web admin. There were two log files: ejabberd.log had similar content to yours. And sasl.log had a lot of PROGRESS REPORT.
An 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. When the web browser opens with a page linking to log files, check if a file sasl.log was created, and the last lines are
=PROGRESS REPORT==== 4-Mar-2008::22:43:24 === application: ejabberd started_at: ejabberd@localhostI wrote a lot of
I wrote a lot of explanations and included all the info I coould....
here it goes....and thanks in advance for all the help you are providing to me.
I really appreciate it.
I uninstalled, deleted the remaining folders and files, rebooted.
I installed...chose "localhost" (in lowercase) as server name
"admin" as user and "12345" as password.
It installs fine, but on the last step of the installation it takes
a long long time...but does install eventually.
Then I double click on the "start ejabberd" shortcut in the desktop.
It opnes the console and says "starting ejabberd..." and then takes a very long time (about 5 minutes) until I get a response (the machine is a fast machine with 1GB of ram)
The response is a web page that says:
"
Error occured...
Please check your configuration and your installation.
If you are an advanced user, you can check the logs to check what is going wrong.
The name of the current ejabberd node is ejabberd@localhost.
For more informations, please go to the Process-one site or the ejabberd Community Site
"
in the logs directory there are 3 files
-----------------------------------------------
1) ejabberd.log
"
=INFO REPORT==== 2008-03-10 12:40:49 ===
I(<0.302.0>:mod_pubsub:152) : pubsub init "localhost" [{access_createnode,
pubsub_createnode},
{plugins,
["default","pep"]}]
=INFO REPORT==== 2008-03-10 12:40:49 ===
I(<0.302.0>:mod_pubsub:207) : ** tree plugin is nodetree_default
=INFO REPORT==== 2008-03-10 12:40:49 ===
I(<0.302.0>:mod_pubsub:211) : ** init default plugin
=INFO REPORT==== 2008-03-10 12:40:49 ===
I(<0.302.0>:mod_pubsub:211) : ** init pep plugin
"
----------------------------------------------------
2)sasl.log
"
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,sasl_safe_sup}
started: [{pid,<0.46.0>},
{name,alarm_handler},
{mfa,{alarm_handler,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,sasl_safe_sup}
started: [{pid,<0.47.0>},
{name,overload},
{mfa,{overload,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.45.0>},
{name,sasl_safe_sup},
{mfa,
{supervisor,
start_link,
[{local,sasl_safe_sup},sasl,safe]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,sasl_sup}
started: [{pid,<0.48.0>},
{name,release_handler},
{mfa,{release_handler,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
application: sasl
started_at: ejabberd@localhost
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,kernel_safe_sup}
started: [{pid,<0.52.0>},
{name,disk_log_sup},
{mfa,{disk_log_sup,start_link,[]}},
{restart_type,permanent},
{shutdown,1000},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,kernel_safe_sup}
started: [{pid,<0.53.0>},
{name,disk_log_server},
{mfa,{disk_log_server,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,mnesia_sup}
started: [{pid,<0.66.0>},
{name,mnesia_event},
{mfa,{mnesia_sup,start_event,[]}},
{restart_type,permanent},
{shutdown,30000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,mnesia_kernel_sup}
started: [{pid,<0.68.0>},
{name,mnesia_monitor},
{mfa,{mnesia_monitor,start,[]}},
{restart_type,permanent},
{shutdown,3000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,mnesia_kernel_sup}
started: [{pid,<0.69.0>},
{name,mnesia_subscr},
{mfa,{mnesia_subscr,start,[]}},
{restart_type,permanent},
{shutdown,3000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,mnesia_kernel_sup}
started: [{pid,<0.70.0>},
{name,mnesia_locker},
{mfa,{mnesia_locker,start,[]}},
{restart_type,permanent},
{shutdown,3000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,mnesia_kernel_sup}
started: [{pid,<0.71.0>},
{name,mnesia_recover},
{mfa,{mnesia_recover,start,[]}},
{restart_type,permanent},
{shutdown,180000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,kernel_safe_sup}
started: [{pid,<0.75.0>},
{name,dets_sup},
{mfa,{dets_sup,start_link,[]}},
{restart_type,permanent},
{shutdown,1000},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:47 ===
supervisor: {local,kernel_safe_sup}
started: [{pid,<0.76.0>},
{name,dets},
{mfa,{dets_server,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,kernel_safe_sup}
started: [{pid,<0.85.0>},
{name,timer_server},
{mfa,{timer,start_link,[]}},
{restart_type,permanent},
{shutdown,1000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,mnesia_kernel_sup}
started: [{pid,<0.72.0>},
{name,mnesia_tm},
{mfa,{mnesia_tm,start,[]}},
{restart_type,permanent},
{shutdown,30000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,mnesia_kernel_sup}
started: [{pid,<0.86.0>},
{name,mnesia_checkpoint_sup},
{mfa,{mnesia_checkpoint_sup,start,[]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,mnesia_kernel_sup}
started: [{pid,<0.87.0>},
{name,mnesia_snmp_sup},
{mfa,{mnesia_snmp_sup,start,[]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,mnesia_kernel_sup}
started: [{pid,<0.88.0>},
{name,mnesia_controller},
{mfa,{mnesia_controller,start,[]}},
{restart_type,permanent},
{shutdown,3000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,mnesia_kernel_sup}
started: [{pid,<0.89.0>},
{name,mnesia_late_loader},
{mfa,{mnesia_late_loader,start,[]}},
{restart_type,permanent},
{shutdown,3000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,mnesia_sup}
started: [{pid,<0.67.0>},
{name,mnesia_kernel_sup},
{mfa,{mnesia_kernel_sup,start,[]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
application: mnesia
started_at: ejabberd@localhost
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,crypto_sup}
started: [{pid,<0.97.0>},
{name,crypto_server},
{mfa,{crypto_server,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
application: crypto
started_at: ejabberd@localhost
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ssl_sup}
started: [{pid,<0.103.0>},
{name,ssl_server},
{mfa,{ssl_server,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ssl_sup}
started: [{pid,<0.104.0>},
{name,ssl_broker_sup},
{mfa,{ssl_broker_sup,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
application: ssl
started_at: ejabberd@localhost
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,stringprep_sup}
started: [{pid,<0.106.0>},
{name,stringprep},
{mfa,{stringprep,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.154.0>},
{name,ejabberd_hooks},
{mfa,{ejabberd_hooks,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,kernel_safe_sup}
started: [{pid,<0.156.0>},
{name,pg2},
{mfa,{pg2,start_link,[]}},
{restart_type,permanent},
{shutdown,1000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.155.0>},
{name,ejabberd_node_groups},
{mfa,{ejabberd_node_groups,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.157.0>},
{name,ejabberd_system_monitor},
{mfa,{ejabberd_system_monitor,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.158.0>},
{name,ejabberd_router},
{mfa,{ejabberd_router,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.164.0>},
{name,ejabberd_sm},
{mfa,{ejabberd_sm,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.178.0>},
{name,ejabberd_s2s},
{mfa,{ejabberd_s2s,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.184.0>},
{name,ejabberd_local},
{mfa,{ejabberd_local,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.189.0>},
{name,ejabberd_receiver_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_receiver_sup,ejabberd_receiver]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.190.0>},
{name,ejabberd_c2s_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_c2s_sup,ejabberd_c2s]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.191.0>},
{name,ejabberd_s2s_in_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_s2s_in_sup,ejabberd_s2s_in]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.192.0>},
{name,ejabberd_s2s_out_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_s2s_out_sup,ejabberd_s2s_out]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.193.0>},
{name,ejabberd_service_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_service_sup,ejabberd_service]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.194.0>},
{name,ejabberd_http_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_http_sup,ejabberd_http]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.195.0>},
{name,ejabberd_http_poll_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_http_poll_sup,ejabberd_http_poll]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.196.0>},
{name,ejabberd_iq_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_iq_sup,gen_iq_handler]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.197.0>},
{name,ejabberd_frontend_socket_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_frontend_socket_sup,
ejabberd_frontend_socket]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_listeners}
started: [{pid,<0.199.0>},
{name,5222},
{mfa,
{ejabberd_listener,
start,
[5222,
ejabberd_c2s,
[{certfile,
"C:\\Program Files\\ejabberd-2.0.0\\conf\\server.pem"},
starttls,
{access,c2s},
{shaper,c2s_shaper},
{max_stanza_size,65536}]]}},
{restart_type,transient},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_listeners}
started: [{pid,<0.200.0>},
{name,5269},
{mfa,
{ejabberd_listener,
start,
[5269,
ejabberd_s2s_in,
[{shaper,s2s_shaper},
{max_stanza_size,131072}]]}},
{restart_type,transient},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_listeners}
started: [{pid,<0.201.0>},
{name,5280},
{mfa,
{ejabberd_listener,
start,
[5280,
ejabberd_http,
[http_bind,http_poll,web_admin]]}},
{restart_type,transient},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.198.0>},
{name,ejabberd_listener},
{mfa,{ejabberd_listener,start_link,[]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.223.0>},
{name,ejabberd_mod_caps_localhost},
{mfa,{mod_caps,start_link,["localhost",[]]}},
{restart_type,transient},
{shutdown,1000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.240.0>},
{name,ejabberd_http_bind_sup},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_http_bind_sup,ejabberd_http_bind]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.241.0>},
{name,ejabberd_mod_irc_sup_localhost},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_mod_irc_sup_localhost,
mod_irc_connection]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.242.0>},
{name,ejabberd_mod_irc_localhost},
{mfa,{mod_irc,start_link,["localhost",[]]}},
{restart_type,temporary},
{shutdown,1000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.258.0>},
{name,ejabberd_mod_muc_sup_localhost},
{mfa,
{ejabberd_tmp_sup,
start_link,
[ejabberd_mod_muc_sup_localhost,mod_muc_room]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:48 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.259.0>},
{name,ejabberd_mod_muc_localhost},
{mfa,{mod_muc,start_link,
["localhost",
[{access,muc},
{access_create,muc},
{access_persistent,muc},
{access_admin,muc_admin}]]}},
{restart_type,temporary},
{shutdown,1000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:49 ===
supervisor: {local,ejabberd_sup}
started: [{pid,<0.302.0>},
{name,ejabberd_mod_pubsub_localhost},
{mfa,
{mod_pubsub,
start_link,
["localhost",
[{access_createnode,pubsub_createnode},
{plugins,["default","pep"]}]]}},
{restart_type,transient},
{shutdown,1000},
{child_type,worker}]
=PROGRESS REPORT==== 10-Mar-2008::12:40:49 ===
application: ejabberd
started_at: ejabberd@localhost
"
-------------------------------
3) a crash dump file called
erl_crash_20080310-153313.dump
so then I tried running the commands you recommend, this is how that session went
C:\>telnet localhost 5222
aaaaa
<?xml version='1.0'?>
Connection to host lost.
C:\>
---------------------------------------
then I tried the ejjaberctl live command
and the session went like this
C:\Program Files\ejabberd-2.0.0\bin>bash ./ejabberdctl live
--------------------------------------------------------------------
IMPORTANT: ejabberd is going to start in LIVE (interactive) mode.
All log messages will be shown in the command shell.
You can interact with the ejabberd node if you know how to use it.
Please be extremely cautious with your actions,
and exit immediately if you are not completely sure.
To exit this LIVE mode and stop ejabberd, press:
q(). and press the Enter key
Press any key to continue
{error_logger,{{2008,3,10},{15,55,24}},"Protocol: ~p: register error: ~p~n",["inet_tcp",{{badmatch,{error,duplicate_name
}},[{inet_tcp_dist,listen,1},{net_kernel,start_protos,4},{net_kernel,start_protos,3},{net_kernel,init_node,2},{net_kerne
l,init,1},{gen_server,init_it,6},{proc_lib,init_p,5}]}]}
{error_logger,{{2008,3,10},{15,55,24}},crash_report,[[{pid,<0.20.0>},{registered_name,net_kernel},{error_info,{error,bad
arg}},{initial_call,{gen,init_it,[gen_server,<0.17.0>,<0.17.0>,{local,net_kernel},net_kernel,{'ejabberd@localhost',short
names,15000},[]]}},{ancestors,[net_sup,kernel_sup,<0.8.0>]},{messages,[]},{links,[#Port<0.8>,<0.17.0>]},{dictionary,[{lo
ngnames,false}]},{trap_exit,true},{status,running},{heap_size,233},{stack_size,21},{reductions,459}],[]]}
{error_logger,{{2008,3,10},{15,55,24}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reaso
n,{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfa,{net_kernel,start_link,[['ejabberd@localhos
t',shortnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2008,3,10},{15,55,24}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{re
ason,shutdown},{offender,[{pid,undefined},{name,net_sup},{mfa,{erl_distribution,start_link,[]}},{restart_type,permanent}
,{shutdown,infinity},{child_type,supervisor}]}]}
{error_logger,{{2008,3,10},{15,55,24}},crash_report,[[{pid,<0.7.0>},{registered_name,[]},{error_info,{shutdown,{kernel,s
tart,[normal,[]]}}},{initial_call,{application_master,init,[<0.5.0>,<0.6.0>,{appl_data,kernel,[application_controller,er
l_reply,auth,boot_server,code_server,disk_log_server,disk_log_sup,erl_prim_loader,error_logger,file_server_2,fixtable_se
rver,global_group,global_name_server,heart,init,kernel_config,kernel_sup,net_kernel,net_sup,rex,user,os_server,ddll_serv
er,erl_epmd,inet_db,pg2],undefined,{kernel,[]},[application,application_controller,application_master,application_starte
r,auth,code,code_aux,packages,code_server,dist_util,erl_boot_server,erl_distribution,erl_prim_loader,erl_reply,erlang,er
ror_handler,error_logger,file,file_server,file_io_server,prim_file,global,global_group,global_search,group,heart,hipe_un
ified_loader,inet6_tcp,inet6_tcp_dist,inet6_udp,inet_config,inet_hosts,inet_gethost_native,inet_tcp_dist,init,kernel,ker
nel_config,net,net_adm,net_kernel,os,ram_file,rpc,user,user_drv,user_sup,disk_log,disk_log_1,disk_log_server,disk_log_su
p,dist_ac,erl_ddll,erl_epmd,erts_debug,gen_tcp,gen_udp,gen_sctp,prim_inet,inet,inet_db,inet_dns,inet_parse,inet_res,inet
_tcp,inet_udp,inet_sctp,pg2,seq_trace,wrap_log_reader,zlib,otp_ring0],[],infinity,infinity},normal]}},{ancestors,[<0.6.0
>]},{messages,[{'EXIT',<0.8.0>,normal}]},{links,[<0.6.0>,<0.5.0>]},{dictionary,[]},{trap_exit,true},{status,running},{he
ap_size,987},{stack_size,21},{reductions,2063}],[]]}
{error_logger,{{2008,3,10},{15,55,24}},std_info,[{application,kernel},{exited,{shutdown,{kernel,start,[normal,[]]}}},{ty
pe,permanent}]}
{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}
}"}
Crash dump was written to: ../logs/erl_crash_20080310-155514.dump
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}}
)
C:\Program Files\ejabberd-2.0.0\bin>
---------------------------------------------
I do have to mention that on a previous install this command did run and did run the simple commands such as 3+7. and ets:tab2list(config). this is the first time its doing this.
the last line of sasl.log is
=PROGRESS REPORT==== 10-Mar-2008::12:40:49 ===
application: ejabberd
started_at: ejabberd@localhost
just like the one you mentioned.
-------------------------------------
I just realized that the erl process was running (there was no beam process) so I killed it and tried the ejabberctl command again...this are the results
--------------------------------
C:\Program Files\ejabberd-2.0.0\bin>bash ./ejabberdctl live
--------------------------------------------------------------------
IMPORTANT: ejabberd is going to start in LIVE (interactive) mode.
All log messages will be shown in the command shell.
You can interact with the ejabberd node if you know how to use it.
Please be extremely cautious with your actions,
and exit immediately if you are not completely sure.
To exit this LIVE mode and stop ejabberd, press:
q(). and press the Enter key
--------------------------------------------------------------------
Press any key to continue
Eshell V5.5.5 (abort with ^G)
(ejabberd@localhost)1>
=INFO REPORT==== 10-Mar-2008::15:59:20 ===
I(<0.299.0>:mod_pubsub:152) : pubsub init "localhost" [{access_createnode,
pubsub_createnode},
{plugins,
["default","pep"]}]
(ejabberd@localhost)1>
=INFO REPORT==== 10-Mar-2008::15:59:20 ===
I(<0.299.0>:mod_pubsub:207) : ** tree plugin is nodetree_default
(ejabberd@localhost)1>
=INFO REPORT==== 10-Mar-2008::15:59:20 ===
I(<0.299.0>:mod_pubsub:211) : ** init default plugin
(ejabberd@localhost)1>
=INFO REPORT==== 10-Mar-2008::15:59:20 ===
I(<0.299.0>:mod_pubsub:211) : ** init pep plugin
(ejabberd@localhost)1> 5+7.
12
(ejabberd@localhost)2> ets:tab2list(config).
[{config,language,"en"},
{config,{access,c2s,global},[{deny,blocked},{allow,all}]},
{config,{access,pubsub_createnode,global},[{allow,all}]},
{config,{access,s2s_shaper,global},[{fast,all}]},
{config,{access,c2s_shaper,global},[{none,admin},{normal,all}]},
{config,hosts,["localhost"]},
{config,{access,muc,global},[{allow,all}]},
{config,{shaper,fast,global},{maxrate,50000}},
{config,{access,max_user_sessions,global},[{10,all}]},
{config,{access,configure,global},[{allow,admin}]},
{config,{shaper,normal,global},{maxrate,1000}},
{config,{access,muc_admin,global},[{allow,admin}]},
{config,{access,announce,global},[{allow,admin}]},
{config,{access,register,global},[{allow,all}]},
{config,{access,local,global},[{allow,local}]}]
(ejabberd@localhost)3>
(ejabberd@localhost)3> q().
ok
(ejabberd@localhost)4>
C:\Program Files\ejabberd-2.0.0\bin>
---------------------------------
OK this all the information I have...I have tried this on the server which is a VPS running windows 2003 server under the virtuozzo control panel...I have also run it on my local machine which is a vista ultimate machine. They are on completely different networks (one machine is in the USA on a datacenter the other is local in my house). I get pretty much the same results on both. Each is running a completely different set of software, and neither had a firewall or an antivirus running during the testing.
I also tried using a browser to go to locaholst:5280/admin and I do get the http authentication windows but have not been able to log on with any of the combinations of username password (with @locahost and without for the username).
A CRY FOR HELP......ive been trying for two weeks now.
thanks!
-guillermo
Initial crash, manual start waiting, and create your admiaccount
With all the detailed information you provided, I constructed this explanation:
It installs fine, but on the last step of the installation it takes
a long long time...but does install eventually.
The installation process first copies files. Later it starts ejabberd, and tries to create the admin account. Then it stops ejabberd and finishes. It seems ejabberd crashed during this initial start.
-------------------------------
3) a crash dump file called
erl_crash_20080310-153313.dump
This crash dump was generated by an ejabberd that was started at 15:33. If you look at the file time, it should say 15:33, or 15:34 or similar. I think this dump was generated by the initial ejabberd start. So, your admin account couldn't be created.
Then I double click on the "start ejabberd" shortcut in the desktop.
It opnes the console and says "starting ejabberd..." and then takes a very long time (about 5 minutes) until I get a response (the machine is a fast machine with 1GB of ram)
The response is a web page that says:
"
Error occured...
Please check your configuration and your installation.
...
"
2)sasl.log
"
...
=PROGRESS REPORT==== 10-Mar-2008::12:40:49 ===
application: ejabberd
started_at: ejabberd@localhost
"
The first time you start ejabberd manually, it takes 5 minutes to show something, but it doesn't consume CPU, right? The logs indicate that ejabberd started correctly. I don't know why it took so much time to start, but at least it seems to start correctly.
so then I tried running the commands you recommend, this is how that session went
C:\>telnet localhost 5222
aaaaa
<?xml version='1.0'?>
Connection to host lost.
C:\>
So, ejabberd is started correctly, and you can connect to it. In fact, ejabberd complains that 'aaaaa' is xml not well formed :)
---------------------------------------
then I tried the ejjaberctl live command
and the session went like this
C:\Program Files\ejabberd-2.0.0\bin>bash ./ejabberdctl live
--------------------------------------------------------------------
IMPORTANT: ejabberd is going to start in LIVE (interactive) mode.
All log messages will be shown in the command shell.
You can interact with the ejabberd node if you know how to use it.
Please be extremely cautious with your actions,
and exit immediately if you are not completely sure.
To exit this LIVE mode and stop ejabberd, press:
q(). and press the Enter key
Press any key to continue
{error_logger,{{2008,3,10},{15,55,24}},"Protocol: ~p: register error: ~p~n",["inet_tcp",{{badmatch,{error,duplicate_name
}},[{inet_tcp_dist,listen,1},{net_kernel,start_protos,4},{net_kernel,start_protos,3},{net_kernel,init_node,2},{net_kerne
}"}
Crash dump was written to: ../logs/erl_crash_20080310-155514.dump
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}}
)
That's a normal error: ejabberd was already started, and then you tried to start it again, so the second ejabberd crashed and complained that it was already running (error, duplicate_name).
I do have to mention that on a previous install this command did run and did run the simple commands such as 3+7. and ets:tab2list(config). this is the first time its doing this.
As you already had ejabberd started, the second time you try to start it, it complains.
the last line of sasl.log is
=PROGRESS REPORT==== 10-Mar-2008::12:40:49 ===
application: ejabberd
started_at: ejabberd@localhost
just like the one you mentioned.
Those messages were written by the first ejabberd you started, which was started correctly.
-------------------------------------
I just realized that the erl process was running (there was no beam process) so I killed it and tried the ejabberctl command again...this are the results
--------------------------------
C:\Program Files\ejabberd-2.0.0\bin>bash ./ejabberdctl live
--------------------------------------------------------------------
IMPORTANT: ejabberd is going to start in LIVE (interactive) mode.
All log messages will be shown in the command shell.
You can interact with the ejabberd node if you know how to use it.
Please be extremely cautious with your actions,
and exit immediately if you are not completely sure.
To exit this LIVE mode and stop ejabberd, press:
q(). and press the Enter key
--------------------------------------------------------------------
Press any key to continue
Eshell V5.5.5 (abort with ^G)
(ejabberd@localhost)1>
=INFO REPORT==== 10-Mar-2008::15:59:20 ===
I(<0.299.0>:mod_pubsub:152) : pubsub init "localhost" [{access_createnode,
pubsub_createnode},
{plugins,
["default","pep"]}]
(ejabberd@localhost)1>
=INFO REPORT==== 10-Mar-2008::15:59:20 ===
I(<0.299.0>:mod_pubsub:207) : ** tree plugin is nodetree_default
(ejabberd@localhost)1>
=INFO REPORT==== 10-Mar-2008::15:59:20 ===
I(<0.299.0>:mod_pubsub:211) : ** init default plugin
(ejabberd@localhost)1>
=INFO REPORT==== 10-Mar-2008::15:59:20 ===
I(<0.299.0>:mod_pubsub:211) : ** init pep plugin
(ejabberd@localhost)1> 5+7.
12
(ejabberd@localhost)2> ets:tab2list(config).
[{config,language,"en"},
{config,{access,c2s,global},[{deny,blocked},{allow,all}]},
{config,{access,pubsub_createnode,global},[{allow,all}]},
{config,{access,s2s_shaper,global},[{fast,all}]},
{config,{access,c2s_shaper,global},[{none,admin},{normal,all}]},
{config,hosts,["localhost"]},
{config,{access,muc,global},[{allow,all}]},
{config,{shaper,fast,global},{maxrate,50000}},
{config,{access,max_user_sessions,global},[{10,all}]},
{config,{access,configure,global},[{allow,admin}]},
{config,{shaper,normal,global},{maxrate,1000}},
{config,{access,muc_admin,global},[{allow,admin}]},
{config,{access,announce,global},[{allow,admin}]},
{config,{access,register,global},[{allow,all}]},
{config,{access,local,global},[{allow,local}]}]
(ejabberd@localhost)3>
(ejabberd@localhost)3> q().
ok
(ejabberd@localhost)4>
C:\Program Files\ejabberd-2.0.0\bin>
---------------------------------
This time you killed the first ejabberd. So now you didn't have any ejabberd running. When you tried to start ejabberd using the Live command, it started correctly, and you could play with it.
I also tried using a browser to go to locaholst:5280/admin and I do get the http authentication windows but have not been able to log on with any of the combinations of username password (with @locahost and without for the username).
So, at this time ejabberd was running correctly, because you can connect to him. And you tried to enter the web admin providing information of a Jabber account that doesn't exist: remember that the initial ejabberd crashed and the installation couldn't create an admin account.
Summary:
Summary: * I don't know
No idea, but the same thing happens on my local vista machine...the online thing in common
these two machines have is that I am doing the double clicking during the install. They
are completely different (win2003server vs vista ultimate), on different networks (datacenter vs
local network), different software, etc....weird
only happnens with the start.bat file with the live option it starts inmediately and then takes about 10 seconds from the moment it says "press any key to continue" until I can actually give it commands.
I edited the start.bat file to remove the echo off command
and then ran it again...the results dont say much, but it does seem to go through the whole thing.
C:\Program Files\ejabberd-2.0.0\bin>start.batC:\Program Files\ejabberd-2.0.0\bin>echo Starting ejabberd...
Starting ejabberd...
C:\Program Files\ejabberd-2.0.0\bin>cd /D "C:\Program Files\ejabberd-2.0.0\bin"
C:\Program Files\ejabberd-2.0.0\bin>bash ./ejabberdctl start
C:\Program Files\ejabberd-2.0.0\bin>bash ./ejabberdctl started
C:\Program Files\ejabberd-2.0.0\bin>if errorlevel 1 goto error
C:\Program Files\ejabberd-2.0.0\bin>rundll32.exe url.dll,FileProtocolHandler "C:\Program Files\ejabberd-2.0.0\doc\error.html"
C:\Program Files\ejabberd-2.0.0\bin>
the only insightful thing I can tell you from this experiment is that the 5 minutes it gets
stuck happens right after running the "ejabberdctl startTED" line. Its something in there
that its not liking. The erl process starts right away.
I tried this using tkjabber client and indeed your asumption is correct. I created the admin account and then was able to log in through the browser. I was also able to create a couple of users and talk to each other using 2 instances of tkjabber client on the same machine... the did communicate but when I added one user to my roster I didnt get a popup or message on the other client asking for permission. That is probably something I have to configure.
Do you think that if I got this far I should be safe and run this server? Or should I not risk it because of the weird behavior with the crashes, and errors with no corresponding error in the log?
thanks again for all the help you are providing me, I really really really appreciate it.
-guillermo
PS.- could it be a permissions thing? could it be some folder or file does not have the correct permisssions? Maybe the server is not allowed to write somewhere and that is why the admin account is not being created? or maybe a windows service that should be running is not running?