zava
Elite Observer

logging stopped working (FSAppender/datedLogging)

Jump to solution

Hello,

We have been unable to get logging messages for about two weeks now. On the monitoring page under the Logfiles menu we get this message

A configured FSAppender with enabled "datedLogging" is required for displaying log entries. Please check your configuration!

we don't know what happened.

Here is the log configuration on the server.

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="INFO">
	<Appenders>
		<!-- dated logging is used by server monitoring for log file display -->
		<FsAppender name="fs" consoleLogging="false" plainLogging="true"
					datedLogging="true" maxFileSize="5MB" buffer="8192" flushCycle="10"/>
	</Appenders>
	<Loggers>
		<Logger name="org.eclipse.jetty" level="WARN" additivity="false">
			<AppenderRef ref="fs"/>
		</Logger>
		<Logger name="org.apache" level="WARN" additivity="false">
			<AppenderRef ref="fs"/>
		</Logger>
		<Logger name="org.apache.log4j.jmx" level="ERROR" additivity="false">
			<AppenderRef ref="fs"/>
		</Logger>
		<Logger name="de.espirit.firstspirit.server.ExecutionManagerImpl" level="INFO" additivity="false">
			<AppenderRef ref="fs"/>
		</Logger>
		<Logger name="httpclient.wire" level="INFO" additivity="false">
			<AppenderRef ref="fs"/>
		</Logger>
		<Logger name="org.apache.commons.httpclient" level="INFO" additivity="false">
			<AppenderRef ref="fs"/>
		</Logger>
		<Logger name="org.apache.http" level="INFO" additivity="false">
			<AppenderRef ref="fs"/>
		</Logger>
		<Logger name="org.apache.http.impl.execchain.RetryExec" level="WARN" additivity="false">
			<AppenderRef ref="fs"/>
		</Logger>
		<Root level="INFO">
			<AppenderRef ref="fs"/>
		</Root>
	</Loggers>
</Configuration>

 

0 Kudos
1 Solution

Accepted Solutions
zava
Elite Observer

I renamed the file .conf and now it works

View solution in original post

0 Kudos
7 Replies
Windmüller
Crownpeak employee

The configuration file looks fine. Can you please share its filename and the FirstSpirit version?

0 Kudos
zava
Elite Observer

filename fs-logging.xml
FirstSpirit version: 2024.4

0 Kudos
Windmüller
Crownpeak employee

Please check the fs-wrapper.log for a line containing

Log4j properties loaded: ...

Does it mention the same filename?

0 Kudos
zava
Elite Observer

I found this, maybe that's the problem ☹️

INFO | jvm 1 | 2024/09/05 11:17:39 | ERROR (de.espirit.firstspirit.server.logging.LoggingManagerImpl): '/srv/firstspirit5/conf/fs-logging.conf' not found, cannot configure logging

0 Kudos
Windmüller
Crownpeak employee

Just to verify, the absolute filename of your configuration filename is /srv/firstspirit5/conf/fs-logging.xml?

Support for the Log4J1 configuration syntax has been removed with FirstSpirit 2024.6. An update of the server might solve this issue.

0 Kudos

yes /srv/firstspirit5/conf/fs-logging.xml

0 Kudos
zava
Elite Observer

I renamed the file .conf and now it works

0 Kudos