Is there a method I can turn off all logging? Since I’'ve had to ‘‘adjust’’ the wildfire settings to make it work on a VPS, it was nice enough to wake up in the morning and find out that the admin-console.log was over 2gb… the admin warning is:
10:20:20.552 WARN!! [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9091]]] org.mortbay.util.ThreadedServer.acceptSocket(ThreadedServer.java:461) >02> EXCEPTION
javax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled.
at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.checkEnabledSuites(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source)
at org.mortbay.util.ThreadedServer.acceptSocket(ThreadedServer.java:432)
at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:634)
How the heck do I turn that logging off or fix that warning:) Thank you!
Not even a way to null the logs?
Not that this is helpful, but I do not believe there is a way to clear out the admin-console logs like you can the others. Feature request? ;D ;D ;D
i agree with jadestorm I cannot find anywhere you can disable the admin-console.log ; I also am not sure why you would want to. if it were me I would attempt to fix the error. to do so I would start by adjusting your SSL sittings
admin console / server / server manager / Security Settings
you can disable debug Logging
admin console / server / server manager / logs / debug > you can disable debug logging
(this is the LARGEST log)
Disable Message Auditing
admin console / server / Server Settings / Message Audit Policy
as a last resort you could try disabling write permissions to the logs folder, or the admin-console.log ; ( I have never tried this)
I look to disable it simply because of the issues I’‘ve already had installing this on a VPS; most of which seem irrelevant to the system (such as the Java errors that that halted it from starting) - regardless, I’‘m not using any SSL on this chat service… or any of my sites. Whatever SSL it finds must be part of the other systems, or something that I’'m just not aware of… I admit, I have a lot of server experience, but this is my first VPS.
I didn’‘t think of permissions, that’‘s genius:) Regardless, I’‘ll take a look at the other areas you suggested too. This has been a potential deal breaker for me; if I can’‘t get this logging fixed, it’'ll be Jabberd 2.0.11 or bust.
Edit: I get points for stupid for not even noticing the SSL disable in the server settings – I hope that does the trick, thank you for pointing it out. I’'ll let the logs write for a few hours to see how it reacts.
Message was edited by: bradyj
disableing SSL should fix your issue… I found this thread dealing with the same problem.
http://www.jivesoftware.org/community/thread.jspa?messageID=120486𝚦
I found this thread that says the debug log will also disable the admin-console.log
http://www.jivesoftware.org/community/thread.jspa?messageID=111472𛍰
Disabling SSL did the trick – my debug is currently disabled as of the installation, so things seem to work well so far. I’‘m still trying to figure out some of the size issues… I noticed I turned on wildfire, it wasn’'t writing logs anymore, but my space usage was up 1.6gb. It reverted upon stopping wildfire. I guess I have a little more searching on this system to figure out exactly what it is doing, but so far you have all been great helping with this, thank you:)
Nevermind, it still continues after all of that!!
:24:38.719 WARN!! [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9091]]] org.mortbay.util.ThreadedServer.acceptSocket(ThreadedServer.java:461) >02> EXCEPTION
javax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled.
at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.checkEnabledSuites(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source)
at org.mortbay.util.Thre
Looks like I’'ll have to try and disable the write to the folder, see if that works… 3gb in less than an hour, nice…
ln -s /dev/null admin-console.log
;D
Best I can tell this error is due to an empty or corrupt SSL keystone. if locking down the log folder doesnt work then I would install a new SSL cert and delete the old ones.
this is a maybe.
have you completely disabled SSL?
what version / OS are you useing?
do you know the java version? (Wifi will tell you under server sittings)
ln -s /dev/console admin-console.log
Red Hat Linux, Java 1.5.0_07
And I disabled the SSL in the admin settings - there shouldn’‘t be any SSL needed at all – is there a way for me to verify this information is not active in a database somewhere? If I say disabled in the server settings, I don’‘t see why it’'s logging the issue.
Regarding SSL corruption – this is a VPS, unless someone installed it before, there’‘s a possibility - but from what I know it’‘s a clean setup and I’'ve never installed an SSL in there.
I’'m starting to think this is a very buggy setup under VPS:)
jadestorm wrote:
ln -s /dev/null admin-console.log
;D
Would that work? If so, I’'d take it.
aznidin wrote:
ln -s /dev/console admin-console.log
That ones got me stumped, why would I link my admin console to my developer console?
Well, I’‘ve tried everything - even added a self-signed cert that validated to test it, and inquired with media temple if they see any errors, which they don’‘t. I’‘m chalking this up to software bug, there’'s no reason for an error log to continually repeat itself in this manner, almost every split second. Hate to say it, I love how nice it was to setup, but this seems way too buggy on a VPS to use.
Maybe that comes from the https-based admin console? You have to disable that in the config xml and restart Wildfire.
anlumo wrote:
Maybe that comes from the https-based admin console? You have to disable that in the config xml and restart Wildfire.
Would that be commenting out or disabling the ports for wildfire.xml’'s:
Thanks again guys for all the help here.
Um… what was the final solution? Did you find a solution? I’'m just having the same problem. Thanks for the help.
All attempts have been completely unsuccessful - we scrapped Wildfire for Jabberd 2. Not what we were after, but no one seems to have an answer, and running wildfire on a VPS seems extremely buggy. We even purchased an SSL specifically for the chat service, and tested it there - no problems on Jabberd 2, still problems on Wildfire. Maybe VPS will be more manageable on another version.