Re: apache won't start after upgrade - read-only filesystem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 4, 2024 at 4:48 PM Alex <mysqlstudent@xxxxxxxxx> wrote:
>
> 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.
> AH00015: Unable to open logs

This smells of SELinux as Alessio pointed out.

> 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)

ls -AlZ is usually your friend when it comes to SELinux. The 'Z'
option shows SELinux labels.

I _think_ stuff served by web servers need user unconfined_u and type
httpd_sys_content_t. Maybe something like:

    chcon -u unconfined_u -t httpd_sys_content_t <file>

> dovecot is also on this system and has no issues with writing to /home.
>
> What could I be missing?

Did you follow post-upgrade tasks detailed at
<https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/>?
One of the steps is to relabel the filesystem.

But I also find you should not serve from your $HOME directory. Move
it to /var or /opt. I believe someone else was asking about a similar
problem recently.

Jeff
-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux