Search Module Problems

[apollo9]

For more than 12 months there has been a problem with search on my site. I thought it might be the installation, so I installed a fresh copy on the same server; the problem persists. Doesn't appear to be version specific.

Front end: After pressing submit, page times-out.
Back end: Module settings cannot be changed; pressing submit results in a time-out or page unavailable message.

I've had problems with mod_security (back end menu not expanding). The hosting company have whitelisted a few rules. Could this be related?

Chris

[paulbaker]

Don't think mod_security affects Search. Do you have many GB of content? (Pages, news items, etc). Anything relevant in the admin log? Post your system information.

[chandra]

Which CMS version you are using? Have you tried to use the reindex option inside Search modules admin?

[apollo9]

The installation I'm using to test this out has only the demo pages. Test version is 1.11.7. Main site version is 1.11.9. It began several version ago.

I've tried re-indexing and the browser reports the same: server at rest, or time out.

Admin log:
[Mon Nov 11 18:51:27 2013] [error] [client 84.92.176.214] File does not exist: /home/lbc1085/public_html/500.shtml, referer: http://cornworthy.com/c/admin/moduleinterface.php?_sx_=c031589b&module=Search
[Mon Nov 11 18:48:09 2013] [error] [client 84.92.176.214] File does not exist: /home/lbc1085/public_html/500.shtml, referer: http://cornworthy.com/c/admin/moduleinterface.php?_sx_=c031589b&module=Search
[Mon Nov 11 18:47:41 2013] [error] [client 84.92.176.214] File does not exist: /home/lbc1085/public_html/500.shtml, referer: http://cornworthy.com/c/admin/moduleinterface.php?_sx_=c031589b&module=Search

System Info:
----------------------------------------------

Cms Version: 1.11.7

Installed Modules:

CMSMailer: 5.2.1
CMSPrinting: 1.0.4
FileManager: 1.4.3
MenuManager: 1.8.5
MicroTiny: 1.2.5
ModuleManager: 1.5.5
News: 2.12.12
Search: 1.7.8
ThemeManager: 1.1.8


Config Information:

php_memory_limit:
process_whole_template:
max_upload_size: 50000000
url_rewriting: none
page_extension:
query_var: page
image_manipulation_prog: GD
auto_alias_content: true
locale:
default_encoding: utf-8
admin_encoding: utf-8
set_names: true


Php Information:

phpversion: 5.2.17
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
memory_limit: 64M
max_execution_time: 30000
output_buffering: On
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 50M
upload_max_filesize: 50M
session_save_path: /tmp (1777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)


Server Information:

Server Api: cgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.0.96
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable

----------------------------------------------

[chandra]

It seams there's something wrong with your server if you get a server status 500.

[paulbaker]

Anything in your PHP error log? This could be anywhere - depends on your host.

[apollo9]

I can't find the PHP error log. Host uses cPanel. Would it be in phpMyAdmin?

[chandra]

It seams there's something wrong with your server if you get a server status 500.

Some information

Fixing 500 errors - general

This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of the Web server site to locate and analyse the logs which should give further information about the error.

Try to ask you provider. He will know it where he has to look ...

[apollo9]

I've raised this with the hosting provider.
They noted that the 500 error in the log was due to a missing 500 Internal Server Error page.

They're currently investigating.

[chandra]

Have you checked your .htaccess file?

A misconfigured .htaccess can do also an error 500.

Try to deactivate your .htaccess.

[apollo9]

I have tested with .htaccess disabled in public_html and the CMSMS main folder. I presume the .htaccess files in sub folders of a new install would be configured correctly.

I've attached the error which appears in Firefox.

There are no PHP errors appearing.