Perhaps this is caused by celery not having write permissions for the celerybeat-schedule
file. The docs you linked to show celery configured to use /var/run/celerybeat-schedule
as the celery beat schedule file.
Does your process have write permissions to that file? If that directory is owned by root
(as it should be) and your process is running as anything other than the root
user, that could cause the permission denied errors.
Check that your permissions are correct and then try deleting that file then restarting everything.