Knowing Within Minutes When PDF Signing Stops Working
You will learn how to configure proactive monitoring for your OneSigner deployment so that you can detect and resolve PDF signing failures within minutes of occurrence.
Prerequisites and Deployment Requirements
To successfully monitor your automated PDF signing setup, verify that your environment meets the core operational requirements:
- A dedicated Windows machine (Windows 10/11 or Windows Server 2019+) running
OneSignerServiceas LocalSystem with the hardware token (YubiKey, SafeNet, or ePass2003) physically plugged in. - An interactive Windows session maintained via Windows auto-logon so that the service can spawn signing tasks in the logged-on user's session without session-zero isolation blocks, as detailed in Signing Fails in Service Mode.
- Administrative access to the local machine to inspect the Windows Event Log and file system logs.
Inspecting the Daily Signing History Logs
OneSigner writes all transaction attempts, successes, and errors to tab-separated text logs on the local disk. When automated folder watch jobs or API requests fail silently, these log files provide the exact timestamp and failure reason.
- Navigate to the default installation directory on your signing host:
C:\OneSigner\app\logs\. - Open the current log file, named according to the date format
signing-YYYY-MM-DD.log. - Search for recent entries marked with error statuses or review the history directly within the configuration utility under Management → Logs.
- For enhanced debugging output during test cycles, set the environment variable
ONESIGNER_CLI_LOG=infoto capture verbose CLI diagnostics.
For a detailed breakdown of specific log indicators and error codes, refer to Reading the OneSigner Log Files: Where They Are and What Matters.
Monitoring via Windows Event Viewer
Because OneSignerService runs as a native Windows background service, critical service failures, token detachment events, and startup errors are logged directly to the Windows Event Log.
- Press Win + R, type
eventvwr.msc, and press Enter to open the Event Viewer. - In the left-hand console tree, expand Windows Logs and select Application.
- Click Filter Current Log... on the right action pane.
- Under Event sources, select OneSignerService (or filter by Source name) and click OK.
- Look for error-level events indicating service crashes, inability to access the PKCS#11 driver, or session communication timeouts.
If the service fails to communicate with the hardware token because the user session logged out after a reboot, ensure your machine is properly configured using the steps in Configuring Windows Auto-Logon for Unattended Token Access.
Polling the REST API Health and Status Endpoints
If you integrate OneSigner into a broader IT infrastructure or CI/CD pipeline, you can programmatically poll the REST API to verify that the signing engine and token backends are operational.
- Send an authenticated GET request to check engine availability:
GET /api/signing/status
Authorization: Bearer YOUR_TENANT_OR_ADMIN_TOKEN
- Review the response payload to verify that active signing profiles are loaded and that the hardware token is detected and unlocked.
- Inspect specific profile configurations by calling:
GET /api/signing/profiles
Authorization: Bearer YOUR_TENANT_OR_ADMIN_TOKEN
If the API returns authentication or token communication errors, verify your bearer token and ensure the USB token has not experienced a PIN lockout due to incorrect credential attempts across multiple failed jobs.