Home » Forums » ejabberd & XMPP » ejabberd Administration

Latest Windows installer won't install on Windows XP - hangs in postinstall script.

Submitted by tbessie on Mon, 2008-10-27 02:50

I've been trying to install the latest version of ejabberd on several Windows XP boxes.

However, when it gets to the end of the installation, it hangs when it runs the postinstall script. In fact, in the very first line of the pathconv() function in the formatconfig.sh script. To be precise, the line:

FROM=$(grep "{$1" ejabberd.cfg | head -n 1 | cut -d'"' -f$2)

is hanging for one of the lines of input it's getting from elsewhere in that script.

Has anyone seen this happen?

- Tim

‹ Ejabberd 2.0.2 installation with mod_rabbitmq how to make groups and let new user to choose among them ? ›

Does 2.0.1 installer complete correctly?

Submitted by mfoss on Mon, 2008-10-27 16:01.

I too have a problem with ejabberd 2.0.2_2 Windows installer. In my case the file C:\Windows\Temp\bitrock_installer.log says:

Executing final installation script
Error executing post installation script
C:\ejabberd-2.0.2_2f\bin\postinstall.bat
\epmd: Cannot connect to local epmd

If I uninstall this and install ejabberd 2.0.1, all works correctly.

The Windows installer performs four tasks:

  • Copy the files
  • Register the Windows service
  • Modify ejabberd.cfg with the settings introduced during the installation: hostname, username of admin account, path to SSL certificate...
  • Start ejabberd, register a Jabber account (for the admin), and stop ejabberd

So, even if postinstall fails, ejabberd can be used.

Regarding your case: there wasn't any change in formatconfig.sh since ejabberd 2.0.1. What happens if you install ejabberd 2.0.1?

BTW, there is another problem report of Windows installer: "Error running Post Install Script" with ejabberd-2.0.2_2-windows-installer.exe

»

I just tried 2.0.1 - fails as well

Submitted by tbessie on Wed, 2008-10-29 18:58.

I just tried installing 2.0.1, and it fails around the same place as well (within the postinstall script). I was surprised, since I've seen other people saying that it worked for them.

I couldn't find that log file you mention, tho'.

By the way, after I canceled the 2.0.1 installation, I tried installing 2.0.2 again, and THIS time it worked. I don't know if the attempted 2.0.1 installation fixed something, or if it is merely a timing issue, and this time it worked, I don't know, but installation completed.

By the way, during the 2.0.1 installation, my virus software kept telling me it saw signs of a virus in the 2.0.1 files. Ever see that before?

- Tim

»
Syndicate content

User login