My first major problem is that I don’‘t think my database isn’'t upgrading. I originally was running Wildfire 2.6.2 deployed via an RPM (on Suse 10) with a MySQL 4.1.19 database, with authentication against OpenLDAP. Earlier this week I upgraded to Wildfire 3.0.0, and am having some slight issues. Firstly in the info log in the admin console, I keep seeing “Old database found version 8… Upgrading to 10…”. Now I suspect that the upgrading is a good thing, however the problem is that this message appears every single I startup the server.
Does this possibly mean that the database isn’'t actually being upgraded? Is this normal? if not, is there any way of manually making the upgrade of the database? I suspect that there is something broken as I installed wildfire 3.0.0 from a clean install on another server to act as a warm backup, and it deployed 29 tables, whereas the actual live server only has 28 tables. The missing table is a table starts with “SASL…” (sorry I forgot the name)
I’'ve tried searching through these forums, and there are many people with questions about upgrading databases manually, and most posts point towards the document at “http://www.jivesoftware.org/community/entry.jspa?externalID=481&categoryID=22” but every single time I click on it, it goes to a page saying "404 There is no Action mapped for namespace / and action name entry. Check if there is such an action name with such namespace defined in the xwork.xml and also if such an action class exists. Check also the log to see if the action class is successfully loaded.
/community/entry.jspa was not found on this server."
Is there any way for me to get hold of this document? I’'ve spent about 1 hour searching the Jive site and using google with no luck. It would be greatly appreciated.
My second problem is minor: Trillian Pro doesn’‘t work with the Wildfire 3.0.0 server. It connects fine and receives messages, but you cannot send messages. Every other client it works happily and perfectly, but its just trillian pro that you can’'t send messages? I am unsure if it is just my trillian that has this problem, or is this problem occurred with my previous 2.6.2 version? Has anyone else experienced this problem?
Hopefully someone can help me
Thanks in advance,