View Revisions: Issue #1031

Back to Issue
Summary 0001031: Add heartbeat to pull CUPS job id status
Revision 2019-01-31 21:04 by rijkr
Description IST: Occasionally CUPS notifier fails to deliver job state notifications. As a result, job end states are not coming through, and the jobs in question remain in state "Processing" on the SavaPage side. Failures can be traced down in /var/log/cups/error_log , where a burst of error messages like this:
E [31/Jan/2019:10:53:43 +0100] Unable to send event for subscription 273 (savapage:localhost:8631)!
show up around the time the jobs were last notified as "Processing".
SOLL: Use a heartbeat to perform a CUPS pull of a job id status while monitoring CUPS notifications. When CUPS notifies (push) job id status in between, the heartbeat offset for this job id is reset to zero. The heartbeat frequency (milliseconds) is set in config item "cups.notifier.job-status-pull.heartbeat-msec" (default 20000).
Revision 2019-02-01 11:46 by rijkr
Description IST: Occasionally CUPS notifier fails to deliver job state notifications. As a result, job end states are not coming through, and the jobs in question remain in state "Processing" on the SavaPage side. Failures can be traced down in /var/log/cups/error_log , where a burst of error messages like this:
E [31/Jan/2019:10:53:43 +0100] Unable to send event for subscription 273 (savapage:localhost:8631)!
show up around the time the jobs were last notified as "Processing".
SOLL: Use a heartbeat to perform a CUPS pull of a job id status while monitoring CUPS notifications. When CUPS notifies (push) job id status in between, the heartbeat offset for this job id is reset to zero. The heartbeat frequency (milliseconds) is set in config item "cups.notifier.job-status-pull.heartbeat-msec" (default 30000).