[ome-devel] Neverending image stats calculation with OME from CVS

[Curtis Rueden]

Some more information:

After a while, the offending processes keep respawn after I kill them.
I'm not sure what's going on, but this might be a hint:

curtis at skyking:~$ lsof|grep OME
apache2   4983       root  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   4983       root  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5072   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5072   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5073   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5073   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5074   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5074   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5075   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5075   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5076   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5076   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5077   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5077   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5078   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5078   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5079   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5079   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5119   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5119   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so
apache2   5122   www-data  mem       REG  254,0   73742     315726
/usr/local/lib/perl/5.8.7/auto/OME/Image/Pix/Pix.so
apache2   5122   www-data  mem       REG  254,0   18189    4882738
/OME/Inline/lib/auto/OME/Util/cURL_79e0/cURL_79e0.so

Dropping the OME database, deleting /OME, and doing a fresh install
does not halt the problem.

The only way I have found to bring Apache back under control is to
remove the OME.conf include from my Apache configuration.

On Jan 17, 2008 1:08 PM, Curtis Rueden <ctrueden at wisc.edu> wrote:
> Hi,
>
> I have been testing OME server from the latest CVS code for the past
> few days, and noticed a new problem on my system. After doing a
> successful image import, OME spawns another process to compute image
> statistics. Unfortunately, this process never ends, and consumes 100%
> CPU until I kill it -- actually, even if I do so, it comes back unless
> I log out of OME and aggressively kill hungry Apache processes.
>
> The weird thing is that I can view the Image details page just fine,
> and the three associated module executions are listed (image import,
> image statistics, stack statistics). But the tasks view shows that the
> image statistics task is eternally running.
>
> Any ideas? Is there an easier way to reliably instruct OME to
> terminate such running processes?
>
> Thanks,
> Curtis
>