We have a very high traffic site and are experiencing issues during archiving. We have traced the problem down to a request made by the archive command
When we put this command into the browser, it takes about 40s to complete, but it does complete and the data is properly archived. When initiated from the archive ./console --force-idsites=XXXX command it returns an empty response.
Does anyone know why these execution contexts would differ in their limitations? It seems to me that a CLI context would be more permissive in terms of memory limits and execution timeouts.
It looks like the console command actually makes an HTTP request (it outputs the URL above), which would invoke the php.ini related to apache, not the cli. Does anyone know which php.ini is involved?