Project

General

Profile

Bug #2818

access_log bypassed by replication

Added by Jing Tao over 14 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
metacat
Target version:
Start date:
04/12/2007
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2818

Description

Matt just check the access_log talbe in knb metacat and found there are only 397 insert/update/delete action from 2006 Aug. to now. We think replication bypasses the access log. If replication calls the main metacat api, the logging would happen automatically.

History

#1 Updated by Jing Tao over 14 years ago

Currently, access loging system are called in MetacatServlet class. But replication is happened in MetacatReplication class, so it bypassed the access log. Now, the access log was added in the class and it works fine to me.
Here are some known problem:
1) Username "replication", rather than the real username in remote server, will be stored in the access_log table during the replication
2) Remote metacat server ip address, rather than the real user's ip address, will be stored in the access_log table during the replication.

The reason we did this is because this bug doesn't have the highest priority and we try to minimize the modification in dupilication part.

#2 Updated by Redmine Admin over 8 years ago

Original Bugzilla ID was 2818

#3 Updated by ben leinfelder over 8 years ago

  • Status changed from In Progress to Closed

When documents are inserted or read via replication, this should be logged as the other metacat server so I think this works as desired. There is no user that should be listed for those events.

Also available in: Atom PDF