forked from eprints/irus
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #5 from eprintsug/issue-4
Add error logging
- Loading branch information
Showing
5 changed files
with
173 additions
and
138 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -36,6 +36,21 @@ In the file `lib/cfg.d/pirus.pl` there is a URL for a test COUNTER server in the | |
if you are testing the plugin, or have it installed on a test/development machine, you can add the configuration | ||
above to a file in the archive specific configuration e.g. `~/archives/ARCHIVEID/cfg/cfg.d/z_pirus.pl`. | ||
|
||
### Troubleshooting | ||
|
||
From v1.2.2, more information about a failed transfer of data to the tracker will be logged in the description of the | ||
`Event::PIRUS` event (that then replays the data to the tracker). | ||
To view the event, go to 'Manage records' -> 'Tasks' as an admin user in the EPrints interface. If there are a lot of | ||
items in the list, you may want to filter for `Plugin` = `Event::PIRUS`. | ||
|
||
There is also a configuration option to add the same information to the Apache error log. This can can be quite | ||
verbose as it would log for every failed transmission, whereas the replay event is created once. | ||
|
||
The `Event::PIRUS` replays may only exist for a short amount of time in the event queue if the initial transmissions | ||
fail, but the replay events work. To scrutinise the replay event you may need to temporarily stop the EPrints indexer | ||
to allow you to see the details of the failure. | ||
|
||
|
||
## Implementation | ||
|
||
This code will PING the configured tracker server whenever a full-text or item summary page is requested from EPrints. | ||
|
@@ -72,7 +87,11 @@ The default oai_dc metadata profile does not contain ORCIDs, but if you have a m | |
|
||
|
||
## Changes | ||
|
||
|
||
* 1.2.2 John Salter <[email protected]> | ||
|
||
Additional information added to replay event and error log when a data transfer fails. This information may help diagnose the problem. | ||
|
||
* 1.2.1 John Salter <[email protected]> | ||
|
||
Update to default tracker URL. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.