500 Internal Server Error in Ruby


#1

Hi,

The mini ruby profiler is causing a “Internal Server Error” the error is:

[Fri Jul 27 19:16:22 2012] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.2 with Suhosin-Patch Phusion_Passenger/3.0.13 configured -- resuming normal operations

[ pid=5961 thr=3074713984 file=ext/apache2/Hooks.cpp:848 time=2012-07-27 19:16:36.338 ]: The backend application (process 6009) didn't send a valid HTTP response. It might have crashed during the middle of sending an HTTP response, so please check whether there are crashing problems in your application.

This is the data that it sent: [8dsbp","d4ebq9agdwv8q3d2eod5","moe51mopk64x82bqi71m","ftc0qemnxi3qcqae6qgt","ptdje6lgzh9ursxf6sso","7gpcvxsp72i5904qsntw","wq2m5c6967jrh2hp9wdc","e8ram1eb4l4xcerun1tw","y1lasuksqjugfphc524s","bzif8pmo8alwrld869mr","x9lzg5c5ikdnl8ymlldx","fvhkmfzlsw7urqm81z2l","r9ygdjieyp62p9rv21nc","2hbloqbylsavwvyo309h","5dqzla34i0yvy81vf33q","57djb5gi8c4hvhab426p","ybvh63kiwsso7pez3mtf","45j6timrccma19buw5bz","e5ufyfuvhyvgup3zm0xk","g1mnxdg5lr8u3dthb2xa","wvpsvzkg8erq1axoi3l4","wzpjs4b3enfafwit3tms","zd9ctqkb6jtzndbcip4g","3t9v9lws9go3zse3p5ik","cq7iajrcsjzbzejlnd0o","2tdy26geoxdqrdq11rob","b1jsypaf3s49cjn8yhow","ujyzvflpn0gctgazabq9","rqdjm2so2hef5gmozkju","njvbnpaczzo5poaubs0v","2e44fau36clbbgxp8pql","h479vnu175usg4ur09aa","ivvv3q5lj4vafnlq0cyb","mtb6j207wrsfhtbxzqot"]]

I’m using Rails 3.2.6

If you need anything else please let me know.

Many thanks


#2

Can you test the latest source at Github?


#3

should be fixed in latest (0.1.8) please confirm


#4

@sam I’m still getting it: rails 3.2.7 and 0.1.9 (sorry I didn’t get an email when this thread was updated)


#5

We’re still seeing this in MiniProfiler 0.1.27.

Usually after a longer wait time where the local development server is not running (say overnight) this will crop up the next morning:

!! Unexpected error while processing request: No such file or directory - /Users/user/code/project/tmp/miniprofiler/mp_views_3b8d0774d3f759f36dd96f694bb39df4


#7

This is likely happening due to purge rules, we only keep data around for 24 hours see:

Open to have a PR that makes this more configurable.