Hi,
We just added a piece of code that queries an API using net/http when a visitor visits a certain page on our site. This block of code is also surrounded by a timeout block, just in case it takes too long querying the API, we don't want it to hang for the visitor. Once we added this, our vhost root started filling up with core dump files. I'm not all that well versed with reading coredump files, but it seems to be saying this:
Core was generated by `ruby /opt/lsws/fcgi-bin/RailsRunner.rb'.
Program terminated with signal 6, Aborted.
---Type <return> to continue, or q <return> to quit---
#0 0xb7e42518 in raise () from /lib/tls/libpthread.so.0
Not sure if that's helpful, is there a way to get something more useful out of it? I can also send you a link to download the core file if that would be helpful.
I'd say this page gets about 1 req/s, and we are getting a new core dump file every 15 minutes or so.
Thanks,
Chris
We just added a piece of code that queries an API using net/http when a visitor visits a certain page on our site. This block of code is also surrounded by a timeout block, just in case it takes too long querying the API, we don't want it to hang for the visitor. Once we added this, our vhost root started filling up with core dump files. I'm not all that well versed with reading coredump files, but it seems to be saying this:
Core was generated by `ruby /opt/lsws/fcgi-bin/RailsRunner.rb'.
Program terminated with signal 6, Aborted.
---Type <return> to continue, or q <return> to quit---
#0 0xb7e42518 in raise () from /lib/tls/libpthread.so.0
Not sure if that's helpful, is there a way to get something more useful out of it? I can also send you a link to download the core file if that would be helpful.
I'd say this page gets about 1 req/s, and we are getting a new core dump file every 15 minutes or so.
Thanks,
Chris