You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we log in to production instance over SSH and check opcache status or perform commands manually, it's always fine, but just wanted to reach out regarding this strange behavior we monitor in our logs.
The text was updated successfully, but these errors were encountered:
Hi,
In our production logs we get certain amount of 500 errors related to moments when Opcache Clear command is running. Access log shows following:
172.31.42.150 - - [14/Apr/2021:01:35:31 +0000] "GET /opcache-api/clear?key=eyJpdiI6IlFMT2h2VWsrTEpmcUM0K2M5ZUR3RlE9PSIsInZhbHVlIjoiQ0hQbllUd0ZqeGdXTnVCNVRHeUV4QT09IiwibWFjIjoiOTFjM2VmYmJlZjAwYzY5MGNkMmFhZWQ1ZmZmOGUwNGNjOTY3ZmM5YjIwZDJlZmRlZGY4ZjU4M2FhOGE4NjRjMCJ9 HTTP/1.1" 403 6641 "-" "GuzzleHttp/7" "3.128.24.47"
And Laravel log shows:
When we log in to production instance over SSH and check opcache status or perform commands manually, it's always fine, but just wanted to reach out regarding this strange behavior we monitor in our logs.
The text was updated successfully, but these errors were encountered: