It looks like the server's internal @socket was set to nil somehow. Do this for me on your servers:
1) Start them up like normal in production mode. 2) killall -USR1 mongrel_rails Let it run, and when you hit this error again you'll get a stack trace. Send that to me so I can fix it. Thanks. On Fri, 22 Dec 2006 02:49:08 +0100 Gitte Wange <[EMAIL PROTECTED]> wrote: > Hi ! > > My mongrel just starting spitting out these nice lines: > The error occured while evaluating nil.accept. TELL ZED HE'S A MORON. > !!!!!! UNHANDLED EXCEPTION! You have a nil object when you didn't > expect it! > > Not sure what happened or why, but just FYI: Zed, you are a moron :-) > > > > Happy holidays! > Gitte Wange > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/ http://www.awprofessional.com/title/0321483502 -- The Mongrel Book http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help. _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
