Pages
About Me
Links
Tags
PERSONAL 322
LDS 258
SPIRITUAL 251
BOOK OF MORMON 181
SCRIPTURES 99
RELIGION 78
LINUX 68
COMPUTERS 63
LIFE 60
GENERAL CONFERENCE 39
MISCELLANEOUS 34
GENTOO 33
MUSIC 31
PROGRAMMING 30
CARS 29
MICROSOFT 23
FAMILY 22
AUDIO 18
I LOVE MY JOURNAL 18
FUN 15
CHILDREN 12
CURRENT EVENTS 10
NATURE'S WAY 10
DRM 9
VIDEO 8
CONEXM 7
FRIENDS 6
COMPUTER HARDWARE 5
BABBLINGS 5
DRUMS 4
GAMES 4
GENERAL INSANITY 3
KDENLIVE 3
ADVERSITY 2
CATS 2
YOUTH CONFERENCE 1
EVERYDAY THOUGHTS 1
CHURCH NOTES 1
MY JOURNAL 1
POLITICS 1
PARENTING 1
POETRY 1
RSS Feed
Subscribe!Sat - Jul 12, 2008 : 01:30 pm
content
 |
|
|
|
|
rated 0 times |
OpenFire gentoo problems
I just spent the last three hours trying to figure out why my OpenFire 3.5.2 instance was installing just fine, saying that it was running just fine, but in reality was not running at all.
Neither port 9090, nor 9091 was open, both ports 9090, and 9091 were closed. ps -A | grep openfire returned nothing - at all.
Yet, /etc/init.d/openfire status would say that it was happily running along without problem.
The logs were all empty, and the "everything" log (metalog) didn't say jack about openfire at all.
So, after 3 hours, I figured out that the problem was that I had blackdown version 1.4 running as my default java instance.
Openfire won't run without java 1.5 or greater. Would have been really REALLY REALLY nice if openfire would have some sort of message stating something about java needing to be updated.
So, if you're having the same problem, simply run: java-config -L and see which one is running as default (java -version does the same thing), and then use java-config -S to set one that is at or above 1.5
Just thought I'd spread the love. OpenFire is now running great.
[SOLVED]
Neither port 9090, nor 9091 was open, both ports 9090, and 9091 were closed. ps -A | grep openfire returned nothing - at all.
Yet, /etc/init.d/openfire status would say that it was happily running along without problem.
The logs were all empty, and the "everything" log (metalog) didn't say jack about openfire at all.
So, after 3 hours, I figured out that the problem was that I had blackdown version 1.4 running as my default java instance.
Openfire won't run without java 1.5 or greater. Would have been really REALLY REALLY nice if openfire would have some sort of message stating something about java needing to be updated.
So, if you're having the same problem, simply run: java-config -L and see which one is running as default (java -version does the same thing), and then use java-config -S to set one that is at or above 1.5
Just thought I'd spread the love. OpenFire is now running great.
[SOLVED]
Comment by Justin Workman on Feb. 05, 2009 @ 09:34 pm
Hi : )
I'm having what seems to be the same problem. /etc/init.d/openfire start will say it starts, but it won't. And I can't connect to the admin panel, and the logs are empty.
But java-config -L gives me Sun JDK 1.6.0.05 [sun-jdk-1.6]
Any suggestions?
I'm having what seems to be the same problem. /etc/init.d/openfire start will say it starts, but it won't. And I can't connect to the admin panel, and the logs are empty.
But java-config -L gives me Sun JDK 1.6.0.05 [sun-jdk-1.6]
Any suggestions?
Comment by Harry Rose on Feb. 26, 2009 @ 10:40 am
Hi,
In response to Justin Workman's post, I found that by moving /opt/openfire/conf/openfire.xml.sample to /opt/openfire/conf/openfire.xml and making sure it was owned by jabber and part of the jabber group fixed the problem.
In response to Justin Workman's post, I found that by moving /opt/openfire/conf/openfire.xml.sample to /opt/openfire/conf/openfire.xml and making sure it was owned by jabber and part of the jabber group fixed the problem.
Let us know what you think: