EDU Monitoring and Troubleshooting
This article covers EDU's logs, log masking, hardening, in-app status, startup checks, and common error scenarios. For configuration and how EDU works, see the EDU Administrator Guide.
Log files​
| File | Use |
|---|---|
EDU_yyyy-MM-dd.log | Normal Information+ activity, daily rolling, 30 backups |
EDU_errors_yyyy-MM-dd.log | Warning+ only, daily rolling, 90 backups |
EDU_debug.log | Verbose diagnostic output (incl. HTTP), 50 MB size rolling, 5 backups |
HTTP traffic is logged with an 8-character correlation ID for request/response matching.
Sensitive-data handling in logs​
- The
Authorizationrequest header is never logged. - Request and response bodies are masked — any JSON property whose name looks sensitive (password, secret, token, API key, and similar) is replaced with
***MASKED***, at any nesting depth. - For sign-in traffic, EDU never logs the actual token. Instead it logs a one-way fingerprint of it plus the token's non-secret details (who issued it, who it's for, when it expires, and any clock difference) — enough to troubleshoot sign-in problems without a usable token ever landing in the log.
Hardening​
- Buffered HTTP response reads are capped at 32 MB.
- Server error bodies captured into exceptions are truncated to 4096 characters.
- Hand-edited settings are clamped to safe ranges on read-back.
- TLS certificate validation is on by default. Leave Validate SSL Certificates enabled outside of test environments.
In-application status​
- The main window has a left menu (Activity Log, Clear Activity Log, Open Log Folders, Clean Backup Folder) and a status bar.
- The status bar shows Monitoring / Not Monitoring, the watched process types, queued/processed counts, the mode, and the signed-in user.
- The Activity Log shows a live, human-readable stream — including Odyssey connect/retry activity and the startup Article Exchange availability line.
Startup checks​
After sign-in, EDU runs two hard-stop checks before file watching begins — a version check and an ILLiadServerIP presence check — either of which shows a dialog and exits if misconfigured. An Article Exchange availability diagnostic is logged (naming any missing keys) but is non-fatal.
Common error scenarios​
| Symptom | Likely cause |
|---|---|
| "Directory Configuration Required" prompt after login | No watch directory configured and the server image-path keys didn't resolve to a folder on this workstation; add one on Settings → File Processing |
| Watch directory error at runtime | A configured directory does not exist or disappeared |
| Login fails, "check API URL" | API base URL wrong or the Web API host unreachable; use Change to re-run the wizard |
| Login fails with credential error | Username/password invalid, or the SSO provider is misconfigured on the server |
| Transaction not processed | Transaction not found, wrong process type, or not at the required In Stacks Searching / In DD Stacks Searching status |
| Send fails (socket / protocol error) | Lender's Odyssey listener unreachable or refusing connection; status reverts and a note is added |
| Article Exchange unavailable | One or more of the five OCLC customization keys is missing/blank (named in the Activity Log) |
| File never picked up | Extension not allowed; file under a Backup or dot-prefixed folder; directory not actually watched; or a duplicate .sent marker suppressed it |
| Startup exits immediately after login | ILLiadServerIP unset or version mismatch |