On 7/7/24 5:42 PM, Alex wrote:
Is it specifically /home or the application's home directory?
It's specifically /home.
For example, this is the home directory for my website:
alex:x:1007:1007::/var/www/www.example.com:/sbin/nologin
From there, I have html/, logs/ and .ssh/ and have generally
>
>
> > 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 w
On Jul 5, 2024, at 13:40, Alex wrote: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/http://www.mysite.com/logs/error_log>www.mysite.com/logs/e
Alex writes:
Do you have any idea why this option isn't part of the systemd service file
on the other systems I upgraded? The document root for the other systems
uses/var/www, but they didn't have this problem, and their home directories
are also defined with this path.
I checked my other
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/http://www.mysite.com/logs/error_log>
> www.mysite.com/logs/err
> > or_log.
> > AH000
Alex writes:
« HTML content follows
»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/http://www.mysite.com/logs/error_log>www.mysite.com/logs/err
Hi,
On Thu, Jul 4, 2024 at 7:36 PM Tim via users
wrote:
> Tim:
> >> Why are you trying to write log files into your homespace?
>
> Alex:
> > It's a legacy system (think webalizer era), but there are also
> > multiple virtual hosts and it makes it easier to keep them segmented.
> > The document
Tim:
>> Why are you trying to write log files into your homespace?
Alex:
> It's a legacy system (think webalizer era), but there are also
> multiple virtual hosts and it makes it easier to keep them segmented.
> The document root is in /home/httpd/www.mysite.com/html.
>
> There's not enough space
>
>
> > 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
> >
> > It has something to
On Thu, 2024-07-04 at 16:31 -0400, Alex 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 l
On Thu, Jul 4, 2024 at 4:48 PM Alex 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 l
I wouldn't focus on filesystem, but on selinux.
Jul 4, 2024 22:32:47 Alex :
> 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/l
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.
AH00015: Unable to open logs
It has something to do with /home, as it seems it
13 matches
Mail list logo
