/admin problems

Ruby Apps Radiant CMS
1

I’ve seen this one posted, but not the solution.

I have Radiant installed and the site section is working
fine, but I get an application error when I try to go to
the admin section. Running it with webrick locally on OS
X machine.

Anyone have any ideas?

Thanks.

2

Could you please post the exact error output text?

3

Output is

Application error (Apache)

Change this error message for exceptions thrown outside of
an action (like in Dispatcher setups or broken Ruby code)
in public/500.html

On Tue, 28 Nov 2006 21:40:09 -0500

4

That’s an internal server error. Then you might have WebBrick and
apache trying to listen to the same port or have the
radiantDir/public/dispatcher.rb misconfigured.

5

John F. wrote:

Output is

Application error (Apache)

Change this error message for exceptions thrown outside of
an action (like in Dispatcher setups or broken Ruby code)
in public/500.html

We need to see the error from the logs. Look for the one that is
relevant to the mode (production|development) that you are running in.

–
John L.
http://wiseheartdesign.com

6

It seems that you need to give Apache read/write access to the script
folder. sudo chmod -R 755 ./script should help.

7

Here it is:

Permission denied -
script/…/config/…/tmp/sessions//ruby_sess.b794dd418e29357b
/usr/lib/ruby/1.8/pstore.rb:101:in initialize' /usr/lib/ruby/1.8/pstore.rb:101:inopen’
/usr/lib/ruby/1.8/pstore.rb:101:in transaction' /usr/lib/ruby/1.8/cgi/session/pstore.rb:71:ininitialize’
/usr/lib/ruby/1.8/cgi/session.rb:273:in new' /usr/lib/ruby/1.8/cgi/session.rb:273:ininitialize’
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_process.rb:112:in
new' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_process.rb:112:insession’
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_process.rb:108:in
stale_session_check!' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_process.rb:108:insession’
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:918:in
assign_shortcuts_without_flash' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/flash.rb:141:inassign_shortcuts’
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:402:in
process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:377:inprocess_without_session_management_support’
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:in
process' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:indispatch’
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/webrick_server.rb:115:in
handle_dispatch' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/webrick_server.rb:81:inservice’
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in service' /usr/lib/ruby/1.8/webrick/httpserver.rb:65:inrun’
/usr/lib/ruby/1.8/webrick/server.rb:155:in start_thread' /usr/lib/ruby/1.8/webrick/server.rb:144:instart’
/usr/lib/ruby/1.8/webrick/server.rb:144:in start_thread' /usr/lib/ruby/1.8/webrick/server.rb:94:instart’
/usr/lib/ruby/1.8/webrick/server.rb:89:in each' /usr/lib/ruby/1.8/webrick/server.rb:89:instart’
/usr/lib/ruby/1.8/webrick/server.rb:79:in start' /usr/lib/ruby/1.8/webrick/server.rb:79:instart’
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/webrick_server.rb:67:in
dispatch' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/commands/servers/webrick.rb:59 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:ingem_original_require’
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
require' /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:inrequire’
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/commands/server.rb:30
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
gem_original_require' /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:inrequire’
/usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:in
`require’
script/server:3

On Tue, 28 Nov 2006 22:06:29 -0500

8

I usually get that problem with new Rails applications when the tmp/
directory doesn’t exist (especially if I checked them out of an SVN
repo). Go to the root of your Radiant installation and run rake tmp:create . If it’s already there, you may have to chmod -R.

Sean C.
seancribbs.com

9

Thanks. It was the permissions on the tmp directory.

Daniel S. wrote:

To: [email protected]

Permission denied -
script/…/config/…/tmp/sessions//ruby_sess.b794dd418e29357b

Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant

–

John F.
Digital Systems and Services Coordinator
MBLWHOI Library
Woods Hole MA 02543 USA
PHONE: 508-289-7435
EMAIL: [email protected]
http://www.mblwhoilibrary.org

10

Yup. I usually use the recursive flag because I’m sure with all
metaprogramming Rails does it probably uses tmp directories a lot. Not
to mention session storage and management. So even though this time
was easy to isolate to /tmp/sesh it’s just better to chmod the whole
folder and its children.

11

Actually, it needs read/write access to tmp/sessions (actually, all of
tmp)

12

The metaprogramming doesn’t really affect or deal with the tmp/
directory per
se (There’s no compilation so you don’t have to rewrite class-files when
you
add to a class or change something). However, it is used to store
session
files, IPC sockets (for FCGI, etc), and the page/fragment cache – all
of
which are transient data that a running app needs.

Sean