Job Running for more than 24hours
Permalink
Hey there :)
I ran jobs (sitemap, index, etc.) on my site yesterday morning, and they're now running for more than 24hours...
I ran them because I wanted to do a backup before updating Concrete5 but seems that these jobs aren't ready to stop.
Anyone having an idea of what happens?
Thanks in advance :)
Dom.
I ran jobs (sitemap, index, etc.) on my site yesterday morning, and they're now running for more than 24hours...
I ran them because I wanted to do a backup before updating Concrete5 but seems that these jobs aren't ready to stop.
Anyone having an idea of what happens?
Thanks in advance :)
Dom.
Well, I'm not a programmer - should have make sure it would be easy to use and manage before using Concrete5 I think.
Actually the only job that's still running is the search engine indexing.
Now, in any way the system doesn't allow any backup right now and I'd like to update with the last C5 version. Is there a relation between this job and the update?
Actually the only job that's still running is the search engine indexing.
Now, in any way the system doesn't allow any backup right now and I'd like to update with the last C5 version. Is there a relation between this job and the update?
Did you try the url to run the jobs in the background and see if you got any errors ? I am running my site in dev on my localhost and did get errors on the url provided below the list of jobs.
If you run the jobs URL manually and add '&force=1' to the end of it, it should run all tasks again.
If you have access to the database you can also reset the status of that job so you can tick it in the dashboard to run again.
If you have access to the database you can also reset the status of that job so you can tick it in the dashboard to run again.
I know this is an old post, but for people like me who are searching here is what I did.
Go into php.ini file.
I upped the time limit and the memory. The larger the website the larger the memory, or at least if you have a lot of pages added since you last ran the job.
max_execution_time = 300
memory_limit = 256M
I ran the URL with the "&force=1" as suggested by shadow computers.
Go into php.ini file.
I upped the time limit and the memory. The larger the website the larger the memory, or at least if you have a lot of pages added since you last ran the job.
max_execution_time = 300
memory_limit = 256M
I ran the URL with the "&force=1" as suggested by shadow computers.
If you search around you'll find where you need to update your db to not show the jobs as running.