Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cachetool tasks #221

Open
t3easy opened this issue Nov 4, 2018 · 3 comments
Open

Cachetool tasks #221

t3easy opened this issue Nov 4, 2018 · 3 comments
Labels
Milestone

Comments

@t3easy
Copy link
Collaborator

t3easy commented Nov 4, 2018

Expected Behavior

Predefined task to flush apc/opcache with https://github.com/gordalina/cachetool

Actual Behavior

Not available

@t3easy t3easy added the feature label Nov 4, 2018
@sabbelasichon sabbelasichon added this to the 3.0.0 stable release milestone Dec 14, 2018
@simonschaufi
Copy link
Collaborator

simonschaufi commented Feb 19, 2020

Maybe this is the solution to my long term problem:

Server (TYPO3 CMS) TYPO3\Surf\Task\Php\WebOpcacheResetExecuteTask
Executing PHP opcache reset script at "https://example.com/surf-opcache-reset-xxx.php" did not return expected result

I get this error during almost every deployment process on a website behind a proxy server and My customer is so annoyed of this problem as right after the deployment is finished, the server responds with internal server error. One minute later everything is fine.

The typo3temp problem described here #295 also occurs very often but is really hard to reproduce.

@jonaseberle
Copy link
Contributor

For me it solved the problem you describe @simonschaufi .

When using cachetool via HTTP like here https://gist.github.com/jonaseberle/9bfc29b3af726c41b3cd9cec088fc722
the only difference to WebOpcacheResetExecuteTask seems to be that the latter

  • create PHP script
  • transfer
  • switch symlink
  • access via HTTP

while the first (when configured as remote task) does

  • transfer
  • switch symlink
  • create PHP script
  • access via HTTP

-> This seems to help. I guess in our case it was about storage systems vs. webservers noticing the symlink switch. That problem does not seem to occur if the file is created after the symlink is switched.

Using --fcgi with cachetool is prefered, of course where possible.

@sabbelasichon
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants