To make sure you are using the correct instuctions, refer to your hosting company support articles or ask your system administrator.
For example, a random article says that the cron job command looks like this: This is correct, but you also should remember, that permissions for /var/www/magento/file should allow its execution.
I installed Magento 2.0.7 in Ubuntu server 14.0.4 (AWS) and followed the differents steps described here but I had this error : update-cron. $non Writable Paths = $permission Info- I'm running Magento 2.0.10 and in my case it seems like Magento wants to have every single file and directory writeable in its root directory. The first time I checked it it was over 10GB in size.
That includes a directory with a Word Press installation and .bashrc file. Cron Readiness zip I am experiencing this problem too when updating.
Do not forget to change /path/to/your/magento/site/root to the path of your website’s default folder.I have tried @bramklg fix and I can't get it to run. I have tried everything in the cron scripts help tutorial and I think I setup cron correctly...Check Cron Scripts task is the only task that fails.I have been Googling permutations of these error messages for the last few days trying to find a solution to no avail. Il mercoledì 15 giugno 2016, Mark Bonano [email protected] scritto: 1 I have replicated this issue on v2.0.7 and despite a variety of attempts at modifying the cron jobs in order to circumvent this issue, I continue to see the following error: update-cron. Found following non-writable paths   Can this issue be assigned to a developer? Reply to this email directly, view it on Git Hub #4911 (comment), or mute the thread https://github.com/notifications/unsubscribe/AGIg Nwjp XRa VHw QLc GGOBNd9i1CGP0gcks5q MEGtga Jp ZM4Ivn Ue . We had the same issue and it was because of a statistics directory where magento did not have write permissions for, however the log was empty (e.g.not showing the directories or files it could not write to or read from). Thanks :-) Hello everyone, I am having a similar issue with a little twist.Make sure you use the correct email address in MAILTO.