Project

General

Profile

Where to start after installation?

Jairo Junior
Added over 1 year ago

Hello everyone!

I installed Tigase XMPP Server with the options below in a Windows 7 computer (please see the attachments).

But now I'm a little confuse about where to start.

I thought that I would find a web admin panel or something like to manage the server and accounts (like OpenFire) but I've no clue how to do this now.

Someone can give me an light?

Thanks in advance.


Replies (6)

Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

Hi Jairo,

Our HTTP component provides a web-based configuration method. When your server is running go to

http://localhost:8080/admin/

on your browser and login with the admin JID and password you used during setup. This should provide you access to the administration panel.

http://localhost:8080/ui/ provides access to the web-based client.

Added by Jairo Junior over 1 year ago

Hi, Daniel,

I tried this but seems that there's no webserver running.

Also I tried to login using the Spark XMPP client but without success.

Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

After setup, Tigase XMPP Server is not installed as a service, so it has to be run as an application for first start.

Tigase is not really a native windows exe program, so no start menu or desktop icons were made during installation.

You can either use wrapper.exe or tigase.exe in the installation directory. Output for console log will be in /logs/wrapper.log

Have a look there to see if any warnings or errors pop up to indicate issues running the program.

Added by Jairo Junior over 1 year ago

After installation I see two shortcuts: "Manually Start Tigase" and "Install Tigase Windows Service". I tried both, first manually and so the Windows service.

I read the Log files and between many lines these below call my attention, seems that Tigase cannot launch JVM.

I tried to install jre and jdk 32 bits version but without success :|

STATUS | wrapper | 2017/05/25 08:50:12 | Launching a JVM...

ERROR | wrapper | 2017/05/25 08:50:44 | Startup failed: Timed out waiting for a signal from the JVM.

ERROR | wrapper | 2017/05/25 08:50:44 | JVM did not exit on request, termination requested.

STATUS | wrapper | 2017/05/25 08:50:46 | JVM exited after being requested to terminate.

STATUS | wrapper | 2017/05/25 08:50:51 | Launching a JVM...

INFO | jvm 2 | 2017/05/25 08:51:08 | WrapperManager: Initializing...

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager:

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: The file is located on the path at the following location but

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: could not be loaded:

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: C:\Tigase\jars\wrapper.dll

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: Please verify that the file is both readable and executable by the

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: current user and that the file has not been corrupted in any way.

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: One common cause of this problem is running a 32-bit version

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: of the Wrapper with a 64-bit version of Java, or vica versa.

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: This is a 64-bit JVM.

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: Reported cause:

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: C:\Tigase\jars\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager: System signals will not be handled correctly.

INFO | jvm 2 | 2017/05/25 08:51:21 | WrapperManager:

ERROR | wrapper | 2017/05/25 08:51:23 | Startup failed: Timed out waiting for a signal from the JVM.

ERROR | wrapper | 2017/05/25 08:51:23 | JVM did not exit on request, termination requested.

STATUS | wrapper | 2017/05/25 08:51:23 | JVM exited after being requested to terminate.

STATUS | wrapper | 2017/05/25 08:51:28 | Launching a JVM...

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: Initializing...

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager:

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: The file is located on the path at the following location but

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: could not be loaded:

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: C:\Tigase\jars\wrapper.dll

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: Please verify that the file is both readable and executable by the

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: current user and that the file has not been corrupted in any way.

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: One common cause of this problem is running a 32-bit version

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: of the Wrapper with a 64-bit version of Java, or vica versa.

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: This is a 64-bit JVM.

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: Reported cause:

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: C:\Tigase\jars\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager: System signals will not be handled correctly.

INFO | jvm 3 | 2017/05/25 08:51:28 | WrapperManager:

Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

Verify that tigase.conf is pointing to the right location for JVM.

Which version of JDK did you install? It should be at least v8

Added by Jairo Junior over 1 year ago

Yes, I already (1) verify the path to JDK folder in tigase.conf

"C:\Program Files (x86)\Java\jdk1.8.0_131\bin\java" -cp "jars/*" -Djdbc.drivers=com.mysql.jdbc.Driver tigase.server.XMPPServer --property-file etc/init.properties

and (2) I put the complete path to java.exe in Run.bat and (3) reinstall Tigase but none works.

JAVA_HOME="C:\Program Files (x86)\Java\jdk1.8.0_131"

CLASSPATH=""

#PRODUCTION_HEAP_SETTINGS=" -Xms5G -Xmx5G " # heap memory settings must be adjusted on per deployment-base!

JAVA_OPTIONS="${GC} ${GC_DEBUG} ${EX} ${ENC} ${DRV} ${JMX_REMOTE_IP} -server ${PRODUCTION_HEAP_SETTINGS} ${DNS_RESOLVER} ${INTERNAL_IP} ${EXTERNAL_IP} -XX:MaxDirectMemorySize=128m "

TIGASE_OPTIONS=" --property-file etc/init.properties "

Thank you, Daniel!

But nothing seems to work in Windows, now I'll try in a Raspberry with Debian.

Have a good day!

    (1-6/6)