get asset in typo3temp after deployment (behind Proxy)

[simonschaufi]

This is not really a bug or a feature but more a brainstorming.

I have a website with high load and I do exception tracking and often get a message like the following:

Message: Core: Error handler (FE): PHP Warning: file_get_contents(/var/www/html/releases/20190509120834/private/typo3temp/assets/css/2ba2d28e2f.css): failed to open stream: No such file or directory in /var/www/html/releases/20190509120834/vendor/typo3/cms/typo3/sysext/core/Classes/Resource/ResourceCompressor.php line 359

This happens right after the deployment is completed. Since right after deployment the typo3temp folder is empty there is no asset to fetch. TYPO3 is behind a proxy server if that is important. Any idea how to solve this?

Specifications

• Surf Version: any
• PHP Version: 7.2
• Platform: Ubuntu

[kaystrobach]

TYPO3 should not throw a warning if resouce is missing, but either fail or create it silently.

Maybe you can create the resources via commandline?

[simonschaufi]

Well, this is a css file that is auto generated by TYPO3 and after deployment the file name can be different because of changes in the original css.

I have the feeling that the time period between when TYPO3 checks if the file exists and then reads it is too long and is interrupted by the symlink change to the new version. Or it is a proxy problem...

[simonschaufi]

I'm still looking for a solution to this.

[sabbelasichon]

@simonschaufi I am going to close this issue. Feel free to reopen.