Visitor hits page on server 1, where 34354q387g3aohfo35hg98hg9o4.css files exists in the ctools/css folder.

When pages loads, css is loaded from server 2, 34354q387g3aohfo35hg98hg9o4.css doesn't not exist on server 2.

Page displays incorrectly.

Solutions? Can I disable the generation of these partial css files? I sometimes have multiple versions of the same file with _xx tacked on the end, how and why are these files created, what benefit am I getting from this? Some of them go back weeks, even months, shouldn't they be cleaned up.

I could use file replication to make sure they exist on all server, but it looks like a big mess. Is there any documentation of how that whole thing works.

Comments

djake’s picture

I am having this same issue. I understand many are using NFS mounts to share public files, but, since this file is automatically generated, I'm curious if there is any mechanism for the server to recreate the file locally if it does not exist.

I am using Amazon Elasticache w/ the Memcache plugin, in case that is relevant, and page caching is on for anonymous users.

Anonymous’s picture

Issue summary: View changes

Did you ever manage to fix this issue? I'm running Drupal 7 on AWS with ElasticCache and EFS, and ctools really doesn't want to play nice with that setup sadly...

I've "solved" the issue for now by having a session fixation on the same backend for the duration of the browser's session (just remote the duration of the ELB cookie). But when I enable a module, someone on another backend instance might get cache-related errors.

MustangGB’s picture

Category: Support request » Feature request