Authlogic crashes with infinite recursion

I have some problems using authlogic in my rails app, so I started using a blank example from github.com/binarylogic/authlogic_example which doesn't work as well.

I spent all day installing rubies 1.9.1 and 1.8 and jruby1.8, also didn't work. The most interesting thing is that there is another rails application running on my server. However, I just can't see where the code breaks or where the difference is. Here's the output that generic / log / mongrel_debug / threads.log gives:

Mon Oct 12 19:23:53 +0200 2009 REQUEST /favicon.ico
0.0.0.0:7102 -- THREADS: 1 -----
 KEYS:
  -- #<Thread:0x7ffe28347fc8>: [:started_on, :__recursive_key__]

      

Some time after the request, it expires at 500. I correctly assume that this is an infinite recursion in some piece of code?

My server config:

Linux xxxxxx 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:45:36 UTC 2009 x86_64
ruby 1.8.7 (2008-08-11 patchlevel 72) [x86_64-linux]
gem -v: 1.3.5
rails 2.3.4 (any lower version doesn't change it)

      

So far it doesn't depend on database or rails version. The only thing that allows the app to comment again is #acts_as_authenticated, so I guess there are some authlogic issues and my server conf. Locally it still works (OSX 10.6.1)

I have searched google for a few hours and have been building an authlogic app from scratch. If you have any idea what else I might find or what I might check, give me a hint!

Many thanks! Before

+2


source to share


2 answers


My colleague has another explanation:

config.cache_classes = true



Sets it to false.

+1


source


Finally I found a solution:



the database name and user had an underscore in it, and the password had special characters. By setting it to a simpler one, he solved it.

+1


source







All Articles