OX6:Setting Loglevels - Revision history

Choeger: Choeger moved page Setting Loglevels to OX6:Setting Loglevels

2015-11-27T10:58:48Z

Choeger moved page Setting Loglevels to OX6:Setting Loglevels

← Older revision

Revision as of 10:58, 27 November 2015

Tierlieb at 10:29, 20 January 2014

2014-01-20T10:29:38Z

← Older revision		Revision as of 10:29, 20 January 2014
Line 1:		Line 1:
			<div class="title">OX Logging</div>
	{{VersionTo\|7.4.1}}		{{VersionTo\|7.4.1}}

Tierlieb: old version

2014-01-20T10:29:18Z

old version

@@ Line 1: / Line 1: @@
-= Open-Xchange loglevels =
+{{VersionTo|7.4.1}}
 The loglevel Open-Xchange backend is using for each single class can be defined in the file <tt>/opt/open-xchange/etc/file-logging.properties</tt>.
@@ Line 45: / Line 50: @@
 [[Image:jconsole.png|600px]]

Choeger at 09:54, 30 August 2013

2013-08-30T09:54:05Z

← Older revision		Revision as of 09:54, 30 August 2013
Line 42:		Line 42:
	$ jconsole service:jmx:rmi:///jndi/rmi://localhost:9999/server		$ jconsole service:jmx:rmi:///jndi/rmi://localhost:9999/server

	Note: That requires a X11 connection.		'''Note:''' That requires a X11 connection.

	[[Image:jconsole.png\|600px]]		[[Image:jconsole.png\|600px]]

Choeger at 09:52, 30 August 2013

2013-08-30T09:52:14Z

← Older revision		Revision as of 09:52, 30 August 2013
Line 37:		Line 37:

	$ /opt/open-xchange/sbin/showruntimestats -d 'java.util.logging:type=Logging!setLoggerLevel!com.openexchange.soap.cxf.logger!ALL!'		$ /opt/open-xchange/sbin/showruntimestats -d 'java.util.logging:type=Logging!setLoggerLevel!com.openexchange.soap.cxf.logger!ALL!'

			When you install the complete java sdk, you can use the jmx console:

			$ jconsole service:jmx:rmi:///jndi/rmi://localhost:9999/server

			Note: That requires a X11 connection.

			[[Image:jconsole.png\|600px]]

Choeger at 08:42, 30 August 2013

2013-08-30T08:42:38Z

