First install issues

Openfire Openfire Support
1

Hello,

I installed Wildfire Server on Windows XP and I am having a few issues.

The install seems to have gone fine but I can’‘t connect to the server. This is my first Jabber server install and I don’'t really know what exactly has to be done, so I am not sure what is going on.

The server is running, and I created users using the web admin interface. I tried connecting with iChat but it does not work. I tried connecting with Adium and it seems to connect, but I can’'t have any conversations with other users. I did not change any settings at all other than entering the host name and creating an admin username and password during installation.

Is there a resource on the web that can guide me step by step through an installation? The Wildfire documentation is not that detailed, and I don’'t really know where to go from here.

Any advice will help.

Thanks,

-Elie

2

Have you checked any of the error logs in the administrative interface? Since you are able to connect to the admin interface, I am assuming you don’'t have a firewall running but you may want to ensure none are running. Also, if you can post your wildfire.xml configuration file here in the forums, it will help others troubleshoot your problems (of course, take out sensitive information).

3

Hi Elie,

does the client work fine if you run it on the server where Wildfire is installed? Then you really need to open your firewall for the clients. Port 5222 is the standard xmpp port and thus the only one you need to open for (basic) IM as there are some other ports.

Do the clients fail to connect?

Is the xmpp.domain (server name) resolvable by the clients?

LG

4

Hello,

Here is the wildfire.xml I never modified this file, by the way. Do I have to put any personal settings in there?

Here are the logs. There appears to be something funny going on…

admin-console.log

15:45:14.703 WARN!! [Update Manager] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >04> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

15:45:14.796 WARN!! [Update Manager] org.apache.commons.httpclient.HttpMethodBase.getResponseBody(HttpMethodBase.jav a:676) >04> Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

16:23:17.546 WARN!! [SocketListener0-1] org.mortbay.http.HttpServer.doStop(HttpServer.java:742) >35> java.lang.InterruptedException: sleep interrupted

16:23:20.890 WARN!! [SocketListener0-1] org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:589) >11> /server-stopped.jsp:

java.lang.NullPointerException

at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:57)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.util.LocaleFilter.doFilter(LocaleFilter.java:65)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingF ilter.java:41)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler. java:471)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)

at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.ja va:633)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)

at org.mortbay.http.HttpServer.service(HttpServer.java:909)

at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)

at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)

at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)

at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)

at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)

at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

14:40:08.281 ERROR! [SocketListener0-1] uk.ltd.getahead.dwr.util.CommonsLoggingOutput.error(CommonsLoggingOutput.java:7 5) >40> Line=19 The content of element type “dwr” must match “(init?,allow?,signatures?)”.

error.log

2006.12.12 15:53:37 [org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(O utgoingServerSession.java:259)

] Error trying to connect to remote server: admin(DNS lookup: admin:5269)

java.net.UnknownHostException: admin

at java.net.PlainSocketImpl.connect(Unknown Source)

at java.net.SocksSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Ou tgoingServerSession.java:254)

at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(Outgo ingServerSession.java:140)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPac ket(OutgoingSessionPromise.java:130)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSess ionPromise.java:40)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSession Promise.java:95)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

warn.log

2006.12.14 10:01:17 TLS was required by the server and connection was never secured. Closing connection : org.jivesoftware.wildfire.net.SocketConnection@d844a9 socket: Socket[addr=/132.205.139.95,port=1169,localport=5222] session: org.jivesoftware.wildfire.ClientSession@1e9f5cc status: -1 address: havoc/52ad6b91 id: 52ad6b91 presence:

2006.12.14 10:03:15 TLS was required by the server and connection was never secured. Closing connection : org.jivesoftware.wildfire.net.SocketConnection@1505258 socket: Socket[addr=/132.205.139.95,port=1171,localport=5222] session: org.jivesoftware.wildfire.ClientSession@15fd251 status: -1 address: havoc/9210da97 id: 9210da97 presence:

2006.12.14 10:03:53 TLS was required by the server and connection was never secured. Closing connection : org.jivesoftware.wildfire.net.SocketConnection@1e8e144 socket: Socket[addr=/132.205.139.95,port=1172,localport=5222] session: org.jivesoftware.wildfire.ClientSession@c8e4de status: -1 address: havoc/ea75b776 id: ea75b776 presence:

Thank you for your help.

5

Hi,

The client seems to run fine either on the machine the host is installed on or on another machine on the network. I can connect to the server and the admin interface shows who is connected (under the users tab). However, when I try communicating with another user, that doesn’'t work.

Also, if the machine the server is running on is called havoc on the network, do the jabber logins have to be of the form name@havoc? Do I have to add a ‘’.xxx’’ like ‘’.com’’ or ‘’.org’’ after the host name, because I don’‘t think the machine is identified like that. And this server is only for internal use, so I don’‘t think it’'s necessary…

6

Hi Elie,

even if you use the server only internally all clients must be able to resolve its name. So if you set the server name (xmpp.domain) to havoc then your admin account will be “admin@havoc”.

If user “foo@havoc” wants to communicate with “admin” then it must always specify the full JID, thus “admin@havoc”. Otherwise the connection will fail as the server does not know where to connect to.

LG