This forum is in READ-ONLY mode.
You can look around, but if you want to ask a new question, please use the new forum.
Home » legacy support » symfony 1.0 » How do I debug this?
How do I debug this? [message #102218] Thu, 08 July 2010 19:58 Go to next message
balunadig  is currently offline balunadig
Messages: 5
Registered: August 2009
Junior Member
New to Symfony, but I am trying to debug an issue with an existing app running 1.0.16. Here is what I see in the log... Appreciate any and all help

Excerpts from the fo_dev.log...


1) Jul 08 12:44:18 symfony [info] {sfDoctrine Statement} executeQuery : SELECT c.id ....
... 8189, 8188, 8185, 8173, 8159, 8156, 8153, 8505, 8587, 8514, 8511, 8553, 8591, 8554, 8555, 8556, 8545, 8557, 8443, 8573, 8559, 8499, 8560, 8589 )
>>>
>>> Seems to hang here - the browser shows hourglass...
2) When click on another button on the browser, I see the following in the the log:

Jul 08 12:49:38 symfony [info] {sfRouting} connect "/captcha"
Jul 08 12:49:38 symfony [info] {sfContext} initialization
Jul 08 12:49:38 symfony [info] {sfController} initialization
Jul 08 12:49:38 symfony [info] {sfRouting} match route [map_action] "/map/:action/*"
Jul 08 12:49:38 symfony [info] {sfRequest} request parameters array ( 'action' => 'index', 'module' => 'map', 'borough' => 'manhattan',)
>>>>
3) When click on another button, I see the following in the log. The browser continues to show the hourglass...

Jul 08 12:51:26 symfony [info] {sfRouting} connect "/captcha"
Jul 08 12:51:26 symfony [info] {sfContext} initialization
Jul 08 12:51:26 symfony [info] {sfController} initialization
Jul 08 12:51:26 symfony [info] {sfRouting} match route [category_landing] "/categories/:id/:stripped_title"
Jul 08 12:51:26 symfony [info] {sfRequest} request parameters array ( 'id' => '30', 'stripped_title' => 'museums', 'module' => 'categories', 'action' => 'index',)
Re: How do I debug this? [message #102222 is a reply to message #102218 ] Thu, 08 July 2010 21:51 Go to previous messageGo to next message
balunadig  is currently offline balunadig
Messages: 5
Registered: August 2009
Junior Member
And when I run symfony from command line, I get:

PHP Fatal error: Call to undefined function sys_get_temp_dir() in /home/afta/plugins/sfDoctrinePlugin/data/tasks/sfPakeDoctrin e.php on line 2
Re: How do I debug this? [message #102251 is a reply to message #102218 ] Fri, 09 July 2010 12:11 Go to previous messageGo to next message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
I found this with some googling Wink

http://php.net/manual/en/function.sys-get-temp-dir.php

Look at the dependency info - you need to be running at least version 5.2.1 of PHP. These days I would recommend nothing less than 5.2.4, but make it as recent as you can (say the latest version of 5.2 if you don't want to jump to 5.3 yet).


Remember Palestine
Re: How do I debug this? [message #102272 is a reply to message #102251 ] Fri, 09 July 2010 16:54 Go to previous messageGo to next message
balunadig  is currently offline balunadig
Messages: 5
Registered: August 2009
Junior Member
Unfortunateely, upgrading php (to 5.2 or later) isn't an option.

Actually, I fixed sys_get_temp_dir() by simply providing '/tmp' and symfony no longer flags the errror:
PHP Fatal error: Call to undefined function sys_get_temp_dir() in /home/afta/plugins/sfDoctrinePlugin/data/tasks/sfPakeDoctrin e.php on line 2

Yet, I continue to have the problem described in my first post Sad
Re: How do I debug this? [message #102281 is a reply to message #102218 ] Fri, 09 July 2010 23:56 Go to previous messageGo to next message
balunadig  is currently offline balunadig
Messages: 5
Registered: August 2009
Junior Member
Stack traae I got when I rebooted the server...
at ()
in SF_ROOT_DIR/plugins/sfDoctrinePlugin/lib/doctrine/Doctrine/C onnection.php line 1074 ...


$name = 'Doctrine_Connection_' . $this->driverName . '_Exception';


line 1074 => $exc = new $name($e->getMessage(), (int) $e->getCode());

if ( ! is_array($e->errorInfo)) {

$e->errorInfo = array(null, null, null, null);

}
Re: How do I debug this? [message #102315 is a reply to message #102218 ] Sun, 11 July 2010 12:18 Go to previous messageGo to next message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
I wouldn't recommend altering core files in order to get around version restrictions. Your version of Doctrine may require a more recent version of PHP (Doctrine 1.2 requires 5.2.3, for example). It would be a good idea to see which version you are running.


Remember Palestine
Re: How do I debug this? [message #102382 is a reply to message #102315 ] Mon, 12 July 2010 21:48 Go to previous messageGo to next message
balunadig  is currently offline balunadig
Messages: 5
Registered: August 2009
Junior Member
I wouldn't normally touch the core files, but was just curious to make some head-way with the app...

Many web pages from this app come up quite nicely, quickly and correctly... But, certain pages keeps spinning the wheel:(

Are there any php/symfony/doctrine/postgres parameters that might be impacting large queries? How about caching? How about memcache?

I played around with the some big numbers of shared_buffers on postgres. Not much help Sad AccessShareLock and ExclusiveLock on postgres seems to hang around for ever Sad

BTW, doctrine is 0.11


Re: How do I debug this? [message #102425 is a reply to message #102218 ] Tue, 13 July 2010 15:09 Go to previous message
halfer  is currently offline halfer
Messages: 9535
Registered: January 2006
Location: West Midlands, UK
Faithful Member
I don't know enough about Doctrine to comment. But your statement looked like it might have a very long IN () clause - your problem might be that your db statement needs to be made more efficient?


Remember Palestine
Previous Topic:is it ok to increase max_forwards ?
Next Topic:can't get raw output in symfony 1.0.21
Goto Forum:
  

powered by FUDforum - copyright ©2001-2004 FUD Forum Bulletin Board Software