summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBernhard Posselt <dev@bernhard-posselt.com>2015-04-29 23:20:26 +0200
committerBernhard Posselt <dev@bernhard-posselt.com>2015-04-29 23:20:26 +0200
commit5d00ee374568c792168c10070cb8652c489e88b7 (patch)
tree61fa6578a7be270c130fd011d0edb47323b5b9f4
parent9b6584fd1f5dc0256eb9ff2575599eb1850238e0 (diff)
update readme
-rw-r--r--README.md7
1 files changed, 1 insertions, 6 deletions
diff --git a/README.md b/README.md
index 7e807cfed..281b092ff 100644
--- a/README.md
+++ b/README.md
@@ -162,12 +162,7 @@ Check the **owncloud/data/owncloud.log** for hints why it failed. After the issu
"maintenance" => false,
-### All feeds are not updated anymore
-[This is a bug in the core backgroundjob system](https://github.com/owncloud/core/issues/3221) deleting the **owncloud/data/cron.lock** file gets the cron back up running
-
-Another way to fix this is to run a custom [updater script](https://github.com/owncloud/news/wiki/Custom-Updater)
-
-### All feeds are not updated and theres no cron.lock
+### Feeds are not updated
* Check if the cronjob exists with **crontab -u www-data -e** (replace www-data with your httpd user)
* Check the file permissions of the **cron.php** file and if **www-data** (or whatever your httpd user is called like) can read and execute that script
* Check if the cronjob is ever executed by placing an **error_log('updating')** in the [background job file](https://github.com/owncloud/news/blob/master/backgroundjob/task.php#L37). If the cronjob runs, there should be an updating log statement in your httpd log.