powered by Jive Software

Openfire 3.6.4 and MySQL 5.1

According to the poll this is the most popular choice by a large margin, so I should be able to assume there’s plenty of experience. I also hope there will be someone who has taken this far enough to come up with better documented installation procedures. I checked most of the related posts (and documentation) but none of the fixes actually solve the issue once and for all. This is troubling to me as I doubt it is a lack of experience or know-how.

None of the available descriptions of how to install actually result in a working production-ready system, why? Almost all result in the same annoying behavior over and over again, the SETUP completes and no matter what you do, restarts over and over again. It’s not the openfire.xml file, it’s not SQL permissions, it’s not the bug where you have to stop and start Openfire. This has been happening over the last 3 releases.

If you dig deeper into the problem you notice that without manual intervention Openfire is set to start BEFORE MySQL. I’ve been able to get through the installation, change the startup order and fix the problem but even that is not working now. How hard does this have to be? By all means if I am wrong I want to stand corrected and prefer to change what I am doing wrong so as not to have to deal with this ever again. Anybody got a linear (sequential) checklist they’d be willing to share?

We’re installing this as our IM solution for our customers and can’t continue to push it without a better routine.

Thank you in advance for your consideration and for sharing your thoughts,

Joe H. Wise

Global Solutions Architect

OpenScape Unified Communcations Platform

Siemens Enterprise Communications, Inc.

If we want business to embrace open-source we need to make it not only bullet-proof (which I think it is) but reproducible. In the current economy any stall kills margin.

And just to be clear (and fair) all around - as I stated none of the related questions or answers seemed to solve what we’re seeing but I’m starting to think there may be more involved than just Openfire and MySQL. We use SUSE (it’s either a German thing or a developer thing) and I think that might be contributing to the issue.

If I take the following steps:

service mysql stop
service openfire stop

ln -sf /etc/rc.d/mysql /etc/rc.d/rc2.d/S09mysql
ln -sf /etc/rc.d/mysql /etc/rc.d/rc3.d/S09mysql
ln -sf /etc/rc.d/mysql /etc/rc.d/rc5.d/S09mysql

ln -sf /etc/rc.d/openfire /etc/rc.d/rc2.d/S10openfire
ln -sf /etc/rc.d/openfire /etc/rc.d/rc3.d/S10openfire

ln -sf /etc/rc.d/openfire /etc/rc.d/rc5.d/S10openfire

chmod -R 755 /path/to/openfire

service mysql start
service openfire start

Problem solved.

Once we get to this point the Openfire server is pretty much bullet-proof.