Project

General

Profile

Bug #5534

Replication log somehow doesn't work.

Added by Jing Tao almost 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Category:
metacat
Target version:
Start date:
11/09/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5534

Description

Metacat logged the some important replication information into the metacatreplication.log file which stays in the directory specified by property replication.logdir in metacat.properties file.

This metacatreplication.log file helped the user to monitor the replication process easily.

However, it is just sort of working right now.

Duane reported that the last timed replication on LTER was 2011-11-03, but the last time to touch the log file was 2010-04-26.

Knb has the similar scenario.

I dug a little bit on the metacat code. In replication relevant class, it always has something like:
private static Logger logReplication = Logger.getLogger("ReplicationLogging");
private static Logger logMetacat = Logger.getLogger(ForceReplicationHandler.class);

Replication information was reorded to both logReplication and logMetacat.

I believe the loggers write info to catalina.out.

Since the catalina.out is big file and not easily to track, is it possible we still to make metacatreplication.log work?

History

#1 Updated by ben leinfelder almost 9 years ago

had to add the log level when defining the replication logger:

log4j.logger.ReplicationLogging=INFO, replication

#2 Updated by Jing Tao almost 9 years ago

Ben: after you change the debug level, the replication log will go to catalina.out or the metacatreplication.log file?

We want it to be in metacatreplication.log file.

#3 Updated by ben leinfelder almost 9 years ago

As configured, all INFO level (and above) messages for ReplicationLogging will go to the replication log file and not catalina.out

#4 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 5534

Also available in: Atom PDF