Hello,
I am running Zen Cart v. 1.3.8, and I have 3 things that I would like to be done:
1) Upgrade to 1.3.9b
2) About 5% of my customers are finding it impossible to complete the order process. This is especially true when they try to order in different currencies. I was able to recreate the error, and this it what is returned (using Chrome):
This webpage has a redirect loop.
The webpage at (xxx) has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
Here are some suggestions:
Reload this web page later.
Learn more about this problem.
More information on this error
Below is the original error message
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.
3) My site is very slow at times, and I'm not quite sure why. This is what my hosting company said I need to do to fix.
"Unfortunately, your user's [login to view URL] processes are being killed
by our procwatch daemon, and this is the source of the delays (and errors
in the error log)you are receiving.
Procwatch is a daemon that runs constantly on shared servers to monitor
the usage of RAM/CPU and execution time so that no single user can use an
inappropriately high percentage of the shared resources and impact the
overall health of the server or the server's ability to serve all users'
pages.
When it finds a process that is using too great an amount of resources,
it kills that process. If it does this to a running script, the resultant
error the server shows is "premature end of script headers" - the script
can't complete.
This is happening regularly with your site. Below please see excerpts
from our procwatch log:
2010-05-04 23:43:01 procwatch2 INFO: Process(pid=3878, name='[login to view URL]',
tty=None, cpu=0.3, rss=20116.0, vsize=142364.0):
kill for total RAM
2010-05-04 23:43:01 procwatch2 INFO: Process(pid=3890, name='[login to view URL]',
tty=None, cpu=0.3, rss=20100.0, vsize=142308.0):
kill for total RAM
2010-05-04 23:43:01 procwatch2 INFO: Process(pid=3885, name='[login to view URL]',
tty=None, cpu=0.4, rss=20096.0, vsize=142352.0):
kill for total RAM
2010-05-04 23:43:01 procwatch2 INFO: Process(pid=3881, name='[login to view URL]',
tty=None, cpu=0.2, rss=20096.0, vsize=142344.0):
kill for total RAM
2010-05-04 23:43:11 procwatch2 INFO: Process(pid=3879, name='[login to view URL]',
tty=None, cpu=0.2, rss=20092.0, vsize=142316.0):
kill for total RAM
2010-05-04 23:43:11 procwatch2 INFO: Process(pid=3946, name='[login to view URL]',
, tty=None, cpu=0.5, rss=19784.0, vsize=142692.0):
kill for total RAM
In short, what this is saying is that the combined PHP scripts run by the
user that runs that site is simply using too much memory for
a shared server. Note this could be a single site, or more than one site
- with PHP it is hard to tell as each PHP process is only identified as
php5.cgi. This can be telling us that a single request added to other
running requests, or a single large request alone, is exceeding
acceptable memory limits.
I suggest that you:
Decrease the overall memory required for your scripts to process,
create, and serve your site. With many common scripts/applications, there
are several things you can try to help with this, and you may find some
help with that within the application's user community.
It is also possible that a spike in traffic, or a heavy run by the
Googlebot, or another robot, or even abusive hits by a given IP address
(leaching), could cause this on a short term basis, so you might want to
inspect your access logs for such activity (you can often mitigate this
with [login to view URL] or by blocking abusive IP addresses with .htaccess).
I'd like to have someone troubleshoot with me, and have all of these issues fixed by the end of the week. Good communication and timeliness are essential. Please address my specific concerns in your reply, or you will be deleted. Looking to start today. Thanks!
Jason