Zen Cart Logo
Forums / General Questions / "500" on Cleanup Debug Log Files, PHP 5.4

"500" on Cleanup Debug Log Files, PHP 5.4

Views: 2,602

Results 1 to 6 of 6
28 Feb 2013, 2:23 AM
#1
rayw1679 avatar

rayw1679

Zen Follower

Join Date:
Mar 2005
Location:
Waxahachie, Texas
Posts:
172
Plugin Contributions:
0

"500" on Cleanup Debug Log Files, PHP 5.4

I noticed several files in my cache folder as I haven't taken my main store down yet to empty the db_cache folder. I tried to perform a "Cleanup Debug Log Files" and received a 500 server error. I tried my test store and it works fine. WinMerge says the store_manager.php files are identical. I don't know if a time-out could cause it, but my ISP is running like molasses tonight.

28 Feb 2013, 2:51 PM
#2
rayw1679 avatar

rayw1679

Zen Follower

Join Date:
Mar 2005
Location:
Waxahachie, Texas
Posts:
172
Plugin Contributions:
0

Re: "500" on Cleanup Debug Log Files, PHP 5.4

This worked about 3 months ago. I don't know if it's germane, but the other 2 stores that worked probably didn't have anything in the cache file. Are there indices to the database from these files, or can I just use Filezilla to delete what's in the cache file?

28 Feb 2013, 2:51 PM
#3
rayw1679 avatar

rayw1679

Zen Follower

Join Date:
Mar 2005
Location:
Waxahachie, Texas
Posts:
172
Plugin Contributions:
0

Re: "500" on Cleanup Debug Log Files, PHP 5.4

This worked about 3 weeks ago. I don't know if it's germane, but the other 2 stores that worked probably didn't have anything in the cache file. Are there indices to the database from these files, or can I just use Filezilla to delete what's in the cache file?

28 Feb 2013, 3:09 PM
#4
terragirl avatar

terragirl

Zen Follower

Join Date:
Jun 2010
Location:
Austria
Posts:
123
Plugin Contributions:
0

Re: "500" on Cleanup Debug Log Files, PHP 5.4

500 is a server error, so this does need to be looked at by your host. Your hosting provider has access to logs which may contain the reason for the error - best advice is to put in a quick support ticket to your host and ask them to check their logs for the source of the 500 error.

And yes, you can manually clear the /cache/ by deleting the content. The only required files are /cache/.htaccess and /cache/index.php

4 Mar 2013, 8:12 PM
#5
rayw1679 avatar

rayw1679

Zen Follower

Join Date:
Mar 2005
Location:
Waxahachie, Texas
Posts:
172
Plugin Contributions:
0

Re: "500" on Cleanup Debug Log Files, PHP 5.4

Thank you, terraGirl, you are most kind to respond. I did as you suggested, but 1and1 said that wasn't their problem, so I'm deleting them with FileZilla.

Could it be a contamined php module? Does anyone know which module performs this task? If so, would it make sense to replace the module with one from a clean install and see if that solves the problem?

5 Mar 2013, 6:06 AM
#6
rodg avatar

rodg

Deceased

Join Date:
Jan 2007
Location:
Australia
Posts:
6,263
Plugin Contributions:
4

Re: "500" on Cleanup Debug Log Files, PHP 5.4

rayw1679:

1and1 said that wasn't their problem,

I wouldn't expect them to say anything else.

rayw1679:

so I'm deleting them with FileZilla.

That'll be fine, BUT, how many files were there? Did you take a look at any of them? With a well oiled zencart store you'll rarely get any of these error/debug files, so if you ARE getting lots of them it is a good indication that your store has another problem that needs to be looked into, and the problem emptying the cache folder is the least of your problems.

rayw1679:

Could it be a contamined php module?.

It is certainly possible, but it certainly isn't the 1st thing that I'd be considering.

rayw1679:

Does anyone know which module performs this task? If so, would it make sense to replace the module with one from a clean install and see if that solves the problem?

A more important question is, does the problem still persist now that you've deleted the files using fileZilla? If the 500 error has gone away I'd be inclined to forget the problem ever existed and go back to figure out why the files are being created in the 1st place. IOW, the 500 error may just be a symptom rather than the problem itself.

Cheers
Rod