Mongrel hanging on exit. Reaping threads

Greetings,

I’m using the net-ping library within a Rails app to determine server
status. However, whenever the action which utilizes the net-ping lib
is run, it appears to cause a “rogue” thread. The following appears
when I attempt to shutdown the mongrel server:


Thu Jul 12 05:51:31 -0500 2007: Reaping 1 threads for slow workers
because of ‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:51:37 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:51:43 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:51:49 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:51:55 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:52:01 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:52:07 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:52:13 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:52:19 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:52:25 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Waiting for 1 requests to finish, could take 60 seconds.Thu Jul 12
05:52:31 -0500 2007: Reaping 1 threads for slow workers because of
‘shutdown’
Thread #<Thread:0x3320cc8 sleep> is too old, killing.
Waiting for 0 requests to finish, could take 60 seconds.Exiting


Any pointers on how I can troubleshoot this?

Thank you for your time,
Tricon

Ahh, just figured it out.

I relocated my “require” call, problem solved.

Thanks for looking,
Tricon