I had exactly the same problem, and finally a friend suggested that it's perhaps SELinux problem, and guess what, it was... Just type:
setenforce 0
and everything will get back to normal...
(of course without security benefits of SELinux, but I don't really need it, anyway..)