straightflush at gmail.com
2007-Apr-23 14:49 UTC
[Mongrel] mongrel in production not using AR Sessions
Hello, For some reason when i change the "environments" line in mongrel_cluster.yml to use production, ActiveRecord Sessions stop working. Changing this line to development yield the correct result. Entries in database.yml are correct, and confirmed that the sessions table exists in both environments and that production is indeed working (production.logbeing filled up). Any idea why this would happen ? Thanks Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20070423/10aa09de/attachment-0001.html
Are session entries being created in the table? Is your config.action_controller.session_store = :active_record_store line somehow restricted to development? Does setting the environment as an env variable or forcing it in production in environment.rb change things? What happens if you clone the dev database to the production database? (of course, do this only on your dev box ;-) Does it work with Webrick? -Nate On Apr 23, 2007, at 9:49 AM, straightflush at gmail.com wrote:> Hello, > > For some reason when i change the "environments" line in > mongrel_cluster.yml to use production, ActiveRecord Sessions stop > working. > Changing this line to development yield the correct result. > Entries in > database.yml are correct, and confirmed that the sessions table > exists in > both environments and that production is indeed working > (production.logbeing filled up). > > Any idea why this would happen ? > > Thanks > Adam > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users
straightflush at gmail.com
2007-Aug-04 03:15 UTC
[Mongrel] mongrel in production not using AR Sessions
Nathan, It does not work with webrick Restoring dev db to prod does not work Not sure how this config entry would not be picked up by production environment, environment.rb is all environments Thanks for the help, any other ideas on how to best debug here ? On 4/23/07, Nathan Vack <njvack at wisc.edu> wrote:> > Are session entries being created in the table? Is your > config.action_controller.session_store = :active_record_store line > somehow restricted to development? Does setting the environment as an > env variable or forcing it in production in environment.rb change > things? > > What happens if you clone the dev database to the production > database? (of course, do this only on your dev box ;-) > > Does it work with Webrick? > > -Nate > > On Apr 23, 2007, at 9:49 AM, straightflush at gmail.com wrote: > > > Hello, > > > > For some reason when i change the "environments" line in > > mongrel_cluster.yml to use production, ActiveRecord Sessions stop > > working. > > Changing this line to development yield the correct result. > > Entries in > > database.yml are correct, and confirmed that the sessions table > > exists in > > both environments and that production is indeed working > > (production.logbeing filled up). > > > > Any idea why this would happen ? > > > > Thanks > > Adam > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20070803/a0574412/attachment.html
straightflush at gmail.com
2007-Aug-04 03:29 UTC
[Mongrel] mongrel in production not using AR Sessions
figured it out. For some reason it was the acts_as_cached plugin in the vendor/plugins directory and this was completely screwing it up. Removing this from plugins fixed it. Not sure why this plugin would override the default behavior but looks like i was using memcached for sessions without asking for it.... Thanks for the help. On 8/3/07, straightflush at gmail.com <straightflush at gmail.com> wrote:> > Nathan, > > It does not work with webrick > Restoring dev db to prod does not work > Not sure how this config entry would not be picked up by production > environment, environment.rb is all environments > > Thanks for the help, any other ideas on how to best debug here ? > > > > On 4/23/07, Nathan Vack <njvack at wisc.edu> wrote: > > > > Are session entries being created in the table? Is your > > config.action_controller.session_store = :active_record_store line > > somehow restricted to development? Does setting the environment as an > > env variable or forcing it in production in environment.rb change > > things? > > > > What happens if you clone the dev database to the production > > database? (of course, do this only on your dev box ;-) > > > > Does it work with Webrick? > > > > -Nate > > > > On Apr 23, 2007, at 9:49 AM, straightflush at gmail.com wrote: > > > > > Hello, > > > > > > For some reason when i change the "environments" line in > > > mongrel_cluster.yml to use production, ActiveRecord Sessions stop > > > working. > > > Changing this line to development yield the correct result. > > > Entries in > > > database.yml are correct, and confirmed that the sessions table > > > exists in > > > both environments and that production is indeed working > > > (production.logbeing filled up). > > > > > > Any idea why this would happen ? > > > > > > Thanks > > > Adam > > > _______________________________________________ > > > Mongrel-users mailing list > > > Mongrel-users at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20070803/94aec430/attachment-0001.html