aC forum: Odd script timeout issue. Can native define() or dirname() functions hang?

Post #5 by chrisbloom7

chrisbloom7 — Wed, 23 Dec 2009 08:01:48 CST

I did clear the cache out yesterday. I don't suspect any file system/permissions issues because the cache files are being regenerated. I will refresh the permissions, re-clear the cache and continue to monitor.

Post #4 by Ilija Studen

Ilija Studen — Wed, 23 Dec 2009 01:56:10 CST

Try to clearing content of /cache folder and see if that helps. Still, there should be no reason for cache to choke the system, but based on error message that's the place where I would start.

Second, see with your system administrator whether there are any problems with file system access. Nothing should choke the script to take 30 seconds to execute though (all requests should be under 1 second on decent server)...

Post #3 by chrisbloom7

chrisbloom7 — Tue, 22 Dec 2009 22:56:12 CST

The exact error message was "Fatal error: Maximum execution time of 30 seconds exceeded". Looking at the PHP error log for the past month, I'm seeing a lot of that type of message, most pointing at similarly benign code. Some examples:

Maximum execution time of 30 seconds exceeded in C:\web\wwwroot\activecollab\angie\classes\NamedList.class.php on line 6

class NamedList extends AngieObject {

Maximum execution time of 30 seconds exceeded in C:\web\wwwroot\activecollab\application\modules\system\models\search_engines\MysqlSearchEngine.class.php on line 3

require_once SYSTEM_MODULE_PATH . '/models/search_engines/SearchEngine.class.php';

(There was no other error message here, such as one that might suggest the SYSTEM_MODULE_PATH constant was undefined, or that the include file couldn't be found.)

Maximum execution time of 30 seconds exceeded in C:\web\wwwroot\activecollab\angie\classes\cache\backend\FileCacheBackend.class.php on line 65
Maximum execution time of 30 seconds exceeded in C:\web\wwwroot\activecollab\angie\classes\cache\backend\FileCacheBackend.class.php on line 72
Maximum execution time of 30 seconds exceeded in C:\web\wwwroot\activecollab\angie\classes\cache\backend\FileCacheBackend.class.php on line 115
Maximum execution time of 30 seconds exceeded in C:\web\wwwroot\activecollab\angie\classes\cache\backend\FileCacheBackend.class.php on line 132
Maximum execution time of 30 seconds exceeded in C:\web\wwwroot\activecollab\angie\classes\cache\backend\FileCacheBackend.class.php on line 167

 65.        if(is_file($path)) {

 72.        } // if

115.      if(is_file($path)) {

132.      while(($entry = $d->read()) !== false) {

167.      } // foreach

There are many more of the same. I will try to compile some more examples.

Post #2 by Ilija Studen

Ilija Studen — Tue, 22 Dec 2009 19:53:35 CST

As you noticed, this is really simple code that should not result in any severe errors.

What type of timeout do you get (exact error message)? Execution time fatal error, memory limit error or?

Post #1 by chrisbloom7

chrisbloom7 — Tue, 22 Dec 2009 09:40:59 CST

I've started getting sporadic reports of script timeout errors when users are submitting ticket changes. The error code points to line 11 in activecollab\angie\classes\swiftmailer\Swift\ClassLoader.php, a seemingly benign line of code:

if (!defined("SWIFT_ABS_PATH")) define("SWIFT_ABS_PATH", dirname(__FILE__) . "/..");

I've never run into any issue with these two native functions, but I'm wondering if it might be an obscure permissions error or something. Any have any ideas?