error 500 but not error message

[Giu]

Hi.

I have deployed Abyss on a w2003 server. all works fine and extremely fast, loving Abyss, but I have one important problem don't know how to solve. I have a PHP page, that process a csv file, to import data into a MySQL database. using WAMP works like a charm, but with Abyss, I get an error 500 after some time the process started to run.

If I check the logs, I don't see errors. AFAIU, a 500 error comes from a syntax or error in code, but the same code runs OK under apache. Some idea what could be the problem? in log, I only see something like

Reading 8 bytes failed = The process cannot access the file because it is being used by another process.

[Toasty]

This is an issue I've had with Abyss so many times, long running processes (DB queries etc).

For something like this, you're better off just running it from the CLI or setting up a scheduled task to process the data, and use the webpage to output the cached version.

Never had the issue with nginx or httpd though.
_________________
Audit the secure configuration of your server headers!

[immicavn]

I have the same issue, but dont know how to fix it.

[admin]

[timkaelin]

I have the same problem, and have sent an email to support a couple of days ago, no response yet. I seen where others have had the same problem , but I have not seen a resolution

My data set is about 22000 records, but when I reduce it to 10000, I don't get the error and everything works fine.

My fastcgi.log says

09/Jun/2018:19:27:34 -0400 SUID: 3 PUID: 3 RUID: 0 URI: timeout-header2!
09/Jun/2018:19:28:04 -0400 SUID: 3 PUID: 3 RUID: 1 URI: /ace/michaelsstuff/index.php Reading 8 bytes failed = The process cannot access the file because it is being used by another process.

[admin]

timkaelin,

What you describe is a typical behavior of a script which was aborted due to PHP/Abyss Web Server timeout configuration.

If a script takes more than 30 seconds to execute, special configuration should apply to let both PHP (in FastCGI/CGI mode) and Abyss Web Server know about that and wait for it longer.

At the PHP level, you should probably increase the timeout parameter is php.ini: the first is by default set to 30 (seconds):

[timkaelin]

I had already changed the PHP ini file. But I did find the fastcgi time out in the server configuration, and changing that has fixed the problem. Thanks!

[admin]

[laurent15]

[admin]