# :serialize "rot" after some time?

**URL:** <https://www.ruby-forum.com/t/serialize-rot-after-some-time/149003>\
**Category:** Rails\
**Created:** [September 19, 2008, 8:34am UTC](https://www.ruby-forum.com/t/serialize-rot-after-some-time/149003 "2008-09-19T08:34:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![macdigger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/13edae/32.png) [@macdigger](https://www.ruby-forum.com/u/macdigger)\
**Post date:** [September 19, 2008, 8:34am UTC](https://www.ruby-forum.com/t/serialize-rot-after-some-time/149003/1 "2008-09-19T08:34:36Z")

</div>

Hi all,

I have some very weird problems going on with some Ruby on Rails  
(2.0.2)-driven sites on my server (which is RHEL 4.5, running Apache  
2.2, Mongrel cluster)

Basically, everything works perfect after my mongrel clusters just  
launched, but as time passes (and it could be several hours or several  
days in some cases), serialized values of my apps start failing to  
return correct values (returning nils) during deserializing, and start  
failing to serialize values correctly.

Again, everything works just absolutely perfectly fine for some time, so  
this is not a problem with my code being wrong or something…

It is all fixed by restarting Mongrel instances, but I wonder if anybody  
knows what’s up with this problem? I tried different versions of ruby  
(currently running 1.8.6p287), and don’t want to upgrade to 1.8.7 yet  
(have too many systems, some running on Rails 1.2…)

Would be really greatful for any input on this issue, as I don’t even  
know where to start the goddamn debugging…