a5408851

@Kyrdos:

100% of those core.## files I've looked at recently are dumps because the script was taking too long to execute. They are fine to delete and I recommend you delete them because they do count towards your 500mb limit and they fill that up really quickly. If you want to provide your username I can take a look at some of the files for you to tell you for sure though what is causing it.

 

To make your scripts work, and also prevent core dump files I recommend finding ways to break your scripts down into smaller pieces. Like script1 only takes a couple seconds to process and then passes to script2 which runs for another couple seconds, and passes along. What you have now is one script that might work quite well at low server load, but if the load is higher or your remote sites take longer to respond the system has to kill it because it has been executing for too long.

Do you mean that i have to break the script into more smaller scripts and combine them in a main script (e.g. like

scriptP.php:

<?php
require("script1.php");
require("script2.php");
//Etc.
?>

script1.php

do first part

script2.php

do second part

etc.

) or to simply make script1.php do the first part, save the results (in session with serialise(), load with deserialise()), redirect to script2.php and repeat as many times as needed?

EDIT: Adjusted the script to refresh the page for each of the scripts (e.g. in the above example, run script one by default, next redirecting to the next script etc.). All the series get added now one at a time (with exception of the manual series (which are hardcoded by episode numbers)). It works again.

Could you please provide a URL?

 

We are currently working on removing those core files right now - feel free to delete them as they seem to be consuming lots of space.

Added a temp test admin login to the protection system for this supplied page: here.

BTW when it reaches the end of the script, it will give a red DONE.

I have a series update script (takes some data from various predefined sites listed in mysql database with url fopen, takes items using regex and puts it in a different table in the database for other script's further usage) which when executed suddenly stops (no error message or anything, just stops executing and finishes output to the browser).

It worked fine until about monday this week.

BTW also some "core.INSERTNUMBERHERE" file appears in my site's (root?) directory with about 50MB in size.

Anybody knows how to solve this (or is the PHP parser bugged?)?