Hi,
our hosting provider recently moved our account to a new server which is running litespeed httpd rather than apache.
Since this move, we've had a few issues, one of which is still outstanding:
1) Perl moved (not a surprise). Fixed and OK.
2) cgi-bin and perl scripts permissions broken. Fixed and OK.
3) 500 Internal Server error when submitting orders. We and our provider are at a loss to find what is causing this.
Things I've looked at:
Directory permissions - seem OK - acatalog is 777, cgi-bin is 755.
Files created in acatalog - session files are being created, and Order.num/Backup.num are being updated when an order is submitted.
My guess is something is going wrong either when creating the temp file, or creating the encrypted order file.
Does anybody have any suggestions or any information we can feed back to our provider which may help them.
The ONLY thing being logged is a basic 500 error in the access log, nothing in the error log, and nothing in any internal acatalog error files.
Thanks in advance!
-PJC
our hosting provider recently moved our account to a new server which is running litespeed httpd rather than apache.
Since this move, we've had a few issues, one of which is still outstanding:
1) Perl moved (not a surprise). Fixed and OK.
2) cgi-bin and perl scripts permissions broken. Fixed and OK.
3) 500 Internal Server error when submitting orders. We and our provider are at a loss to find what is causing this.
Things I've looked at:
Directory permissions - seem OK - acatalog is 777, cgi-bin is 755.
Files created in acatalog - session files are being created, and Order.num/Backup.num are being updated when an order is submitted.
My guess is something is going wrong either when creating the temp file, or creating the encrypted order file.
Does anybody have any suggestions or any information we can feed back to our provider which may help them.
The ONLY thing being logged is a basic 500 error in the access log, nothing in the error log, and nothing in any internal acatalog error files.
Thanks in advance!
-PJC
Comment