So I tried running the installer (on Windows 7 Enterprise), all went well up until the very end and I get this:
---------------------------
Error
---------------------------
Error running Post Install Script.
The installation may have not completed correctly
---------------------------
OK
---------------------------
Why?
Not only that, but when I try to log into the admin site (which is hosted locally), it says that the password that I previously set is not recognized, again, why?
BTW, anyone know how to log into the bug track database for ejabberd and report this as an issue?
And why is it that when I try to create new content (including the create forum topic page), I see this?
"Crea un tema de debate nuevo en los foros."
I have my settings set to English.
![Syndicate content](../../misc/feed.png "Comments for \""Error running Post Install Script" with ejabberd-2.1.8-windows-installer.exe\""){kind=small}
ysg wrote: So I tried running
So I tried running the installer (on Windows 7 Enterprise), all went well up until the very end and I get this:
---------------------------
Error
---------------------------
Error running Post Install Script.
The installation may have not completed correctly
---------------------------
OK
---------------------------
Why?
There are many problems that provide this same error report, so it is very difficult to know what went wrong during your installation. Try to uninstall and remove ejabberd, stop processes: beam erl werl epmd
On the other hand, if installation completion fails, but ejabberd later works perfectly, you can continue using it anyway :)
Not only that, but when I try to log into the admin site (which is hosted locally), it says that the password that I previously set is not recognized, again, why?
Because the installation didn't complete, the account was not created. That isn't a big problem: you can create the account manually using ejabberdctl shell program, or using a Jabber client.
Thanks for your reply. I
Thanks for your reply.
I looked at the processes tab in my Windows Task Manager and have epmd.exe and erl.exe running. Are beam.exe and werl.exe not starting and this is causing the problem? How can I resolve this?
When I tried creating the user from the console, this is the issue that I ran into:
C:\Program Files\ejabberd-2.1.8\bin>ejabberdctl register admin localhost adminCan't register user admin@localhost at node ejabberd@localhost: not_allowed
Commands to start an ejabberd node:
start Start an ejabberd node in server mode
debug Attach an interactive Erlang shell to a running ejabberd node
live Start an ejabberd node in live (interactive) mode
ysg wrote: I looked at the
I looked at the processes tab in my Windows Task Manager and have epmd.exe and erl.exe running.
Ok, then erlang is running, and probably ejabberd too. Just look at the ejabberd log files.
When I tried creating the user from the console, this is the issue that I ran into:
Can't register user admin@localhost at node ejabberd@localhost: not_allowed
You try to register an account at "localhost", but maybe you don't have that vhost in ejabberd.cfg . Good example:
{hosts, ["localhost", "example.com"]}.
badlop wrote: Ok, then erlang
Ok, then erlang is running, and probably ejabberd too. Just look at the ejabberd log files.
Just did, I found a bunch of these: erl_crash_20110825-102419.dump
How can I attach one here? Or can I just dump it all here?
You try to register an account at "localhost", but maybe you don't have that vhost in ejabberd.cfg . Good example:
{hosts, ["localhost", "example.com"]}.
This is lame/weird. I just tried editing it and it said that I can't because another app could possibly be using that file.
Ok, I was just able to create
Ok, I was just able to create the user admin. However, when I tried to login as admin, no go, same error.
ysg wrote: when I tried to
when I tried to login as admin, no go, same error.
In the browser put as user:
Ok, that seemed to work. I'm
Ok, that seemed to work. I'm logged into ejabberd. I'll post here if I have any other issues.
Thanks for your help and I hope you weren't in hurricane Irene's path this weekend :) .