Welcome Guest Login Register Member List
ExpressionEngine Forums
Advanced Search
Username: Password:
Remember Me? forgot password?
You are here: Forum Home  >  Installation  >  Linux  >  Thread
   
 
Problem running Tracks 1.041 on Open Suse 10.1
 
br0sk
Posted: 31 July 2006 10:50 AM   [ Ignore ]  
Newbie
Rank
Total Posts:  2
Joined  2006-07-31

Hi all,

I am trying to install tracks un Open suse 10.1 but I ran in to some problems.

1. The version of Tracks you’re using
1.041

2. The platform you have Tracks installed on (Windows, Mac or Linux)
Linux Open Suse 10.1

3. The browser you are using
Firefox 1.5.0.5, IE 6

4. Any other relevant information (e.g. version of Ruby used, whether you are using Locomotive or InstantRails, etc.)
Installed via yast.
ruby 1.8.4 (2005-12-24) [x86_64-linux]
Rails 1.1.4
Mysql 5.0.18
WEBrick 1.3.1


I have a test application using ruby that is working just fine with adding, editing and removing data base entries.
When I installed the rails everything seemed to be working quite nicely. I was able register my self as the first user. I loaded the database with the test data from the installation instructions. The problem now is that only some of the functionality in rails i working.

I can reach and use the http://0.0.0.0:3000/contexts on the machine where tracks is installed. I can drag and drop sort the list and the changes I make are reflected in the database.

If I try to access e.g. http://0.0.0.0:3000/projects I get this:

NameError in <controller not set>#<action not set>

uninitialized constant ProjectController

RAILS_ROOT: script/../config/..

Full trace:
./script/../config/../vendor/rails/activesupport/lib/active_support/dependencies.rb:89:in `const_missing’
./script/../config/../vendor/rails/activesupport/lib/active_support/dependencies.rb:120:in `const_missing’
generated/routing/recognition.rb:4:in `recognize_path’
./script/../config/../vendor/rails/actionpack/lib/action_controller/routing.rb:477:in `recognize!‘
./script/../config/../vendor/rails/railties/lib/dispatcher.rb:38:in `dispatch’
./script/../config/../vendor/rails/railties/lib/webrick_server.rb:115:in `handle_dispatch’
./script/../config/../vendor/rails/railties/lib/webrick_server.rb:81:in `service’
/usr/lib64/ruby/1.8/webrick/httpserver.rb:104:in `service’
/usr/lib64/ruby/1.8/webrick/httpserver.rb:65:in `run’
/usr/lib64/ruby/1.8/webrick/server.rb:173:in `start_thread’
/usr/lib64/ruby/1.8/webrick/server.rb:162:in `start_thread’
/usr/lib64/ruby/1.8/webrick/server.rb:95:in `start’
/usr/lib64/ruby/1.8/webrick/server.rb:92:in `start’
/usr/lib64/ruby/1.8/webrick/server.rb:23:in `start’
/usr/lib64/ruby/1.8/webrick/server.rb:82:in `start’
./script/../config/../vendor/rails/railties/lib/webrick_server.rb:67:in `dispatch’
./script/../config/../vendor/rails/railties/lib/commands/servers/webrick.rb:59
./script/../config/../vendor/rails/activesupport/lib/active_support/dependencies.rb:136:in `require’
./script/../config/../vendor/rails/railties/lib/commands/server.rb:30
script/server:3

If I try to access e.g. http://0.0.0.0:3000/ I get this:
NameError in <controller not set>#<action not set>

uninitialized constant TodoController

RAILS_ROOT: script/../config/..

Full trace:
./script/../config/../vendor/rails/activesupport/lib/active_support/dependencies.rb:89:in `const_missing’
./script/../config/../vendor/rails/activesupport/lib/active_support/dependencies.rb:120:in `const_missing’
generated/routing/recognition.rb:4:in `recognize_path’
./script/../config/../vendor/rails/actionpack/lib/action_controller/routing.rb:477:in `recognize!‘
./script/../config/../vendor/rails/railties/lib/dispatcher.rb:38:in `dispatch’
./script/../config/../vendor/rails/railties/lib/webrick_server.rb:115:in `handle_dispatch’
./script/../config/../vendor/rails/railties/lib/webrick_server.rb:81:in `service’
/usr/lib64/ruby/1.8/webrick/httpserver.rb:104:in `service’
/usr/lib64/ruby/1.8/webrick/httpserver.rb:65:in `run’
/usr/lib64/ruby/1.8/webrick/server.rb:173:in `start_thread’
/usr/lib64/ruby/1.8/webrick/server.rb:162:in `start_thread’
/usr/lib64/ruby/1.8/webrick/server.rb:95:in `start’
/usr/lib64/ruby/1.8/webrick/server.rb:92:in `start’
/usr/lib64/ruby/1.8/webrick/server.rb:23:in `start’
/usr/lib64/ruby/1.8/webrick/server.rb:82:in `start’
./script/../config/../vendor/rails/railties/lib/webrick_server.rb:67:in `dispatch’
./script/../config/../vendor/rails/railties/lib/commands/servers/webrick.rb:59
./script/../config/../vendor/rails/activesupport/lib/active_support/dependencies.rb:136:in `require’
./script/../config/../vendor/rails/railties/lib/commands/server.rb:30
script/server:3


This is what I get in the console window when I start ruby
ruby script/server -e development
=> Booting WEBrick…
=> Rails application started on http://0.0.0.0:3000
=> Ctrl-C to shutdown server; call with—help for options
[2006-07-31 11:16:37] INFO WEBrick 1.3.1
[2006-07-31 11:16:37] INFO ruby 1.8.4 (2005-12-24) [x86_64-linux]
[2006-07-31 11:16:37] INFO WEBrick::HTTPServer#start: pid=689 port=3000

Does anybody have any suggestions about how to fix this problem?

Profile
 
br0sk
Posted: 09 August 2006 10:49 AM   [ Ignore ]   [ # 1 ]  
Newbie
Rank
Total Posts:  2
Joined  2006-07-31

I managed to get it working now.

The problem was that I was donloading the files to a windows machine and transferred the unzipped files via ftp. For some reason the the ftp client(or server) did not like to put the .htaccess files on the server. The solution was to move the tracks zip file to the server and just unpack it on top of the already excisting files in the tracks installation directory. Everything is fine now and I can verify that tracks is working just fine on Suse Linux 10.1.

Maybe this thread will save someone some debugging time….

Profile
 
   
 
 
‹‹ Umlaut Problem with Tracks and Apache2      Trouble installing publicly-accessible w/ apache (debian stable) ››

Powered By ExpressionEngine
Template Design By Sonnenvogel.com
Select a theme:

ExpressionEngine Discussion Forum - Version 2.1.1 (20081028)
Script Executed in 0.1200 seconds

Atom Feed
RSS 2.0