Permission denied in tmp

Question

I just deployed a Rails 3 app with Ruby 1.9.2. I have been getting several errors.

application.css wasn't compiled. so I set pre compilation in production.rb to false;
Then I got: cannot generate tempfile, so I did rake tmp:clear;
And now I get ActionView::Template::Error (Permission denied - /srv/www/appname/tmp/cache/assets): and I haven't been able to fix this one.

Please help.

score 39 · Accepted Answer · edited May 23 '17 at 12:17

39

If the user:group running your web server is http:http and it's running on *nix, do this:

sudo chown -R http:http /srv/www/appname/

Also, silly question, but does /tmp/cache/assets exist?

And, if so, as @leonel points out, you may also need to change the permissions:

chmod 777 /srv/www/appname/tmp/cache

Be careful setting 777 permissions on anything. Only do this to verify a permissions issue, then reset to the most minimal permissions necessary.

edited May 23 '17 at 12:17

Community

1
1

answered Sep 23 '11 at 07:10

Adam Eberlin

14,005
5
37
49

4

So that command would give ownership to anybody? I had to change the permissions of cache to drwxrwxrwx. – leonel Sep 23 '11 at 15:08
1

@leonel gave the right answer: `chmod 777 /srv/www/appname/tmp/cache` fixed the problem for me. – kgadek May 22 '14 at 01:23
6

Please be careful when giving any directory 777 permissions: See [Fixing answers that recommend “chmod 777”](http://meta.stackoverflow.com/q/318885/4174897). – JAL Mar 22 '16 at 13:06

score 8 · Answer 2 · edited May 24 '19 at 05:09

8

Most likely you're running your app under apache passenger.

You have to change the owner of config/environment.rb to somebody who has permissions to your app's folder.

chown -R www-data:www-data /path/to/app

edited May 24 '19 at 05:09

Dave Powers

2,051
2
30
34

answered Aug 08 '12 at 19:43

Vanuan

31,770
10
98
102

score 4 · Answer 3 · edited Nov 16 '15 at 16:04

4

Make the tmp folder of your project writable:

chown -R group:user /path/to/rails/app/tmp
chmod -R 777 /path/to/rails/app/tmp

In your console, run rake tmp:cache:clear
Restart your application.

edited Nov 16 '15 at 16:04

Retsam

30,909
11
68
90

answered Jan 14 '14 at 08:10

Spyros

227
2
12

4

**STOP**. Don't do this! This is potentially very dangerous. Please see [Fixing answers that recommend “chmod 777”](http://meta.stackoverflow.com/q/318885/4174897). – JAL Mar 22 '16 at 13:05
2

rake tmp:cache:clear solves the problem! only this!! Thanks – EderRoger Feb 10 '17 at 20:50

pensebien · Answer 4 · 2017-10-05T06:13:10.070

Now for those of us that are using windows - If you are an administrator and see this error

ActionView::Template::Error (Permission denied @ utime_failed) C:/User/..../tmp/cache/assets/sprochets/v3.0/E5/E5PZx-mq8.cache

Then it is Permission and Ownership setting issue on Windows. You can go to the tmp folder on your application and give yourself(User) permission to **Read, Write and Execute ** on the folder. Click [here][1] to view how to give permissions.

Quick Fix. Open your terminal and run the following command as an administrator

    takeown /f <location of your app tmp folder> /r /d y

Then Restart your server.

score 2 · Answer 5 · answered Sep 23 '11 at 04:48

2

You probably didn't create your Rails application with the user running the server now. Can you paste the output of ls -alh /srv/www/appname/tmp/cache/assets and tell us the user running the webserver ?

answered Sep 23 '11 at 04:48

Marc Plano-Lesay

6,808
10
44
75

No. I created the app in my development machine and then uploaded it to the production machine using FTP. I think the user running the server is root. I made it work already but I had to change the permissions on the cache folder to `drwxrwxrwx`. If there is a better way please let me know. This is the output of the ls- alh command: http://pastebin.com/v1sH5Qhb – leonel Sep 23 '11 at 15:12
1

Users not in the nogroup group can't write to your folder. You need to change the owner/group of the tmp folder. – Marc Plano-Lesay Sep 23 '11 at 17:45

score 1 · Answer 6 · answered Aug 23 '13 at 11:03

I encountered this error recently. Apache was not able to write to tmp directory

cannot generate tempfile /tmp/RackRewindableInput2xxxxxxxxxxxxxxxxx' /app-lib/lib/ruby/1.8/tempfile.rb:52:ininitialize' app-dir/vendor/gems/rack-1.0.1/lib/rack/rewindable_input.rb:73:in new' app-dir/vendor/gems/rack-1.0.1/lib/rack/rewindable_input.rb:73:inmake_rewindable' app-dir/vendor/gems/rack-1.0.1/lib/rack/rewindable_input.rb:26:in read' app-dir/vendor/gems/rack-1.0.1/lib/rack/request.rb:134:inPOST'

I checked permission of tmp directory and it had permission to all groups to write to it. I changed owner of tmp directory and it didn't resolve the error either.

The culprit was tmp directory was filled with too many large files, and looks like somehow apache didn't had enough space to write this new file. Cleared all temp and old files. It sorted out the issue.

score 1 · Answer 7 · answered Feb 03 '18 at 11:43

We need to grant permissions to access the required directory for the system root user

sudo chmod 777 -R your_project_directory_to_be_access

In your case you can use:

sudo chmod 777 -R /srv/www/appname/tmp/

For security reasons, just keep in your mind:

chmod 777 gives everybody read, write and execute rights which for most problems is definitively too much.

score 1 · Answer 8 · answered Aug 11 '19 at 06:53

1

I think a better solution without giving everyone manage rights to tmp folder is like that:

 sudo rake tmp:cache:clear

This will clear the temp folder and when you run rails server again it won't give error.

answered Aug 11 '19 at 06:53

tcgumus

328
3
8

score -1 · Answer 9 · edited Mar 25 '17 at 13:25

-1

In my localhost it gave this error, and the command chmod 777 C:/Sites/project_name/tmp/cache/ solved my problem.

edited Mar 25 '17 at 13:25

pacholik

8,607
9
43
55

answered Mar 25 '17 at 13:08

Naiguel Developer

313
3
3

score -2 · Answer 10 · answered Mar 22 '16 at 12:57

-2

Most probably you gave permission to your app's main folder read and execute mode. However, in order to generate new files from your app, you also need to give write permission for required folder. For example: yUML uses tmp folder for generating files. I gave tmp folder write permission:

chmod -R 777 /usr/share/nginx/html/yuml_product/tmp

solved my problem.

answered Mar 22 '16 at 12:57

user2271779

5
3

2

**STOP**. Don't do this! This is potentially very dangerous. Please see [Fixing answers that recommend “chmod 777”](http://meta.stackoverflow.com/q/318885/4174897). – JAL Mar 22 '16 at 13:01

Permission denied in tmp

10 Answers10

Linked