"Segmentation Fault" error when I try to get cached data.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I use Redis for caching MongoDB calls. Data are small stringified Json. It 
works on my local linux server but...
2. ...
3. ...

What is the expected output? What do you see instead?
On my Linux VPS (on my win7 netbook) it works perfectly. Online, on a powerful 
server, every attempt to get cached data crashes with the error: "Segmentation 
fault".

What version of the product are you using? On what operating system?
The latest stable. Ubuntu server.

Please provide any additional information below.
It is very strange, because the app is built on node.js and I use connect-redis 
to manage the session with Express.js. That part works perfectly. The 
minimalistic cache system, instead, in local works perfectly, online crashes. 
But the local VPS is an identical copy of the online server, because I 
parallelly installed (and upgraded) the two systems.

Original issue reported on code.google.com by sul...@gmail.com on 27 Jan 2011 at 10:34

[GoogleCodeExporter]

Hello, thanks for reporting.

We need some additional info:

- The version of the Redis server.
- The stack trace it prints after crashing.
- Is this version the default installed by Ubuntu, or did you compiled it 
yourself?

Thanks,
Salvatore

Original comment by anti...@gmail.com on 27 Jan 2011 at 10:41

[GoogleCodeExporter]

Hello, I just received your email.

I recently upgraded to Redis 2.0.4.
The server is a minimal (but standard) Ubuntu Server.
The only error reported in Redis logs says

WARNING overcommit_memory is set to 0! Background save may fail under low
memory condition. To fix this issue add 'vm.overcommit_memory = 1' to
/etc/sysctl.conf and then reboot or run the command 'sysctl
vm.overcommit_memory=1' for this to take effect.

I fixed this value but the crash continues. Apparently the setex works well
but when I try to get the json it crashes. Consider that the every json
string is minus then 10K.
When I launch my node.js app the log of the app reports nothing about the
error. I simply see that the app crashes because after a while I can see the
restarting string (forced by Monit). If you let me know where I can find
info about the memory stack I will do all the necessary to provide you with
the info.
Thanks a lot,
F

Original comment by sul...@gmail.com on 9 Feb 2011 at 1:39

[GoogleCodeExporter]

When Redis crashes, it dumps a stack trace to the log file. It would be very 
helpful if you provide this stack trace, the output of the INFO command, and 
your configuration file. Thanks.

Original comment by pcnoordh...@gmail.com on 9 Feb 2011 at 8:19

[GoogleCodeExporter]

Hello, if this does not work we can even provide you our public key and check 
ourselves inside the server to see what's happening.

Thanks for the report & help.

Cheers,
Salvatore

Original comment by anti...@gmail.com on 9 Feb 2011 at 9:22