General problems after installing Windows Installer Package.

Having a couple of issues:

1) Whenever I type any commands into the erl console included with the

installer, at first it appears like it is going to perform the command, but

it hangs up and doesn't do anything. The commands that I type into the erl

shell are right from the install manual for ejabberd.

2) Not able to find the erl cookie file anywhere, not even where the manual

says that it is. I have looked in: C:WINDOWS folder, C:WINDOWSSystem32

folder, and even in the ejabberd folder and connot find that cookie

anywhere.

3) I notice inside the ejabberd folder there is a 'ejabberdctl' file and

when I view it I can see the settings for the cookie among other settings,

but I'm not really sure what to do with it or how to use it.

Dot at the end

swright wrote:

1) Whenever I type any commands into the erl console included with the installer, at first it appears like it is going to perform the command, but it hangs up and doesn't do anything. The commands that I type into the erl shell are right from the install manual for ejabberd.

Note that the commands have a . at the end. For example:

$ erl -name aaa@bbb -setcookie RWR3434EREREapv
Erlang (BEAM) emulator version 5.5.4 [source] [async-threads:0] [hipe] [kernel-poll:false]

Eshell V5.5.4  (abort with ^G)
(aaa@bbb)1> time().
{8,49,44}
(aaa@bbb)2> erlang:get_cookie().
'RWR3434EREREapv'
(aaa@bbb)3>
swright wrote:

2) Not able to find the erl cookie file anywhere, not even where the manual
says that it is. I have looked in: C:WINDOWS folder, C:WINDOWSSystem32 folder, and even in the ejabberd folder and connot find that cookie anywhere.

3) I notice inside the ejabberd folder there is a 'ejabberdctl' file and when I view it I can see the settings for the cookie among other settings, but I'm not really sure what to do with it or how to use it.

The ejabberd 1.1.x Windows installers do not create a cookie file. As you noticed, it sets the cookie directly on the start script (ejabberdctl). Also, it is not a random cookie: it is always the string 'ejabberd'.

Maybe the next installer uses the method described on the guide.

ejabberctl

How do I go about setting up the start script in windows with the ejabberdctl?

Syndicate content