Script import.php from the command line ok, from cron executes only part of importation then stops...
- I have a dedicated server but not getting results cront by email.
- I do an identical command (e.g. import.php @MODIFIED) from the command line and cron script:
- /home/cescodir/wwwroot/cescodir.com/migliorprezzo/scripts/import.php @MODIFIED or
- /home/cescodir/wwwroot/cescodir.com/migliorprezzo/scripts/cescodirfetch.sh (On your model script sh automation http://www.pricetapestry.com/node/198 - fetch.sh)
Using cron does not end the importation
Hello framor,
Can you confirm that when using cron;
- It does all the downloading that you are expecting
- It starts to import but does not finish
Can you tell me how you are seeing that it does not finish?
Thanks,
David.
When I go on the administration panel, know that only a few catalogs are updated.
Hi,
When you go the admin panel after running CRON, are some of the "Import" links green, which means that they have been updated but not imported?
Also, could you email me your import script so that I can take a look? Please reply to your forum registration or reg code email...
Cheers,
David.
Exact after you run cron there are some links in green administration panel. How can send attached script and image admin panel?
Hi,
Please email them to me. Reply to your forum registaration email will get me, or use the email address here...
Cheers,
David.
David,
Just had setup the automated product feed download. Every file seems to be downloaded. Even managed to download one that's 167 mb big.
I had setup the fetch.sh which i activate thru cron.
Most of the feeds don't get imported. The import link stays green.
Importing a feed manually that's 68MB big gives the following:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 67110912 bytes) in /home/storepri/public_html/xxxxxxxx/includes/MagicParser.php on line 2
Hi Mikey,
That Magic Parser error is indicative of feed that isn't formatted correctly. This is because the parser is trying to construct a single record in memory; but the data is not being terminated and so eventually the maximum amount of memory allowed is reached.
The first thing to check is that the file is not compressed (zipped). This is a possibility, because if you're running import.php via cron then you must have registered and [trial?] imported the feeds previously...
Cheers,
David.
David,
The file isn't compressed. So perhaps the maximum amount of memory was reached trying to import.
I'll try and extend the memory.
Perhaps that will solve the issue concerning the imports ?
Hi Mikey,
Can you try a register / trial import of one of the feeds that is causing the problem?
The memory exhausted error should only ever occur with a badly formatting feed (for example where quoted text fields are used but the terminating quote is missing).
If extending the memory doesn't help; feel free to drop me an email with a link to one of the feeds (in your /feeds/ directory if I can access it, or copied into another folder otherwise) and i'll download it to my test server and take a look...
Cheers,
David.
Hello framor,
How are you noticing that it is stopping? Are you getting a results email from your cron process; and if so; what does it contain?
Are you running an identical command (e.g. import.php @MODIFIED) from the command line and in your cron script?
Cheers,
David.