Thread

I’ll do my best to keep this short:

I’m running EE 1.6.9, build 20100430 — ever since I updated to 1.6.9 from 1.6.8, I’m running into issues with my cache directories changing permissions from 777 to 755.

If I change them back to 777, they eventually change back to 755.

Is this supposed to be happening? It’s getting in the way of my deploy script which tries to delete the cache folders but fails if the permissions are 755.

I can’t seem to find anyone who’s had this issue with 1.6.x (though there are several posts about 2.0), and for me I never had this problem before updating to 1.6.9.

Are you using any other third-party addons, like modules or extensions?

Modules, no, extensions, yes:

FieldFrame
Last_segment
jQuery for the Control Panel (v.1.1.1)
Clone Entries (v.1.1)
SL Field Formatting (v.1.0.)
EEvent Helper (v.1.0.2)

If the permissions are supposed to be 755, that’s fine, I just need to fix my script — but if for whatever reason it’s not, then I’d like to figure this out.

Douglas,

I believe this was a deliberate change in 1.6.9. Hope that helps.

Hrm- there was a deliberate change in 2.0 (permissions are configurable- yay)- but I’m not spotting one in 1.6 branch.  Douglas, can you check with your host and see if they changed anything on their end?  I do recall at least one instance where the host was changing the permissions.

Let me know whether that’s the case- if it’s not, I’ll dig deeper.  Oh- and if I need to dig deeper- can you let me know which cache folders/files seem to be effected?  If it’s only one folder, would give me a hint.

Robin,

I’ll open a ticket with the host, but we’re on a VPS with no other apache installs running.

At any rate, the cache folders that become 755 seem to change — sometimes the page_cache folder, sometimes the tag_cache folder, sometimes the db_cache folder. Sometimes all three, or just two. It seems like it happens over an hour or so, and sometimes I seem to catch it before they all change to 755.

And for further insight, I’m deploying with capistrano, so during the cleanup task is when the I notice the errors.

After deploying with capistrano, the cache folders are set to 777, but at some time in the future, generally before I deploy the next release, they change to 755.

For the moment, we’ve worked it out with a line in the sudoers file.

I can probably do some more monitoring to get a better idea of how long this issue takes to crop up, but not until next week.

Glad you have a temp fix up.  It’s possible some cache routine dropped a chmod and I’m just not spotting it.  Will take a closer look- but if you spot any hints, definitely let me know.  I’m not replicating myself- but it sounds quirky.

None of the 3rd party modules you have scream a warning- but you might do a quick search through them for ‘cache’ as well.  It’s just possible one of them is in play.  Seems unlikely from the names, though.