Project

General

Profile

HTTP API help and broken link in the documentation

Matt Q Public
Added over 1 year ago

I just installed Tigase Server and got it running on a Debian (mint) box. My understanding is that there is some sort of web-admin UI available to me if I load the HTTP API Component. So, I looked in the documentation, and found this page:

http://docs.tigase.org/tigase-server/7.1.0/Administration_Guide/webhelp/_requirements.html

There, it says I need to download a file named "servlet-api-3.1.jar", but the download link is broken.

How do I get the web admin console working?


Replies (21)

Added by Matt Q Public over 1 year ago

Also, when I run Tigase Server and check open ports using netstat, I don't see that the server has opened ports 5222 or 5269.

Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

Hi Matt,

The old jar is no longer needed for many builds of tigase, that file should be in the /jars directory of your installation.

Did you configure HTTP API component to run? Please indicate which version you are using, the method of installation, and your current init.properties or dsl.config.

Added by Matt Q Public over 1 year ago

Hi Daniel,

The version is 7.1.1-b4457

I don't see that old file in my /jars directory, but there is a file called "tigase-http-api.jar".

There is also a "tigase-web-ui.war" file in there too.

I did a default installation on a VirtualBox VM running Linux Mint 17.3.

Then I modified my init.properties to add the http-api.

Here it is:

--comp-class-1 = tigase.muc.MUCComponent

--virt-hosts = myServerVM

--user-db-uri = jdbc:derby:/home/myUsername/TigaseXmppServer/Tigase-7.1.1-b4457/tigasedb

--user-db = derby

--admins = admin@myServerVM

--comp-name-5 = http

--comp-name-4 = message-archive

--comp-name-3 = proxy

config-type = --gen-config-def

--comp-name-2 = pubsub

--comp-name-1 = muc

--cluster-mode = true

--sm-plugins = +message-archive-xep-0136

--debug = server

--comp-class-4 = tigase.archive.MessageArchiveComponent

--comp-class-3 = tigase.socks5.Socks5ProxyComponent

--comp-class-2 = tigase.pubsub.PubSubComponent

--comp-class-5 = tigase.http.HttpMessageReceiver

Thanks for helping!

Added by Matt Q Public over 1 year ago

Bump. Any ideas about what might be wrong?

Avatar?id=6023&size=32x32

Added by Artur Hefczyc TigaseTeam over 1 year ago

Which Tigase package file exactly did you use? dist-max? And how exactly did you install the Tigase?

Avatar?id=6023&size=32x32

Added by Artur Hefczyc TigaseTeam over 1 year ago

By the way Matt, your email address you used to register on our website seems to be no longer working. Email is bouncing back with message: "550 Mail is rejected by recipients."

Added by Matt Q Public over 1 year ago

Hi Artur. I just saw your reply now. The notifications were getting caught in a spam filter.

That should be fixed now. If not, I'll change the email address for this account.

I installed Tigase Server using the JAR file, "tigase-server-7.1.1-b4457.jar"

It was installed on a fully updated Linux Mint 17.3 VirtualBox VM, running Oracle Java 1.8.0_144

Thanks.

Added by Matt Q Public over 1 year ago

I wiped and reinstalled. Same result. This is probably user error, but I don't know what I'm doing wrong. How am I supposed to access the admin page? Is it http://localhost:8080/ui/ ?

Added by Matt Q Public over 1 year ago

This is what my new init looks like:

--comp-class-1 = tigase.muc.MUCComponent

--virt-hosts = myServerVM

--user-db-uri = mongodb://localhost:27017

--user-db = tigase.mongodb.MongoRepository

--auth-db = tigase.mongodb.MongoRepository

--admins = admin@myServerVM

--comp-name-5 = http

--comp-name-4 = message-archive

--comp-name-3 = proxy

config-type = --gen-config-all

--comp-name-2 = pubsub

--comp-name-1 = muc

--cluster-mode = true

--sm-plugins = +message-archive-xep-0136

--debug = server

--comp-class-5 = tigase.http.HttpMessageReceiver

--comp-class-4 = tigase.archive.MessageArchiveComponent

--comp-class-3 = tigase.socks5.Socks5ProxyComponent

