Mongrel server core dump on Sun Solaris

I am running my Mongrel Web Server 1.1.5 on Sun Solaris 10 server with
Apache 2.2 proxy running with single Mongrel instance to handle my RoR
Web Applications request. My RoR web application was developped on
Windows plateform, once I svn my RoR souce codes to Sun Solaris Web
Application server and run the application through web browser. My
Mongrel Web server most time may die and a core dump file was created in
my RoR Web Application directory as showing below:

uname -a

SunOS Test-zone 5.10 Generic_137138-09 i86pc i386 i86pc

pwd

/opt/coolstack/apache2/htdocs/Jtooltest

ls -al

total 78234
drwxr-xr-x 14 root root 512 Apr 6 18:48 .
drwxr-xr-x 9 root root 512 Apr 7 04:55 …
drwxr-xr-x 7 root root 512 Apr 6 18:40 app
-rw-r–r-- 1 root root 153 Apr 6 18:41 Capfile
drwxr-xr-x 5 root root 512 Apr 6 18:41 config
-rw------- 1 root root 39992793 Apr 6 18:48 core
drwxr-xr-x 4 root root 512 Apr 6 18:40 db
drwxr-xr-x 3 root root 512 Apr 6 18:41 doc
drwxr-xr-x 4 root root 512 Apr 6 18:41 lib
-rw-r–r-- 1 root root 610 Apr 6 18:41 .loadpath
drwxr-xr-x 3 root root 512 Apr 6 18:40 log
-rw-r–r-- 1 root root 443 Apr 6 18:41 .project
drwxr-xr-x 6 root root 512 Apr 6 18:41 public
-rw-r–r-- 1 root root 307 Apr 6 18:41 Rakefile
-rw-r–r-- 1 root root 10619 Apr 6 18:41 README
drwxr-xr-x 5 root root 512 Apr 6 18:40 script
drwxr-xr-x 6 root root 512 Apr 6 18:41 .svn
drwxr-xr-x 7 root root 512 Apr 6 18:40 test
drwxr-xr-x 7 root root 512 Apr 6 18:40 tmp
drwxr-xr-x 4 root root 512 Apr 6 18:40 vendor

Can anybody give some help? Thanks in advance.

Kevin

===================================

P Please consider the environment before printing this e-mail

Cleveland Clinic is ranked one of the top hospitals
in America by U.S. News & World Report (2008).
Visit us online at http://www.clevelandclinic.org for
a complete listing of our services, staff and
locations.

Confidentiality Note: This message is intended for use
only by the individual or entity to which it is addressed
and may contain information that is privileged,
confidential, and exempt from disclosure under applicable
law. If the reader of this message is not the intended
recipient or the employee or agent responsible for
delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If
you have received this communication in error, please
contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy. Thank you.

Liao,

Did you ever figure this out? I am having this same issue and can not
figure it out.

On Thu, May 14, 2009 at 11:54 AM, Ryan G. [email protected]
wrote:

Liao,

Did you ever figure this out? I am having this same issue and can not
figure it out.

Use gdb to get a stack trace and see where the code is at when it
crashes.

If this happens reliably, you might also use strace to trace what is
happening right before it dumps core.

Kirk H.

Ryan G. wrote:

When I do mongrel_rails start the first request to the server goes off
w/o a hitch. However, the second request to the server seems to time out
and core dumps.

Running truss mongrel_rails start results in the same behaviour and
truss output ends with

Incurred fault #6, FLTBOUNDS %pc = 0xFEE7EE96
siginfo: SIGSEGV SEGV_MAPERR addr=0x8A24EE70
Received signal $11, SIGSEGV [caught]
siginfo: SIGSEGV SEGV_MAPERR addr=0x8A24E270

#pstack core

ends with these lines

fee85c45 rb_f_load (1, 8047750, 80903b4, fee7e4a4) + 5ad
fee7ed9a rb_call0 (80916b0, 80903b4, 25c1, 25c1, 1, 8047750) + 916
fee7fade rb_call1 (80916b0, 80903b4, 25c1, 1, 8047750, 1) + 346
fee6e12 rb_eval (80903b4, 8080770, fed6b090, fee665b5) + 2270
fee666bb ruby_run (29, fed6ed18, 80507f7, feffa840, 8047c78, feffa840) +
117
080507e9 ??? (3, 8047cbc, 8047ccc, fed6c6c0)
0805071d _start (3, 8047d8c, 8047da4, 0, 8047dcb) + 7d

Kirk H. wrote:

On Thu, May 14, 2009 at 11:54 AM, Ryan G. [email protected]
wrote:

Liao,

Did you ever figure this out? I am having this same issue and can not
figure it out.

Use gdb to get a stack trace and see where the code is at when it
crashes.

If this happens reliably, you might also use strace to trace what is
happening right before it dumps core.

Kirk H.

When I do mongrel_rails start the first request to the server goes off
w/o a hitch. However, the second request to the server seems to time out
and core dumps.

Running truss mongrel_rails start results in the same behaviour and
truss output ends with

Incurred fault #6, FLTBOUNDS %pc = 0xFEE7EE96
siginfo: SIGSEGV SEGV_MAPERR addr=0x8A24EE70
Received signal $11, SIGSEGV [caught]
siginfo: SIGSEGV SEGV_MAPERR addr=0x8A24E270