Quick search: 500 internal server error
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
Hi (it's me again lol).
Everything is working great now (love the stats btw) but when i search using the search box that is always available at the top right of the screen, I receive an internal server error (after more than 60 seconds of waiting). When I search using the general search it works fine. Any idea what might be going wrong? Oh my error log gives me: Premature end of script headers: search.php, referer: http://www.ghvandoorn.nl/genealogy/index.php?ctype=gedcom
I just accessed your site, and did the top search for "korstiaanszen".
The search took a long time, but yielded the expected results.
The same search, looking for "beusichem" yielded the server error.
I suspect your problem is that the PHP time limit is set too low, and that the script is being killed before it has had a chance to output anything meaningful.
The problem might also be a mis-configuration of the database system. I know nothing about this subject, so I won't be able to help.
Hmm ok. Weird. It worked much faster before the update. Maybe I need to re-import again
But why would it work using the "general search" and not using the "quick search box"?
is your DB all one configuration (LAtin, UTF-8, etc) ? Unmatched configuration can cause significant slowdowns of certain aspects of PGV. Overall, your site is quite snappy. Lists pop up quickly. Also, is the DB tables optimized?
Greg is the DB expert and can perhaps assist. I can tell you the general search searches more things and can be much slower, but is much faster on my GEDCOM in v4.2 than previous versions.
-Stephen
Stephen: I checked and as far as I could see the tables are all Latin_swedish_ci (mysql default i think). Optimized? Should I run an optimize?
The thing is "General search" search works fine but using the search using the little search box in the header is sloooow. I was assuming this box does exactly the same as the general search menu item. Or is this a false assumption?
Oh I did the optimize and it seems to work much better now :). Thanks for the tip! Still a bit weird considering that it worked on the general search.
Its the 'HEADER SEARCH' that I refer to as GENERAL. The Search is much more specific. The header search looks in every nook and cranny and is much more memory intensive.
Stephen
Thanks for the Optimize suggestion.
I have just upgraded from 4.0.1 to 4.2.2 . I threw away the GEDCOM file I created prior to the upgrade because it seemed to double up on everything when importing. I went back to an older one (by date not necessarily by data) and things worked ok.
The site seemed to work ok apart from the Quick Search at the top right. This gave server error 500. Several tables had an overhead of a quite a few KBs which I thought of as next to nothing.
Having now done the Optimize on all tables with an overhead the search is very quick and includes all sorts of things I have not seen before.
ghvandoorn and pmarfell
You should both check out DB collation carefully, as this is the most common cause of slow searching. Optimisation may only be a short term fix.
It is important that collation is consistent, not just across every table in the DB, but also every field in each table.
Look at this patch for more information and the tool to fix it:
https://sourceforge.net/tracker/?func=detail&aid=2318005&group_id=55456&atid=477081