Orders overview customers not working getting http 500 error

[slic535]

I recently am having problems with my orders overview. when I push the view all on the bottom it gives me a http 500 internal server error. what would this be?

[bsmither]

Usually, each 'page' in the pagination gets you a range of 20 orders from all the orders in the database. 'View All' tells CubeCart to not go through the paging process and to show all orders, but -- in some cases will still limit the number to show 100.

 

Take the number of pages available and multiply by 20. How many orders does that come to? Does it closely match the number at the lower-right corner: Total?

 

Please reply with the exact URL (minus the domain name part) the of the View All link.

[slic535]

well I used to push it and it would show me all the orders. I have saved all the orders since I have been using version 5. it won't show me 100 if I push view all it just says http 500 error. it shows 214 total on the lower right. 4280 would be the total.

admin.php?_g=orders&page=all

[Dirty Butter]

MY View all link part is /admin.php?_g=orders&page=all . Mine works and shows 1302 orders.

[bsmither]

The number of pages times 20 would equal 4280? Do you truly believe you have 4280 orders in the database?

 

But then, CubeCart says you only have 214 orders.

 

Which of these figures do you believe is the most correct?

 

There is a conversation on these forums that will have you make some edits that should get these two numbers to agree.

 

Trying to get 4280 orders to show on one page could very well trigger an "overload" block on the database server. You may want to ask your hosting provider if their logs show your site triggered such an event recently.

[slic535]

it was very close. I pushed page 214 and it only has two orders on it.  it goes back to aug. 12 , 2011. so the total would be 4262. theres 20 orders on each page and 214 pages with page 214 with only 2 orders on it.

[bsmither]

The conversation I mentioned is here:

http://forums.cubecart.com/topic/47637-resolved-orders-list-in-admin-bad-pagination/

 

Please let us know if your hosting provider can corroborate the hypothesis that asking for 4000 database records triggered some sort of "Oh, no, you didn't!"

[slic535]

I got with my hosting company and this is what they said on this---

 

 

I've taken a look at the issue and have confirmed there is nothing on the server that is causing this not to work. Unfortunately, this is not an issue that we at HostGator can assist you with as it is a development issue. Although we do have technical knowledge, development is outside the scope of our support. I apologize.

[bsmither]

"confirmed there is nothing on the server that is causing this not to work."

 

I'm disappointed that they didn't say, "We scanned our server error logs, and, even though the server is reporting an error, we can't find any mention of the error in the server error logs." Because they did not say this, I have to wonder if they scanned the server error logs, or if they have any server error logs to look at!

 

What we can try to do is to temporarily force CubeCart to only query for a maximum number of records. The edit shouldn't affect how the store-front works, only in admin where you are asking for all 4000+ database records. We can force a limit on 1000, then 2000, then 3000, etc, and see if the server still gives a 500 ISE response.

 

Did you make the edits discussed in the link above about the pagination issue?

[slic535]

no i haven't tried the edit for the above statement but i did give them the link to this page so they could see the conversation.

[KSD]

We have the same problem here.

It started when we had more than 4096 orders in our database.

From that moment on, a click on 'all orders' lead to a http 500 error.

After deleting some old orders, it worked fine again (4093 orders).

[bsmither]

Your sig says you have a virtual private server. In your opinion, do you think that means you can configure your installed web server, installed database server, installed PHP, and whatever else is installed, in any way you see fit?

 

If so, we can explore some config settings to bump up limits.

[KSD]

Yes, we can configure our VPS like we want.

We have root access.

[bsmither]

We can work on increasing the memory that PHP will use, if, when loading that many records into memory, is exhausting that resource.

 

Please determine the setting as set in the PHP.INI file. This can easily be seen in CubeCart admin, PHP Info. In the Core section, find memory_limit. The second column is the Local (CubeCart) Value, the third column is the Master (PHP.INI) Value. A stock CubeCart sets the memory_limit to 128M. In the file /ini.inc.php, line 56, change to 256M.

 

Test and let us know if you still get a 500-ISE when trying to load all orders.

 

I am confident that your database server can deliver 5000 records in a very short period of time. And that CubeCart can process that array quickly. And that Smarty, the template engine, can build the table with that many rows and assemble the final page within several seconds. And that the web server can shove that response onto the wire quickly. So, I am not concerned at this point that the sequence of actions is causing any player to give up and say y'all ran out of time.

 

There are a few instances where CubeCart bumps up PHP's max_execution_time: collecting and zipping up files and database table data for an archive, deploying files and restoring a database from an archive, and maybe one other obscure instance.

[KSD]

I cannot find /inc.ini.php.

Maybe this has to do with my FastCGI config?

[bsmither]

ini.inc.php, not inc.ini.php. It is in the same folder as index.php, admin.php, and the folders /admin/, /classes/, /controllers/, /includes/, and others.

[KSD]

Thanks, bsmither, we have 256 MB in place now and the problem seems to be solved (showing more than 4096 orders in orders overview).

 

There is also a slightly increase of speed ...

 

After a long while we are also able to make a backup of the database files, while a complete site backup still leads to a http 500 error.

[bsmither]

If your store is on a dedicated private server, that is, you can have all 16Gigs of RAM, all 2TB of hard drive space, and 100% of the CPU's attention, then we could explore some real performance experiments.

 

{Daydreaming}

Find and remove all instances where CubeCart sets its own limits in memory and script execution time. Edit the PHP.INI file to give all PHP scripts 2G's of memory and set max_execution_time to 300 seconds.

 

Then let's see how CubeCart behaves.

{/Daydreaming}

[KSD]

Unfortunately we share this server with 3 others.

But I could increase PHP mem limit to 2 G's and increase the values you mentioned in ini.inc.php.

If you are not kidding ....

In addition we have a VPN service running on this machine (incl. MPPC) and my client has an 100 MBit/sec internet connection speed.

What more you need??

[bsmither]

A fat pipe isn't going to matter to PHP.

 

I think the 500ISE is because you are hitting a max_execution_time limit. And if you are still hitting a memory limit somewhere which that then requires paging to file, or whatever, that's the bottlenecks.

 

If the administrator of the server can give your VPS 4GB of actual server RAM (not just 4GB of 'virtual' RAM), and then you give 2GB of that to PHP... well, won't hurt to try.

[KSD]

We have physically  4GB.

I set max_execution_time to 300 seconds and mem to 1024 MB.

Testing now ...

[KSD]

DB backup very fast now.

Site backup had again http 500.

During site backup, CC used 4% more physical memory than before starting this process.

About 120 MB more.

http 500 came in less than 1 Minute.

Mem usage of the server below 23% (in total) 

Maybe there is still a 128 MB limit somewhere in CC's config files?

[bsmither]

The only current statements are in the setup routines (bumps memory to 512M) and in admin maintenance files backup and database backup (bumps time limit to 600 seconds).

 

I wonder if there is an Apache time limit shorter than 10 minutes.

 

Find your PHP error log. If you don't have one, I can tell you how to start one.

[KSD]

Sorry for the late reply, I was on vacation.

 

I searched for but couldn't find our error log :-(

[bsmither]

Create a file named ini-custom.inc.php. It's contents are:

<?php
ini_set('error_log', 'error.log');
ini_set('log_errors', 'on');
?>

Put this file in the main CubeCart folder.

 

If/When PHP complains about something, and has a chance to log it, it will be in the error.log file in CubeCart's main folder.