← Older revision		Revision as of 08:42, 30 August 2013
Line 21:		Line 21:
	== Change loglevel without restarting Open-Xchange ==		== Change loglevel without restarting Open-Xchange ==

	It is also possible to change the loglevel while Open-Xchange is running. This can be achieved by the tool <tt>showruntimestats</tt>.		It is also possible to change the loglevel while Open-Xchange is running via [http://www.oracle.com/technetwork/java/javase/tech/javamanagement-140525.html JMX]. This can be achieved by whatever JMX tool you want or by the tool <tt>showruntimestats</tt>.

	Given the same example as above, changing loglevel to ALL of the complete Open-Xchange stack, run		Given the same example as above, changing loglevel to ALL of the complete Open-Xchange stack, run

Choeger at 08:24, 30 August 2013

2013-08-30T08:24:09Z

← Older revision		Revision as of 08:24, 30 August 2013
Line 33:		Line 33:
	'''Note:''' Changing loglevel via this tool does not change it permanently. After a restart, the values from the file <tt>/opt/open-xchange/etc/file-logging.properties</tt>		'''Note:''' Changing loglevel via this tool does not change it permanently. After a restart, the values from the file <tt>/opt/open-xchange/etc/file-logging.properties</tt>
	are used again.		are used again.

			If you want to change the loglevel of just a part of the software, e.g. the SOAP api, run

			$ /opt/open-xchange/sbin/showruntimestats -d 'java.util.logging:type=Logging!setLoggerLevel!com.openexchange.soap.cxf.logger!ALL!'

Choeger at 08:17, 30 August 2013

2013-08-30T08:17:41Z

← Older revision		Revision as of 08:17, 30 August 2013
Line 1:		Line 1:
	Usually our groupware and admin daemon tend to be pretty shy, and don't provide much log output. With some charm and the correct configuration parameters they can be coaxed into being more talkative. Have a look at the files:		= Open-Xchange loglevels =

	* /opt/open-xchange/etc~~/groupware~~/file-logging.properties		The loglevel Open-Xchange backend is using for each single class can be defined in the file <tt>/opt/open-xchange/etc/file-logging.properties</tt>.
	* /opt/open-xchange/etc/admindaemon/~~file-logging~~.~~properties~~

	~~These are for~~ the ~~groupware and admin daemon respectively. If you want to turn both into babbling processes change~~ the ~~line:~~		To increase the loglevel of the complete Open-Xchange software stack, set

	<pre>		<pre>
	.level = ~~SEVERE~~		.level = ALL
	</pre>		</pre>

	to		on top of that file.

			As also explained on top of the same file, the following loglevels exist:

			* ALL
			* INFO
			* FINE

			When you changed any value, a restart of the Open-Xchange server is required.

			== Change loglevel without restarting Open-Xchange ==

			It is also possible to change the loglevel while Open-Xchange is running. This can be achieved by the tool <tt>showruntimestats</tt>.

			Given the same example as above, changing loglevel to ALL of the complete Open-Xchange stack, run

			$ /opt/open-xchange/sbin/showruntimestats -d 'java.util.logging:type=Logging!setLoggerLevel!!ALL!'

			and to revert back either restart Open-Xchange or run

	~~<pre>~~		$ /opt/open-xchange/sbin/showruntimestats -d 'java.util.logging:type=Logging!setLoggerLevel!!INFO!'
	.~~level~~ = ~~ALL~~
	~~</pre>~~

	~~and~~ restart the ~~process in question~~. ~~This might help you get closer to whatever problem buggers you~~.		'''Note:''' Changing loglevel via this tool does not change it permanently. After a restart, the values from the file <tt>/opt/open-xchange/etc/file-logging.properties</tt>
			are used again.

Mheiland at 12:55, 1 March 2007

2007-03-01T12:55:02Z

← Older revision		Revision as of 12:55, 1 March 2007
Line 1:		Line 1:
	Usually our groupware and admin daemon tend to be pretty shy, and don't provide much log output. With some ~~charme~~ and the correct configuration parameters they can be coaxed into being more talkative. Have a look at the files:		Usually our groupware and admin daemon tend to be pretty shy, and don't provide much log output. With some charm and the correct configuration parameters they can be coaxed into being more talkative. Have a look at the files:

	* /opt/open-xchange/etc/groupware/file-logging.properties		* /opt/open-xchange/etc/groupware/file-logging.properties
	* /opt/open-xchange/etc/~~groupware~~/file-logging.properties		* /opt/open-xchange/etc/admindaemon/file-logging.properties

	These are for the groupware and admin daemon respectively. If you want to turn both into babbling processes change the line:		These are for the groupware and admin daemon respectively. If you want to turn both into babbling processes change the line:
Line 16:		Line 16:
	</pre>		</pre>

	and restart the process in question. This might help you get closer to ~~whichever~~ problem buggers you.		and restart the process in question. This might help you get closer to whatever problem buggers you.

DerCisco: New page: Usually our groupware and admin daemon tend to be pretty shy, and don't provide much log output. With some charme and the correct configuration parameters they can be coaxed into being mor...

2007-03-01T12:33:43Z

New page: Usually our groupware and admin daemon tend to be pretty shy, and don't provide much log output. With some charme and the correct configuration parameters they can be coaxed into being mor...

New page

Usually our groupware and admin daemon tend to be pretty shy, and don't provide much log output. With some charme and the correct configuration parameters they can be coaxed into being more talkative. Have a look at the files:

* /opt/open-xchange/etc/groupware/file-logging.properties
* /opt/open-xchange/etc/groupware/file-logging.properties

These are for the groupware and admin daemon respectively. If you want to turn both into babbling processes change the line:

<pre>
.level = SEVERE
</pre>

to

<pre>
.level = ALL
</pre>

and restart the process in question. This might help you get closer to whichever problem buggers you.