10% 500 Errors

Server NGINX
21

Not that I know of, but the root cause appears to be an uncaught
exception in the exception handler code.

The failsafe code in dispatcher.rb is utterly obfuscated, one of the
guys in our team has patched it to return 500 properly, but that
hasn’t been submitted back to rails core.

Regardless, the REAL cause of the exception will be in your
production.log.

Cheers

Dave

22

It isn’t. There’s absolutely nothing in the production log.

23

Could it be a permission problem? i.e. something’s trying to write to an
empty log but doesn’t have permission, so dies without telling anyone?

James Golick wrote:

that hasn't been submitted back to rails core.

Dave - is there any common reason that might be happening
       What about hacking a quick controller to respond with the
    no idea.
    > > >
    > > > On Mon, Mar 10, 2008 at 10:10 AM, Igor S.
    > > > > > servers.
    Golick wrote:
    > > > > > > --
    > >

–

Phillip B Oldham
The Activity People
[email protected] mailto:[email protected]

Policies

This e-mail and its attachments are intended for the above named
recipient(s) only and may be confidential. If they have come to you in
error, please reply to this e-mail and highlight the error. No action
should be taken regarding content, nor must you copy or show them to
anyone.

This e-mail has been created in the knowledge that Internet e-mail is
not a 100% secure communications medium, and we have taken steps to
ensure that this e-mail and attachments are free from any virus. We must
advise that in keeping with good computing practice the recipient should
ensure they are completely virus free, and that you understand and
observe the lack of security when e-mailing us.

24

Thanks for the reply, Ezra.

Everything looks kosher there, too. However, the problem is now solved -
we
moved to thin! :slight_smile:

J.

On Mon, Mar 10, 2008 at 3:03 PM, Ezra Z. [email protected]

25

James-

Please double count the number of mongrels you have running and the
ports they run on and then doublecheck the upstream block in your
nginx.conf to make sure it matches exactly. Also restart all of your
mongrels so they are fresh.

We usually see this error when the number of running mongrels is
changed without updating the number of servers in the upstream block.

Cheers-
-Ezra

On Mar 11, 2008, at 10:34 AM, Aníbal Rojas wrote:

On Tue, Mar 11, 2008 at 10:08 AM, James Golick

status.
upstream

Igor S.
–

Igor S.
Igor Sysoev