heroku read only file system error on restart only, subsequent requests successful

[Sachin]

I have deployed radiant app (cloned freshly from github) on heroku
without using
gem.

After a restart or after the app comes out of idle mode, there is
read-
only-filesystem-error for one of the css file. On immediate subsequent
requests the error is not seen. Everything works fine after that.


# Logfile created on Tue Sep 14 08:39:25 -0700 2010/!\ FAILSAFE /!\
Tue Sep 14 08:39:29 -0700 2010
Status: 500 Internal Server Error
Read-only file system - /disk1/home/slugs/287995_8159aab_483e/mnt/
public/stylesheets/admin/main.css
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin.rb:232:in `initialize'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin.rb:232:in `open'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin.rb:232:in `update_stylesheet'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin.rb:86:in `update_stylesheets'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin.rb:79:in `each'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin.rb:79:in `update_stylesheets'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin.rb:77:in `each'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin.rb:77:in `update_stylesheets'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin.rb:51:in `check_for_updates'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/plugins/haml/
rails/../lib/sass/plugin/rack.rb:40:in `call'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rack-cache/lib/
rack/cache/context.rb:123:in `forward'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rack-cache/lib/
rack/cache/context.rb:207:in `fetch'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rack-cache/lib/
rack/cache/context.rb:161:in `lookup'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rack-cache/lib/
rack/cache/context.rb:64:in `call!'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rack-cache/lib/
rack/cache/context.rb:50:in `call'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rails/actionpack/
lib/action_controller/string_coercion.rb:25:in `call'
/home/slugs/287995_8159aab_483e/mnt/.gems/gems/rack-1.1.0/lib/rack/
head.rb:9:in `call'
/home/slugs/287995_8159aab_483e/mnt/.gems/gems/rack-1.1.0/lib/rack/
methodoverride.rb:24:in `call'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rails/actionpack/
lib/action_controller/params_parser.rb:15:in `call'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rails/actionpack/
lib/action_controller/session/cookie_store.rb:99:in `call'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rails/actionpack/
lib/action_controller/failsafe.rb:26:in `call'
/home/slugs/287995_8159aab_483e/mnt/.gems/gems/rack-1.1.0/lib/rack/
lock.rb:11:in `call'
/home/slugs/287995_8159aab_483e/mnt/.gems/gems/rack-1.1.0/lib/rack/
lock.rb:11:in `synchronize'
/home/slugs/287995_8159aab_483e/mnt/.gems/gems/rack-1.1.0/lib/rack/
lock.rb:11:in `call'
/disk1/home/slugs/287995_8159aab_483e/mnt/vendor/rails/actionpack/
lib/action_controller/dispatcher.rb:106:in `call'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/rack/adapter/
rails.rb:74:in `call'
/home/heroku_rack/lib/static_assets.rb:9:in `call'
/home/heroku_rack/lib/last_access.rb:25:in `call'
/home/slugs/287995_8159aab_483e/mnt/.gems/gems/rack-1.1.0/lib/rack/
urlmap.rb:47:in `call'
/home/slugs/287995_8159aab_483e/mnt/.gems/gems/rack-1.1.0/lib/rack/
urlmap.rb:41:in `each'
/home/slugs/287995_8159aab_483e/mnt/.gems/gems/rack-1.1.0/lib/rack/
urlmap.rb:41:in `call'
/home/heroku_rack/lib/date_header.rb:14:in `call'
/home/slugs/287995_8159aab_483e/mnt/.gems/gems/rack-1.1.0/lib/rack/
builder.rb:77:in `call'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
connection.rb:76:in `pre_process'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
connection.rb:74:in `catch'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
connection.rb:74:in `pre_process'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
connection.rb:57:in `process'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
connection.rb:42:in `receive_data'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/
eventmachine.rb:256:in `run_machine'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/
eventmachine.rb:256:in `run'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/backends/
base.rb:57:in `start'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
server.rb:156:in `start'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
controllers/controller.rb:80:in `start'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
runner.rb:177:in `send'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
runner.rb:177:in `run_command'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/lib/thin/
runner.rb:143:in `run!'
/usr/ruby1.8.7/lib/ruby/gems/1.8/gems/thin-1.2.6/bin/thin:6
/usr/ruby1.8.7/bin/thin:19:in `load'
/usr/ruby1.8.7/bin/thin:19


Processing SiteController#show_page (for 165.88.106.230 at 2010-09-14
08:39:34) [GET]
Parameters: {"url"=>"/", "action"=>"show_page",
"controller"=>"site"}
Completed in 297ms (DB: 32) | 200 [http://blazing-
river-34.heroku.com/]


Processing SiteController#show_page (for 165.88.106.230 at 2010-09-14
08:39:48) [GET]
Parameters: {"url"=>["about"], "action"=>"show_page",
"controller"=>"site"}
Completed in 261ms (DB: 33) | 200 [http://blazing-river-34.heroku.com/
about/]


Processing SiteController#show_page (for 165.88.106.230 at 2010-09-14
08:39:53) [GET]
Parameters: {"url"=>["2"], "action"=>"show_page",
"controller"=>"site"}
Completed in 386ms (DB: 32) | 404 [http://blazing-river-34.heroku.com/
2]



I have read heroku's read only file system documentation and
configured cache settings accordingly.

Is it heroku problem or something to do with radiant config settings

Any help, pointer would be appreciated.
Thanks,
-Sachin

[سيف‎]

2010/9/15 Sachin <brigh...@gmail.com>

[john]

On Sep 15, 5:00 am, Sachin <brightsp...@gmail.com> wrote:
> I have deployed radiant app (cloned freshly from github) on heroku
> without using
> gem.
>
> After a restart or after the app comes out of idle mode, there is
> read-
> only-filesystem-error for one of the css file. On immediate subsequent
> requests the error is not seen. Everything works fine after that.
>
> # Logfile created on Tue Sep 14 08:39:25 -0700 2010/!\ FAILSAFE /!\
> Tue Sep 14 08:39:29 -0700 2010
>  Status: 500 Internal Server Error
>  Read-only file system - /disk1/home/slugs/287995_8159aab_483e/mnt/
> public/stylesheets/admin/main.css

i'd guess that's because edge (what you get by default when you clone
from github) requires compass which attempts to compile css when the
app starts. try running in production locally and committing the
generated css files to your repo.

[sachin kale]

Thanks John,

That solved the problem.
After running production locally, the error was still there until I manually deleted the "/public/stylesheets/admin/sass" directory.

Thanks Again for your help.

--
Sachin Kale

www.ednexa.com