selinux
How to solve “Kernel panic – not syncing – Attempted to kill init” — without erasing any user data [closed]
if the full message is: kernel panic – not syncing: Attempted to kill inint ! PId: 1, comm: init not tainted 2.6.32.-279-5.2.e16.x86_64 #1 then you should have disabled selinux and after that you have rebooted the system. The easier way is to use a live OS and re-enable it vim /etc/selinux/config … SELINUX=enforcing … Second … Read more
Attempt to write a readonly database – Django w/ SELinux error
You have to add writing rights to the directory in which your sqlite database is stored. So running chmod -R u+w /srv/mysite/ should help. If a server is using custom user (e.g. www-data) to access the database, the solution could be to change the owner of your database: chown www-data:www-data /srv/mysite chown www-data:www-data /srv/mysite/DATABASE.sqlite