--comp-class-2 = tigase.pubsub.PubSubComponent

Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

The admin page should be located at

http://localhost:8080/admin/

Are you able to get to the logon screen? If you are having issues logging in, check the log file for activity, it may reveal some information as to what is wrong.

Also it sometimes helps to specify the Bosh session under Advanced Options on the login page. This will be localhost:5280

Added by Matt Q Public over 1 year ago

No matter how I try to connect to Tigase Server I get "Unable to Connect" in my browser, which is Firefox. See attached screenshot.

I'm unable to get to a logon screen or any Tigase screen at all. There is no evidence that the Tigase server is running except for the logs, which only contain the following:

STARTED Tigase Sun Oct 8 20:37:48 EDT 2017

STOPPED Sun Oct 8 20:38:05 EDT 2017

STARTED Tigase Sun Oct 8 20:39:13 EDT 2017

STOPPED Sun Oct 8 20:40:21 EDT 2017

STARTED Tigase Sun Oct 8 20:45:18 EDT 2017

STOPPED Sun Oct 8 20:46:00 EDT 2017

STARTED Tigase Sun Oct 8 20:48:22 EDT 2017

STOPPED Sun Oct 8 20:49:28 EDT 2017

STARTED Tigase Sun Oct 8 21:26:16 EDT 2017

STOPPED Sun Oct 8 21:28:01 EDT 2017

STARTED Tigase Sun Oct 8 21:39:20 EDT 2017

STOPPED Sun Oct 8 21:40:08 EDT 2017

STARTED Tigase Sun Oct 8 21:40:42 EDT 2017

STOPPED Sun Oct 8 21:41:46 EDT 2017

STARTED Tigase Sun Oct 8 21:45:18 EDT 2017

STOPPED Sun Oct 8 21:46:52 EDT 2017

STARTED Tigase Sun Oct 8 21:48:16 EDT 2017

STOPPED Sun Oct 8 21:48:49 EDT 2017

STARTED Tigase Sun Oct 8 22:00:12 EDT 2017

STOPPED Sun Oct 8 22:01:10 EDT 2017

I've been reading this documentation:

http://docs.tigase.org/tigase-server/7.1.0/Administration_Guide/html/

Is that the proper & current documentation?

Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

There is some updated documentation here: http://docs.tigase.org/tigase-server/stable-snapshot/Administration_Guide/html/ although most of the updates are for the later versions. The server seems to have some issues staying active, this could be a configuration error. Can you attach console-log the tigase.log.0?

Added by Matt Q Public over 1 year ago

I'm not seeing any "tigase.log" files anywhere.

Can you look at my init.properties file (posted above) and let me know if you see anything wrong. I don't think the web server is running at all. That might be the issue.

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam over 1 year ago

All your logs file should be stored in logs directory within you Tigase XMPP Server installation directory.

As for you init.properties file, it looks ok. I've deployed Tigase on my machine using the same installer as you did and all is working fine.

This log which you provided, where it is from? A file? Is it a console output? If so, then what command you used?

Added by Matt Q Public over 1 year ago

The only log I see is "tigase-console.log" which is in the /logs folder.

When Tigase Server is running, the /logs folder contains:

tigase.pid

tigase-console.log

When Tigase Server is not running, the /logs folder only contains:

tigase-console.log

The information I provided above is from "tigase-console.log", which only seems to log when the server is started or stopped. There is no debug information.

Question: In what directory did you install Tigase Server? During installation, I accepted the default setting, which placed it in my home directory.

Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

You're certainly right, something is preventing the program from doing --really anything. If console.log has nothing but startup and shutdown listings, nothing is happening. Have you tried running the server with sudo privileges? You mentioned it was installed in your home directory, is it like home/tigase or directly into the home dir?

Added by Matt Q Public over 1 year ago

I have it installed in /home/[myUsername]/TigaseServer/Tigase-7.1.1-b4457/

Your information helps me. When I echo $JAVA_HOME as my user, I get the correct response. When I echo it as root, I get a blank response.

When I try to sudo start the server from the command line, I get a message that JAVA_HOME is not set. I guess Tigase is trying to run using global settings, not user settings, and that's the problem.

