|
Type:
|
Bug
|
|
Priority:
|
High
|
|
Severity:
|
Major
|
|
Status:
|
Closed
|
|
Resolution:
|
Complete
|
|
Resources:
|
Bob Denny
|
|
Reported By:
|
Bob Denny
|
|
Component:
|
Dispatch Scheduler Engine
|
|
Versions Affected:
|
8.3
|
|
Start Date:
|
4/23/2020
|
| Created: |
4/23/2020 9:34:51 AM |
| Revised: |
1/12/2021 3:12:50 PM
|
| Closed: |
1/12/2021 3:12:41 PM |
| Resolved: |
1/12/2021 3:12:50 PM |
|
See this Comm Center thread by Tim Long and Steve Reilly. The scheduler is trying to send Operator Intervention email. In that process, as of 8.3, it tries to get the status of TLS (https) on ACP's web server so it can include a link to the Scheduler Engine Log. it does this on all scheduler-generated emaild. However if the Operator Intervention came from a compromised ACP, then tyrying to get TLSSecurityActive from ACP will fail for RPC error etc. It's uncaught in SendEmail so it causes the scheduler to fatally exit. Oops.
|
|
|
|
|
|
|
|
|
|
|
|
Are you sure that you want to reset the votes?
