Three known use cases can cause false Edge Encryption proxy outage alerts. In each case, the string "No Edge Encryption proxy online" appears in the instance logs, which triggers the outage alert.
Steps to Reproduce
The following three use cases can cause false Edge Encryption proxy outages:
- A proxy starts up for the first time (Intermittent). When a brand new proxy connects to a freshly zbooted instance, it takes some time to start up after its registration, which can sometimes exceed the default 25-second outage time.
- GlideCacheManager.invalidate() is called by a script.
- An operation like an upgrade script flushes the Glide cache.
There is no known workaround for this issue. If you are able to upgrade, review the Fixed In field below to determine the versions that have a permanent fix. You can also subscribe to this known error article (click Subscribe button at the top of the article) to receive notifications when more information is available about this issue.
Related Problem: PRB709440