looks like a resource problem when having too many results. Have you tried to limit the results set in your findAll (case of Virginia) ? Try by setting the "limit" parameter in the query. I had that problem (not exactly), that was not a timeout issue but rather a memory_limit (max 8 Gb) authorized in php.ini.
Hope it's a hint On Oct 3, 7:31 am, digitalcowboy <[EMAIL PROTECTED]> wrote: > I apologize if the solution to my issue is to be found elsewhere. > I've tried to look but don't really know what I'm looking for and I > don't have a lot of time. > > I have two problems and I think - but I'm not sure - they are > related. I have a client's production site running on a Cake-based > solution I created. Recently we outgrew our dedicated server and I > added a second beefier server. The Cake-based site is all now on the > new server. I replicated everything as exactly as I could. > > Now I have two issues - First (and most critical) is that queries with > large results are just not running at all. I don't mean large or > complicated queries. In most cases they are simple queries with a > large result set. They are not timing out. They are just not running > at all. After just a few seconds Cake returns an empty page. Empty > as in: "View Source" is an empty file. Other queries - and the > majority of the site - are running fine. In addition, the old server > is now pointing to the database on the new server and doesn't have > this problem. Queries that return a blank page on the new server, > work (albeit slowly because of the remote db) on the old server. > > Second, in trying to troubleshoot this, I discovered that I'm getting > no debug results at all, anywhere on the new server no matter what I > set the debug level to in app/config/core.php. > > I've checked every timeout I can think of - PHP input, PHP script, > Apache, etc. I cannot find anything different between the two > servers. > > Please help. This site is profitable and the core of my client's > business. They are losing customers and getting justifiably > impatient. I need a quick resolution. > > Details: CakePHP 1.1.something on PHP 5, MySQL 5 (5.024 on the old > server and 5.027 on new), CentOS 4. You can see one example of the > problem by going tohttp://govdirections.com/bids/sitemap/state/and > then clicking on the "List" link next to Virginia. That's the new > server and will return a totally empty page after just a few seconds - > as if the query doesn't even attempt to run. On the old server, > pulling from the same database, it takes a good long time, but will > eventually return ~22,000 rows. (That number of rows is not normal - > it's a separate problem. This is just one example but the problem is > also affecting paged results on the new server when trying to switch > to anything greater than 500 results at once.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
