#267 ✓resolved
Chad Woolley

Remaining issues with Rails Upgrade

Reported by Chad Woolley | July 26th, 2009 @ 10:14 PM

Here's what I found:

  • Migrations did not run in daemonized mode, had to start in non-daemon mode:
woolley@thewoolleyweb:~/ccrb$ ./cruise start -d
=> Booting Mongrel
=> Rails 2.3.2 application starting on http://0.0.0.0:3333
woolley@thewoolleyweb:~/ccrb$ ./cruise start 
=> Booting Mongrel
=> Rails 2.3.2 application starting on http://0.0.0.0:3333
cruise data root = '/home/woolley/.cruise'
[info]  Executing migration script 002_move_custom_files_to_directory_in_user_home.rb. This may take some time...
[info]  Finished 002_move_custom_files_to_directory_in_user_home.rb.
=> Call with -d to detach
=> Ctrl-C to shutdown server
^CExiting
  • The PID file being dropped in tmp/pids is wrong. Used to be "mongrel.pid", now is "server.pid". This may just need to be changed to server.pid in daemon/daemon_helper.pid - if so that's an easy change, and I can make it if needed, but not positive if this is the only place it is still referenced.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

People watching this ticket

Pages