Problems when upgrading from 3.0.1 to 3.1.0

I had a working 3.0.1 server and all plugins installed (on Windows). It uses LDAP and MSSQL database. When upgraded on 3.1.1 all my users lost their rosters. When i deinstall it and go again on 3.0.1 all plugins (which was updated on new versions) stop working. Now i can’'t get old version of plugins. Do not try to update if it works …

backups, backups, backups. Even if you’'re upgrading your own program So what plugins do you need? I can share, still have old versions. Though there should be old plugins somewhere at this page.

Here, all plugins for 3.0.1:

http://rapidshare.de/files/36369183/plugins.zip.html

Keep in mind, JS.org is known by their community

Hmm, maybe we can come up with a way of offering old plugins somehow. The current infrastructure doesn’'t make it that easy though.

I’‘m definitely concerned about the upgrade issue – lost rosters?? We’'ve definitely never heard of any issues like that. Anything in your error logs?

Regards,

Matt

Matt, shouldnt you be at the conference now?

I’'m sitting in a talk at the moment with a laptop. How could I stay away?

-Matt

warn log:

Closing session due to incorrect hostname in stream header. Host: 127.0.0.1. Connection: org.jivesoftware.wildfire.net.SocketConnection@1b9808e socket: Socket[addr=/127.0.0.1,port=48048,localport=5269] session: null

Just upgraded to 3.1 and all users show their respective contacts in the lists but all are offline. We backported to 3.0.1 and are seeing the same problem. We can successfully login to the wildfire server and I show multiple user sessions online but the presence is offline for everyone.

edit: would i then be missing some of the original plugins such as presence which would enable this?

Message was edited by: theredthreat

edit: I have successfully downloaded a zip file of the plugins from the address listed above in this thread.

Message was edited by: theredthreat

All rosters have been from ldap groups, so i change filters in searchgroups iand searchuser and it worked.

I switch to new version, install plugins, and now all works but vcard mapping.

What need to be changed in vcard mapping?

Upgrading for me has not been an easy process. I’'m holding off on going to 3.1.0 until I can get some office downtime. Every time I need to upgrade, I always wind up having to rewrite and reconfigure my wildfire.xml file. Granted, I always have a backup, but a simple, streamlined upgrade would be great, if possible.

vCard mapping – the syntax had to change to simplify the file. See the release announcement or LDAP docs for more information.

On upgrades in general: we definitely want to make them as easy as possible. We’‘ve been talking about an auto-upgrade/backup system where it would download just updated files for Wildfire, backup your existing configuration, then auto-update the next time you restart the server. We’‘re doing some initial planning now and it’‘s something we’'d love to have in place for 3.2.

Regards,

Matt

Fixed our problem of offline contacts by deleting them all and adding back in. Noticed that the contacts jabberid went from username@127.0.0.1 to username@server.company.org

My webchat plugins does not seems to work now. It always has a connection problem

Hey sleeping,

Do you see any relevant in the log files? We need more info to be able to help you.

Regards,

– Gato

I check the LDAP documentation, but it’'s for old version.

It still says that searchfilter is (sAMAccountName=) but it’'s not in 3.1.0…it seems that this is documentation for old version.

This is the reslut when i do a test connection.

Server Connection Test

Results: XMPPError connecting to joim.dyndns.biz:5223.: (502) – caused by: java.net.ConnectException: Connection timed out: connect at org.jivesoftware.smack.XMPPConnection.(XMPPConnection.java:271) at org.jivesoftware.smack.SSLXMPPConnection.(SSLXMPPConnection.java:92) at org.jivesoftware.smack.SSLXMPPConnection.(SSLXMPPConnection.java:76) at com.jivesoftware.webclient.jsp.test_002dconnection_jsp._jspService(test_002dcon nection_jsp.java:57) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:830) at com.jivesoftware.webchat.SetCharacterEncodingFilter.doFilter(SetCharacterEncodi ngFilter.java:44) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821) at com.jivesoftware.webchat.SetupFilter.doFilter(SetupFilter.java:91) 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) Nested Exception: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(Unknown Source) at org.jivesoftware.smack.SSLXMPPConnection$DummySSLSocketFactory.createSocket(SSL XMPPConnection.java:149) at org.jivesoftware.smack.XMPPConnection.(XMPPConnection.java:262) at org.jivesoftware.smack.SSLXMPPConnection.(SSLXMPPConnection.java:92) at org.jivesoftware.smack.SSLXMPPConnection.(SSLXMPPConnection.java:76) at com.jivesoftware.webclient.jsp.test_002dconnection_jsp._jspService(test_002dcon nection_jsp.java:57) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:830) at com.jivesoftware.webchat.SetCharacterEncodingFilter.doFilter(SetCharacterEncodi ngFilter.java:44) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821) at com.jivesoftware.webchat.SetupFilter.doFilter(SetupFilter.java:91) 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)

I also found that my network has to be switch on and the network router has to allow port 5223 to be open. and not only on the network on the pc.

I’‘m having the same problem now (with the roster disappearing for all users after the upgrade). I’‘m trying to figure out what the definite fix is for this, but I’‘m not seeing anything in this thread that jumps out at me as the final answer. Is there a definitive fix for this issue? I’‘d like to get my users back up and running soon, so if anyone has the answer, I’'d really appreciate your help. Thanks.

i had to have my users remove their roster contacts and readd them manually with the jabberid as jabberid@yourwildfireserver.com

there is a subscription plugin that can automatically allow the request fulfillment of contacts once the contact is requested rather than wait for manual acceptance.

theredthreat wrote:

i had to have my users remove their roster contacts and readd them manually with the jabberid as jabberid@yourwildfireserver.com

The group I use is automatically populated from LDAP/AD, plus I can’‘t really tell everyone in our organization to re-add everyone. I’‘m guessing that I probably need to make some simple change to the conf file to get things working again, but since it took days to get it working to begin with, I’‘m not terribly excited about making any changes to something that was already working. I don’'t know if it matters, but here is the current conf file LDAP block I am using (that has been working up until the upgrade):

  <N>
  <FAMILY attrs="sn"></FAMILY>














I did see in the old thread I had on this subject (when I was originally trying to get my LDAP piece working) that there were some suggested changes to my conf configuration, but since everything was working up until the upgrade, I’'m hesitant to make any changes unless someone can say a piece of the code is definitely what is causing the roster group to break. Again, thanks in advance to anyone that can help!

did you back up your wildfire.xml before the upgrade? you might try using that one

Hey,

Try removing the sAMAccountName section from your searchFilter. And also removing member section from groupSearchFilter. Those values are automatically added by Wildfire now. The vCard mapping is also outdated. May be you may want to rerun the setup pages to get them straight.

Let us know how it goes.

Thanks,

– Gato