I wouldn't focus on filesystem, but on selinux.

Jul 4, 2024 22:32:47 Alex <mysqlstud...@gmail.com>:

> Hi,
> 
> I've just upgraded from fedora38 to fedora39 and directly to fedora40 and now 
> apache won't start:
> 
> (30)Read-only file system: AH00091: httpd: could not open error log file 
> /home/httpd/www.mysite.com/logs/error_log[http://www.mysite.com/logs/error_log].
> AH00015: Unable to open logs
> 
> It has something to do with /home, as it seems it is unable to write anywhere 
> on /home, even after changing the document root for any virtual host to 
> various directories on /home it still fails with the same message, even 
> though I'm confident the path exists and is writable.
> 
> I've unmounted and checked the filesystem with xfs_check. I've ensured quotas 
> aren't enabled. I've made sure there are no hidden read-only attributes and 
> selinux is completely disabled for this. 
> 
> If I change the document root to /var/www with an otherwise identical virtual 
> config file, it works fine. /var is ext4 while /home is xfs. Perhaps that's 
> the difference? It was always xfs though, even with the previous versions of 
> fedora.
> 
> The entire path to the document root and log directory is readable, but logs 
> are written by root with apache anyway.
> 
> Home is mounted as such:
> # mount|grep md125
> /dev/md125 on /home type xfs 
> (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
> 
> dovecot is also on this system and has no issues with writing to /home.
> 
> What could I be missing?
> 
> 
> 
> 
> 
> 
-- 
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to