Removing the session files worked for me…I had to
do it after switching versions and port for mysql.
Presumably old connection info was in sesion files.
sudden the page will be erased to blank!
Any idea what could cause something like this?
If you’re running WEBrick, try to remove the ruby session files in /tmp.
When using a rails app we have been experiencing sudden blank pages in
the browser.
We show an model “new object” page and start changing stuff and all
of a
sudden the page will be erased to blank!
Any idea what could cause something like this?
If you’re running WEBrick, try to remove the ruby session files in /tmp.
*m
I saw this when switching to DB driven sessions in the environment.rb.
It worked for a while and then all of a sudden, everything was blank. I
turned it off for the moment (back to /tmp) and it is all good. Sorry,
no solution.
Today, I had a problem with sessions that caused that problem. The
session table you can create with rake will use a TEXT column for data,
this tops out at 64KB. I changed this to LONGTEXT and the problem went
away.
More info: This usually happens while data is being entered into one
particular page (the page that is used most often in the app). You will
be entering data normally then BAM a blank page. Weird
I saw this when switching to DB driven sessions in the environment.rb.
It worked for a while and then all of a sudden, everything was blank. I
turned it off for the moment (back to /tmp) and it is all good. Sorry,
no solution.
We’ve seen behaviour in development mode where an application using
DB-backed sessions will suddenly fail because it tries to revert to
pstore sessions - production mode fixes this though. This behaviour
was also in Rails of yore, so it might’ve been fixed, but the
description matches what you’ve got, Fredrik.