Leads Module Timing Out

[avadtechnologies]

We run Sugar 5.0 on Apache 2.0.59 with PHP 5.2.6

We upgraded the php version recently and everything went fine. Today the Leads module started timing out. I tried all of the repair function under admin already. I then changed max file upload and post and memory settings (increasing them) . I also enabled zend.ze1_compatibility_mode = On.

All of the other modules timed out with the exception of the administration. I could log in but then it would say timed out and I had to manually enter module=administration in the address bar for it to work. I changed those settings back down and disabled the zend compatability. But the Leads modules still times out.

The server is windows 2003, 1 gig ram, 3 ghz processor.

We do see a memory spike when someone clicks on the leads module, it starts spiking then lowers, then goes back up again. It is a far larger spike than when they click say the accounts module. We currently only have 176 leads but we have more than double that many accounts.

I have tried everything I can think of aside from a complete re-install or upgrade to a new version of Apache and MySQL (We are using the default version that came with 5.0).

If anyone needs more information let me know what you need. I did a diagnostic dump but did not want to post everything puclicly if it was not needed.

[roblaus]

Does sugarcrm.log (in the sugar root) tell anything usable? Are you logging slow queries (system settings towards the end)? Just fishing here...
Send me your diagnostics info (at) iscon dot at - no promises but I can have a look sometime during the (my) day.

rgds
rl

[avadtechnologies]

The log file is empty, I did turn on the logging slow queries yesterday and played around and it did not add anything to the log file.

I also forgot to mention that we can use a shortcut on the left to "create" a lead. Can also use the "last viewed items" to look at a lead. But we can not use our search option or view the list of leads.

[avadtechnologies]

Further Update:

It appears it is a problem with only certain records. I created a lead with last name of asdfg and did a search and it came up. Also some previous leads come up as well when you search for them. It only times out when you do a search for say the name Mike, or other common names that I am assuming have many results with at least 1 being a problem record.

Any thoughts?

[roblaus]

Not really. Might be that an index crashed but that should have been rectified by the repair routine. Check the records in question directly in the database, maybe you see something strange. If you are brave you could also export the records (directly in e.g. phpmyadmin), truncate the table and re-import again (backup!!!). You could also try the repair (or is it clean-up?) routine directly on the table.
Yes it's trial and error but the good thing is: we at least admit it. Doctors never (with the exception of Dr House )

[avadtechnologies]

I got a delivery failure for that address, I did double check it against the domain in your signature. info@domain.at is what I used.

[roblaus]

Might well be, I am switching domains today. But it worked until some minutes ago. I'll check.
[EDIT] - nope, works... info(at)iscon(.)at

[avadtechnologies]

I did a test earlier.

Found a record that was timing out in Sugar.
Found the corresponding record in the database
Created a new record in Sugar that did work
Found that record in the database, copied its ID, and then deleted the record in the database
Went to the original record that was timing out and changed its ID to the ID of the record that I had just deleted.

That record now shows up in Sugar however all history like notes and calls are gone. I am a network guy so I have a limited knowledge of php, sql, programming, and databases in general that it would make a mouse look smart.

My best guess / interpretation of the problem and information I have gleaned from troubleshooting is that the actual records are ok, but that upgrading to php 5.2 cause some problem due to my before mentioned lack of knowledge. The problem I am thinking is in attachments or the relationship to history.

One thing I also noticed is the following error which only appeared a few times and I can not get it to be stable sometimes the line number changes.

Parse Error: syntax error, unexpected $end, expecting ')' in sugar\htdocs\sugarcrm\cache\modules\Leads\Leadvard efs.php on line 308

I also noticed another error referring to opportunities module.

If I can figure out how to re-corralate the leads history / notes then I can find out if thats causing the problem. Unfortunately I never seem to run into "simple" problems.

[avadtechnologies]

Found the following under the main table -> operations

The additional features for working with linked tables have been deactivated. To find out why click here
PMA Database ... not OK[ Documentation ]
General relation features Disabled

Following the breadcrumbs I found this help but have absolutely no idea what it means, if it is relevant, or how to implement it... The relationships seem to work just fine with accounts or cases and what not.

$cfg['Servers'][$i]['pmadb'] string
The name of the database containing the linked-tables infrastructure.

See the Linked-tables infrastructure section in this document to see the benefits of this infrastructure, and for a quick way of creating this database and the needed tables.

If you are the only user of this phpMyAdmin installation, you can use your current database to store those special tables; in this case, just put your current database name in $cfg['Servers'][$i]['pmadb']. For a multi-user installation, set this parameter to the name of your central database containing the linked-tables infrastructure.

[roblaus]

I am not a technical person either so I can't interpret your last message. To the ones above: The /cache/modules directory you can safely delete. It will be rebuilt again. I did this a 100 times already. The story with your lead record looks interesting. The ID is the only connection to the rest of the world so to speak so if you use the same ID the relations should be still there.

But before you drive yourself crazy: Do a fresh install (same Sugar version). Then copy the old db to the new place (delete the newly created one and copy the old one to the new name). The Sugar user (in config.php in the db section) should be the same for both dbs to avoid permission problems. On this way you can exclude problems with your installation. If then the same problems occur then most probably your db is the culprit.

Maybe one of the tech gurus here has another idea...