Resolved Cron Job does not work

Hello,

Cronjobs do work but what you are attempting is not a real cronjob. Cronjobs are run by calling the cron.php file as explained in the Setting up a cron job tutorial.

The front-end export does not work because it requires JavaScript to function, like it does in the back-end. Easycron and such services do not provide this. The JavaScript is required to make long running imports possible or in general any import that takes more than 20-25 seconds.

The best is to setup a real cronjob using the tutorial I linked above.

Hello,
I also tried to create a command line cron job using Putty but it doesn't work

* * * * * /usr/local/bin/php7.1 -f /homepages/xxxx/xxxxx/htdocs/xxxx/administrator/components/com_csvi/helper/cron.php --key="test" --template_id="12"

thanks

Hello,

I hope you don't expect me now to guess what you see on your screen So please provide us more information other than "it doesn't work". What is the output that you get? A backup of your template helps as well. You can create a backup from the template list by selecting the template and click on the Backup button.

Hello,

I can create a cron job but my hosting doesn't give me access to the shell to see what happens.

The cronjob is executed because, in my web space, folders are created with the csv file that must be processed.

/ tmp / com_csvi / 2463733474
/ tmp / com_csvi / 3198133831
/ tmp / com_csvi / 2164312350
....

the file cron.php because it creates a folder for each execution and does not delete the file?

I created a cron2.php file when it runs increases a counter in a table and works perfectly.

Hello,

the file cron.php because it creates a folder for each execution and does not delete the file?

These are temporary folder which RO CSVI uses for import and deletes it once import is done. For some reason these folders are not deleted in your case. Can you check the permission of tmp folder?

Hello,

I can create a cron job but my hosting doesn't give me access to the shell to see what happens.

Cronjobs usually can send an email as to where to send the output of a job. If you don't have this option, you can also have it written to a text file by doing this

your cronjob > /path/to/file.txt

Replace your cronjob with the actual command you have now and replace /path/to/file.txt with the full path of the file you want to write. The magic is in the > symbol. This makes sure all output is written to that file. It is important to see what the output of the job is.

the file cron.php because it creates a folder for each execution and does not delete the file?

This basically means that it doesn't finish the import.

I created a cron2.php file when it runs increases a counter in a table and works perfectly.

I am afraid this is not a valid comparison because the CSVI script is a lot more complicated than that.

We just need to found out first what output you get from the cronjob and we can take it from there.

Hi solved,

The problem was in the -f command that blocked the execution.

Thanks for the help.