I'll try to get it sorted out later and will update this thread when resolved.

Thanks for all your help. Coming from Openfire, actually having someone respond to me is refreshing.

Added by Matt Q Public over 1 year ago

Okay... In the "tigase.conf" file there was one single "/" at the start of the JAVA_HOME path. It wasn't supposed to be there. I didn't put it there because I never edited that file.

When I removed the "/" so my JAVA_HOME = "usr/lib/jvm/java-8-oracle" the Tigase Server started up, created a ton of logs, lots of errors, and then shut down. But this is much better than nothing.

I still cannot connect via HTTP because the server crashes, but I'm going to call this issue closed. I'll start other threads about specific errors as they come up.

Thanks again for your responses!

Avatar?id=6023&size=32x32

Added by Artur Hefczyc TigaseTeam over 1 year ago

The "/" should be there. The JAVA_HOME variable points to location where Java is installed on your machine and it should be a full path to the Java installation. Maybe, Java on your VM is located in a different directory. I suggest you to find it out and correct the JAVA_HOME variable. The easiest way to find location of your Java installation is:

 $ whereis java
java: /usr/bin/java /usr/share/java

But, the location returned is not real Java location, these are links to the binaries. So another command would show you the full path:

 $ ls -l /usr/bin/java
lrwxrwxrwx 1 root root 25 Mar 20  2014 /usr/bin/java -> /usr/lib/jvm/jdk/bin/java*

So in this case, the Java is installed in /usr/lib/jvm/jdk and JAVA_HOME should be set to this location:

JAVA_HOME=/usr/lib/jvm/jdk

Check this out on your system and correct settings.

Also, if you say you got tons of errors in your log files, please provide some. A few first errors are probably most important as all subsequent are probably consequence of the first problem.

Added by Matt Q Public over 1 year ago

I wiped the install and started fresh. Totally default install. I haven't changed anything except including the HTTP API during the installation process.

This is the problem...

When I start/stop Tigase Server from the desktop shortcuts that were created during the installation process, it does nothing. My tigase-console.log contains only things like:

STARTED Tigase Tue Oct 10 19:12:42 EDT 2017

STOPPED Tue Oct 10 19:13:03 EDT 2017

If I start/stop Tigase Server from the command line (using the exact same command the desktop shortcut uses), it looks like it's working properly. I actually get output to my logs, like:

...(removed for brevity)...

ws2s/adhoc-command/del-script last minute[L] = 0

ws2s/adhoc-command/del-script last second[L] = 0

ws2s/adhoc-command/del-script/Average processing time[L] = 0

ws2s/adhoc-command/list-commands last hour[L] = 0

ws2s/adhoc-command/list-commands last minute[L] = 0

ws2s/adhoc-command/list-commands last second[L] = 0

ws2s/adhoc-command/list-commands/Average processing time[L] = 0

ws2s/adhoc-command/add-script last hour[L] = 0

ws2s/adhoc-command/add-script last minute[L] = 0

ws2s/adhoc-command/add-script last second[L] = 0

ws2s/adhoc-command/add-script/Average processing time[L] = 0

ws2s/Open connections[I] = 0

ws2s/Waiting to send[I] = 0

ws2s/Bytes sent[L] = 0

ws2s/Bytes received[L] = 0

ws2s/Socket overflow[L] = 0

ws2s/Watchdog runs[L] = 0

ws2s/Watchdog tests[L] = 0

ws2s/Watchdog stopped[L] = 0

total/Total queues wait[I] = 0

total/Total queues overflow[L] = 0

Total number of threads: 215

No locked threads.

Save thread-dump to file: logs/thread-dump.log, size: 94347

ShutdownThread finished...

STOPPED Tue Oct 10 18:45:41 EDT 2017

That appears to be working correctly, but the desktop shortcuts don't work. That caused quite a bit of trouble to figure out.

I was able to connect to the server with an XMPP client using the local IP address of the server.

I have not tried to use the HTTP API yet.

Should I start a different thread about the desktop shortcuts, or keep going here?

Added by Matt Q Public over 1 year ago

HTTP API is working now. Thanks.

    (1-21/21)