I have already check the permissions on the folders and set it to 777.
The strange think is that when i did the first clearing of caches, I lost my images, when I publish the page, the images are displayed. If I clear the caches one more time, the images are still displayed.
Regarding this, i dont' think there is a huge problem of configuration.
The problem is that I don't want to re publish all my pages.
Have you tried clearing all cache (including image aliases that you have to select independently cause it's not included in the 'clear all' cache button) ? And why did you update to 3.9.1? You can update directly to 3.9.4.
Yes i think I cleared all caches because i use the bin command with clear --all.
I upgrade to 3.9.1 because i juste want to fixed a bug for the the 3.9.0 and the 3.9.1 was fine but i don't think this is really the matter except if this problem is a knowne bug of the 3.9.1.
I'm not sure that I will not have the problem if I upgrade to 3.9.4. The strange thing is that i have the problem only for the first clearing of cache, after republishing, it's ok images are displayed again.
No, if you read the shell script you'll see that it only clears cache in 'IMAGE_CACHEDIR="$DIR/cache/texttoimage"', in other words text to image cache.
Only bin/php/ezcache.php and the cache tab in the admin interface lets you delete image alias cache. Note: in 3.10+ the shell script is removed so you have to use the php script, and it also has a new option 'purge'. Read more about it in the doc, it's mentioned here: http://ez.no/doc/ez_publish/technical_manual/4_0/features/clustering
Edit: Basically you should never assume eZ Publish functionality does what you want it to do whiteout carefully double checking the doc and/or code. I know it sucks, but it will save you from a lot of grief..
True, but the shell script is removed from 3.10 / 4.0 because it doesn't support cluster setup. So this only applies to the admin interface.
You should also get a warning if you clear image alias cache and not view cache + template block cache, cause you could end up with pages that link to non existing image aliases.