500 Internal Server Error [#2866431]

Hi,

I am using feeds module for importing contents.
When I am trying to import more than 5 rows in a CSV I am getting this error:

" An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?id=238246&op=do StatusText: error ResponseText: 500 Internal Server Error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. "

Why I am getting this error and anyone help on this?.
Thanks in advance.

Comments

Comment #1

3 April 2017 at 17:06

krishnaveni.t created an issue. See original summary.

Comment #2

MegaChriz CreditAttribution: MegaChriz as a volunteer commented 3 April 2017 at 19:36

Title:	Ajax	» 500 Internal Server Error
Version:	7.x-1.x-dev	» 7.x-2.x-dev
Category:	Bug report	» Support request
Status:	Active	» Fixed

This has been reported before: #1219296: Partial import then ajax message - 500 error.

An internal server error is quite a generic error which can be caused by a lot of things:

A misconfiguration on the server (for example in httpd.conf or in a .htaccess file).
A bug in a module (any module).
Unreadable characters in your CSV file.

The first thing I suggest you to do is check if there is anything useful in the server error logs. You could check the recent log messages on your Drupal site as well (admin/reports/dblog), but I expect that Drupal wasn't able to log this error properly, at least not with enough context.
In my case - I'm using Acquia Dev Desktop locally - the server error logs can be found in DevDesktop/apache/logs/error_log. If not working locally, ask your hosting provider where you can find these logs.

If that doesn't give you any hint, then things will be getting a little harder: then the only way to find the culprit is by trial and error. Try one or more of the following things in this case:

Test if you can reproduce the issue on a clean install of Drupal and Feeds. If there is no error, the issue is likely caused by an other module. If you encounter the same issue, it could be a misconfiguration on the server, a malformed source file or a bug in Feeds.
Create a copy of your site. Then try to disable modules one by one until the error disappears. If the error does disappear at some point, then there could be a bug in the just disabled module or an incompatibility between that module and Feeds.

Comment #3

krishnaveni.t CreditAttribution: krishnaveni.t commented 11 April 2017 at 11:13

Hi MegaChriz,

Thanks a lot for your reply.

I have checked the steps mentioned by you. It's was working fine in fresh install and also disable modules in another copy of the project.
The issue onlyt appears while we are using the latest database.
I think the larger database is the cause of this issue (Even I have tested with the older database where I couldn't get the error).
I have tried to do the performance steps suggested by Acquia but still the issue exists.

Thanks.