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
The logrotate utility should be installed and preconfigured on Integration (containerized) environments. Running out of storage due to large log files happens for various reasons. Its absence an unexpected inconsistency with clustered (Pro Plan Production and Staging) environments, which have logrotate. Further, the utility is consistently offered by Magento Cloud's hosting competitors.
A couple scenarios in which I have encountered the issue.
The Production environment of a Starter Plan is containerized. The normal traffic load of a Production site will cause log size to increase rapidly.
If an error exists during a cron run, that error will continuously be logged, causing even unused Integration environments to exceed storage capacity over time.
The text was updated successfully, but these errors were encountered:
As of 2021, it looks like logrotate is installed on both pro plan prod and staging environments as well as integration environments under /usr/sbin/logrotate. However, it isn't configured out of the box.
Staging and prod are on logrotate version 3.8.7 while integration environments are on 3.11.0.
@tonyklapatch would you happen to have a guide for configuring logrotate for the integration environments? Or, even a simple conf file that could be dropped in?
The logrotate utility should be installed and preconfigured on Integration (containerized) environments. Running out of storage due to large log files happens for various reasons. Its absence an unexpected inconsistency with clustered (Pro Plan Production and Staging) environments, which have logrotate. Further, the utility is consistently offered by Magento Cloud's hosting competitors.
A couple scenarios in which I have encountered the issue.
The text was updated successfully, but these errors were encountered: