From Newsgroup: alt.os.linux

# systemctl start apache2.service
Job for apache2.service failed because the control
process exited with error code.
See "systemctl status apache2.service" and "journalctl -xeu
apache2.service" for details.

# systemctl status apache2.service

httpd-prefork: Syntax error in -C/-c directive: Syntax error on line 2
of /etc/apache2/sysconfig.d/include.conf: Could not open configuration
file /path/myapache/myapache.conf: Permission denied


/etc/apache2/sysconfig.d/include.conf

# File generated from /etc/sysconfig/apache2, do not edit. Edit the
sysconfig file instead.
Include /path/myapache/myapache.conf


It seems to find a synatx error in my fully qualified path to my config
file which has wide open permissions (using as local server only).

What am I missing?



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Mon, 11 May 2026 22:44:25 -0400, bad sector wrote:

Include /path/myapache/myapache.conf

It seems to find a synatx error in my fully qualified path to my config
file which has wide open permissions (using as local server only).

Do all components of the path have suitable permissions?
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 12/05/2026 04.44, bad sector wrote:

# systemctl start apache2.service
Job for apache2.service failed because the control
process exited with error code.
See "systemctl status apache2.service" and "journalctl -xeu
apache2.service" for details.

# systemctl status apache2.service

httpd-prefork: Syntax error in -C/-c directive: Syntax error on line 2
of /etc/apache2/sysconfig.d/include.conf: Could not open configuration
file /path/myapache/myapache.conf: Permission denied

/etc/apache2/sysconfig.d/include.conf

# File generated from /etc/sysconfig/apache2, do not edit. Edit the sysconfig file instead.
Include /path/myapache/myapache.conf

It seems to find a synatx error in my fully qualified path to my config
file which has wide open permissions (using as local server only).

What am I missing?

run the following oneline (everything in the same line, just replace the
path with the real one)

apconf_path=/path/myapache/myapache.conf; while [ "$apconf_path" != "/"
]; do ls -ld "$apconf_path"; apconf_path=$(dirname "$apconf_path"); done;

the result could look something like:
-rw-r----- 1 user user 47 Jan 21 2025 /path/myapache/myapache.conf
drwxr-xr-x 1 user user 114 Apr 14 11:08 /path/myapache
drwxr-xr-x 1 root root 6044 May 15 21:16 /path

the wwwrun user should have access to go into each directory, so all of
them needs to be x, the file itself needs to be r for the wwwrun user.

There is few options:
1. on all directories in the path "chmod o+x /path/to/dir" and the file
itself "chmod o+r /path/myapache/myapache.conf"
2. You change the group to wwwrun and ensure that the paths all parts
has g+x for directories and g+r for the file itself.
3. You make wwwrun to be member of your user group.

The "simplest" is option 1.
--
//Aho
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 2026-05-12 08:43, J.O. Aho wrote:

On 12/05/2026 04.44, bad sector wrote:

# systemctl start apache2.service
Job for apache2.service failed because the control
process exited with error code.
See "systemctl status apache2.service" and "journalctl -xeu
apache2.service" for details.

# systemctl status apache2.service

httpd-prefork: Syntax error in -C/-c directive: Syntax error on line 2
of /etc/apache2/sysconfig.d/include.conf: Could not open configuration
file /path/myapache/myapache.conf: Permission denied


/etc/apache2/sysconfig.d/include.conf

# File generated from /etc/sysconfig/apache2, do not edit. Edit the
sysconfig file instead.
Include /path/myapache/myapache.conf


It seems to find a synatx error in my fully qualified path to my
config file which has wide open permissions (using as local server only).

What am I missing?

run the following oneline (everything in the same line, just replace the path with the real one)

apconf_path=/path/myapache/myapache.conf; while [ "$apconf_path" !=
"/" ]; do ls -ld "$apconf_path"; apconf_path=$(dirname "$apconf_path"); done;

the result could look something like:
-rw-r----- 1 user user 47 Jan 21-a 2025 /path/myapache/myapache.conf drwxr-xr-x 1 user user 114 Apr 14 11:08 /path/myapache
drwxr-xr-x 1 root root 6044 May 15 21:16 /path

the wwwrun user should have access to go into each directory, so all of
them needs to be x, the file itself needs to be r for the wwwrun user.

There is few options:
1. on all directories in the path "chmod o+x /path/to/dir" and the file itself "chmod o+r /path/myapache/myapache.conf"
2. You change the group to wwwrun and ensure that the paths all parts
has g+x for directories and g+r for the file itself.
3. You make wwwrun to be member of your user group.

The "simplest" is option 1.

You also need to look at apparmor or selinux.
--
Cheers, Carlos.
ESEfc-Efc+, EUEfc-Efc|;
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 12/05/2026 10.35, Carlos E.R. wrote:

On 2026-05-12 08:43, J.O. Aho wrote:

On 12/05/2026 04.44, bad sector wrote:

httpd-prefork: Syntax error in -C/-c directive: Syntax error on line
2 of /etc/apache2/sysconfig.d/include.conf: Could not open
configuration file /path/myapache/myapache.conf: Permission denied

There is few options:
1. on all directories in the path "chmod o+x /path/to/dir" and the
file itself "chmod o+r /path/myapache/myapache.conf"

The "simplest" is option 1.

You also need to look at apparmor or selinux.

That can be an issue too, that is simplest to detect to look at in the
audit log
grep '/path/myapache/myapache.conf' /var/log/audit.log

or

grep '/path/myapache/myapache.conf' /var/log/audit/audit.log

depending on the location of the log file. Look for something like
DENIED in the rows that matches to the search, if so, then you need to
take a look at apparmor/selinux documentation how to allow access to the
file.
--
//Aho

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 2026-05-12 12:55, J.O. Aho wrote:

On 12/05/2026 10.35, Carlos E.R. wrote:

On 2026-05-12 08:43, J.O. Aho wrote:

On 12/05/2026 04.44, bad sector wrote:

httpd-prefork: Syntax error in -C/-c directive: Syntax error on line
2 of /etc/apache2/sysconfig.d/include.conf: Could not open
configuration file /path/myapache/myapache.conf: Permission denied

There is few options:
1. on all directories in the path "chmod o+x /path/to/dir" and the
file itself "chmod o+r /path/myapache/myapache.conf"

The "simplest" is option 1.

You also need to look at apparmor or selinux.

That can be an issue too, that is simplest to detect to look at in the
audit log
grep '/path/myapache/myapache.conf' /var/log/audit.log

or

grep '/path/myapache/myapache.conf' /var/log/audit/audit.log

depending on the location of the log file. Look for something like
DENIED in the rows that matches to the search, if so, then you need to
take a look at apparmor/selinux documentation how to allow access to the file.

If it is apparmor, the tool to use is aa-logprof
--
Cheers, Carlos.
ESEfc-Efc+, EUEfc-Efc|;
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/12/26 2:43 AM, J.O. Aho wrote:

On 12/05/2026 04.44, bad sector wrote:

# systemctl start apache2.service
Job for apache2.service failed because the control
process exited with error code.
See "systemctl status apache2.service" and "journalctl -xeu
apache2.service" for details.

# systemctl status apache2.service

httpd-prefork: Syntax error in -C/-c directive: Syntax error on line 2
of /etc/apache2/sysconfig.d/include.conf: Could not open configuration
file /path/myapache/myapache.conf: Permission denied


/etc/apache2/sysconfig.d/include.conf

# File generated from /etc/sysconfig/apache2, do not edit. Edit the
sysconfig file instead.
Include /path/myapache/myapache.conf


It seems to find a synatx error in my fully qualified path to my
config file which has wide open permissions (using as local server only).

What am I missing?

run the following oneline (everything in the same line, just replace the path with the real one)

apconf_path=/path/myapache/myapache.conf; while [ "$apconf_path" !=
"/" ]; do ls -ld "$apconf_path"; apconf_path=$(dirname "$apconf_path"); done;

the result could look something like:
-rw-r----- 1 user user 47 Jan 21-a 2025 /path/myapache/myapache.conf drwxr-xr-x 1 user user 114 Apr 14 11:08 /path/myapache
drwxr-xr-x 1 root root 6044 May 15 21:16 /path

the wwwrun user should have access to go into each directory, so all of
them needs to be x, the file itself needs to be r for the wwwrun user.

There is few options:
1. on all directories in the path "chmod o+x /path/to/dir" and the file itself "chmod o+r /path/myapache/myapache.conf"
2. You change the group to wwwrun and ensure that the paths all parts
has g+x for directories and g+r for the file itself.
3. You make wwwrun to be member of your user group.

The "simplest" is option 1.

the real path is a little longer and I used two versions of it

~ apconf_path=/home/u3/0/htdocs/user/myapache/myapache.conf; while [ "$apconf_path" != "/" ]; do ls -ld "$apconf_path"; apconf_path=$(dirname "$apconf_path"); done;

-rwxrwxrwx 1 u3 users 2374 May 11 22:20 /home/u3/0/htdocs/user/myapache/myapache.conf
drwxrwxrwx 2 u3 users 4096 May 11 22:20 /home/u3/0/htdocs/user/myapache drwxrwxrwx 12 u3 users 4096 May 11 23:07 /home/u3/0/htdocs/user
drwxrwxrwx 3 u3 users 4096 Mar 26 2025 /home/u3/0/htdocs
lrwxrwxrwx. 1 u3 users 17 Aug 24 2025 /home/u3/0 -> /0/homes/u3/0Link drwx------. 26 u3 users 4096 May 12 18:56 /home/u3
dr-xr-xr-x. 6 root root 4096 Aug 26 2025 /home


~ apconf_path=/0/homes/u3/0Link/htdocs/user/myapache/myapache.conf;
while [ "$apconf_path" != "/" ]; do ls -ld "$apconf_path"; apconf_path=$(dirname "$apconf_path"); done;

-rwxrwxrwx 1 u3 users 2374 May 11 22:20 /0/homes/u3/0Link/htdocs/user/myapache/myapache.conf
drwxrwxrwx 2 u3 users 4096 May 11 22:20
/0/homes/u3/0Link/htdocs/user/myapache
drwxrwxrwx 12 u3 users 4096 May 11 23:07 /0/homes/u3/0Link/htdocs/user drwxrwxrwx 3 u3 users 4096 Mar 26 2025 /0/homes/u3/0Link/htdocs
drwxrwxrwx 17 u3 users 4096 May 11 21:45 /0/homes/u3/0Link
drwxrwxrwx 19 u3 users 4096 Jan 22 20:40 /0/homes/u3

for the one in your other post (re: selinux)

# grep '/home/u3/0/htdocs/user/myapache/myapache.conf' /var/log/audit/audit.log

returns nothing


sorry about the breaks, I figure this is less hassle that a link to
susepaste













--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/12/26 1:47 AM, Lawrence DrCOOliveiro wrote:

On Mon, 11 May 2026 22:44:25 -0400, bad sector wrote:

Include /path/myapache/myapache.conf

It seems to find a synatx error in my fully qualified path to my config
file which has wide open permissions (using as local server only).

Do all components of the path have suitable permissions?

everything under /path is rw everyone


--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 13/05/2026 03.04, bad sector wrote:

the real path is a little longer and I used two versions of it
drwx------. 26 u3 users 4096 May 12 18:56 /home/u3

This is a blocker, only u3 is allowed, chmod so others can access it.
--
//Aho
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 2026-05-13 08:01, J.O. Aho wrote:

On 13/05/2026 03.04, bad sector wrote:

the real path is a little longer and I used two versions of it
drwx------. 26 u3 users 4096 May 12 18:56 /home/u3

This is a blocker, only u3 is allowed, chmod so others can access it.

Or use acl to give access to wwwrun.
--
Cheers, Carlos.
ESEfc-Efc+, EUEfc-Efc|;
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/13/26 2:01 AM, J.O. Aho wrote:

On 13/05/2026 03.04, bad sector wrote:

the real path is a little longer and I used two versions of it
drwx------. 26 u3 users 4096 May 12 18:56 /home/u3

This is a blocker, only u3 is allowed, chmod so others can access it.

Even if u3 is the user trying to access it? It's the only user in fact,
there are others but they're always on their windows and apples instead.



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

bad sector <forgetski@_INVALID.net> writes:

On 5/13/26 2:01 AM, J.O. Aho wrote:

On 13/05/2026 03.04, bad sector wrote:

the real path is a little longer and I used two versions of it
drwx------. 26 u3 users 4096 May 12 18:56 /home/u3

This is a blocker, only u3 is allowed, chmod so others can access
it.

Even if u3 is the user trying to access it? It's the only user in
fact, there are others but they're always on their windows and apples instead.

u3 can access it, no other user can. Apache wonrCOt be running as u3,
unless yourCOve specifically arranged that it does.

Just put your config file in a more sensible place.
--
https://www.greenend.org.uk/rjk/
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/13/26 7:08 PM, Richard Kettlewell wrote:

bad sector <forgetski@_INVALID.net> writes:

On 5/13/26 2:01 AM, J.O. Aho wrote:

On 13/05/2026 03.04, bad sector wrote:

the real path is a little longer and I used two versions of it
drwx------. 26 u3 users 4096 May 12 18:56 /home/u3

This is a blocker, only u3 is allowed, chmod so others can access
it.

Even if u3 is the user trying to access it? It's the only user in
fact, there are others but they're always on their windows and apples
instead.

u3 can access it, no other user can. Apache wonrCOt be running as u3,
unless yourCOve specifically arranged that it does.

Just put your config file in a more sensible place.

I tried /var/myapache/myapache.conf no change :-(

# apconf_path=/var/myapache/myapache.conf; while [ "$apconf_path" != "/"
]; do ls -ld "$apconf_path"; apconf_path=$(dirname "$apconf_path"); done;

-rwxrwxrwx. 1 root users 2479 May 13 19:24 /var/myapache/myapache.conf drwxrwxrwx. 2 root users 4096 May 13 19:24 /var/myapache
drwxr-xr-x. 12 root root 4096 May 13 20:19 /var


# systemctl status apache2.service
==================================

rui apache2.service - The Apache Webserver
Loaded: loaded (/usr/lib/systemd/system/apache2.service; disabled; preset: disabled)
Active: inactive (dead)



# systemctl start apache2.service
=================================

Job for apache2.service failed because the control process exited with
error code.
See "systemctl status apache2.service" and "journalctl -xeu
apache2.service" for details.



# systemctl status apache2.service
==================================

|u apache2.service - The Apache Webserver
Loaded: loaded (/usr/lib/systemd/system/apache2.service; disabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2026-05-13 20:33:20
EDT; 29s ago
Invocation: d3cf30c2a5ca4f38ab400a850ea08832
Process: 3268 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD
-DFOREGROUND -k start (code=exited, status=1/FAILURE)
Main PID: 3268 (code=exited, status=1/FAILURE)
CPU: 19ms

May 13 20:33:20 localhost.localdomain systemd[1]: Starting The Apache Webserver...
May 13 20:33:20 localhost.localdomain start_apache2[3268]:
httpd-prefork: Syntax error in -C/-c directive: Syntax error on line 2
of /etc/apache2/sysconfig.d/include.conf: Could not open configuration
file /var/myapache/myapache.conf: Permission denied
May 13 20:33:20 localhost.localdomain systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE
May 13 20:33:20 localhost.localdomain systemd[1]: apache2.service:
Failed with result 'exit-code'.
May 13 20:33:20 localhost.localdomain systemd[1]: Failed to start The
Apache Webserver.






# journalctl -xeu apache2.service
=================================

May 13 20:33:20 localhost.localdomain systemd[1]: Starting The Apache Webserver...
ruarua Subject: A start job for unit apache2.service has begun execution
ruarua Defined-By: systemd
ruarua Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ruarua
ruarua A start job for unit apache2.service has begun execution.
ruarua
ruarua The job identifier is 5059.
May 13 20:33:20 localhost.localdomain start_apache2[3268]:
httpd-prefork: Syntax error in -C/-c directive: Syntax error on line 2
of /etc/apache2/sysconfig.d/include.conf: Could not open configuration
file /var/myapache/myapache.conf: Permission denied
May 13 20:33:20 localhost.localdomain systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE
ruarua Subject: Unit process exited
ruarua Defined-By: systemd
ruarua Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ruarua
ruarua An ExecStart= process belonging to unit apache2.service has exited. ruarua
ruarua The process' exit code is 'exited' and its exit status is 1.
May 13 20:33:20 localhost.localdomain systemd[1]: apache2.service:
Failed with result 'exit-code'.
ruarua Subject: Unit failed
ruarua Defined-By: systemd
ruarua Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ruarua
ruarua The unit apache2.service has entered the 'failed' state with result 'exit-code'.
May 13 20:33:20 localhost.localdomain systemd[1]: Failed to start The
Apache Webserver.
ruarua Subject: A start job for unit apache2.service has failed
ruarua Defined-By: systemd
ruarua Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ruarua
ruarua A start job for unit apache2.service has finished with a failure.
ruarua
ruarua The job identifier is 5059 and the job result is failed.










--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Wed, 13 May 2026 17:54:24 -0400, bad sector wrote:

On 5/13/26 2:01 AM, J.O. Aho wrote:

On 13/05/2026 03.04, bad sector wrote:

the real path is a little longer and I used two versions of it
drwx------. 26 u3 users 4096 May 12 18:56 /home/u3

This is a blocker, only u3 is allowed, chmod so others can access
it.

Even if u3 is the user trying to access it?

Apache normally runs web-facing code under the rCLwww-datarCY user.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 14/05/2026 02.45, bad sector wrote:

May 13 20:33:20 localhost.localdomain systemd[1]: Starting The Apache Webserver...
May 13 20:33:20 localhost.localdomain start_apache2[3268]: httpd-
prefork: Syntax error in -C/-c directive: Syntax error on line 2 of / etc/apache2/sysconfig.d/include.conf: Could not open configuration
file /var/myapache/myapache.conf: Permission denied

Could you run:

sudo getenforce | grep -E "(SELinux status|Current mode)"

and

sudo aa-status


I know one of them should generate command not found, but just want to
be on the safe side.


Reading the apache documentation https://httpd.apache.org/docs/2.4/mod/core.html#include

even if it allows the full path, it may require that the file is located
in the apache configuration directory structure.

Traditionally you would use AllowOverride in the configuration to allow
users to use .htaccess files, and maybe that is the way for you to go https://httpd.apache.org/docs/2.4/mod/core.html#allowoverride
--
//Aho

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

bad sector <forgetski@_INVALID.net> writes:

On 5/13/26 7:08 PM, Richard Kettlewell wrote:

u3 can access it, no other user can. Apache wonrCOt be running as u3,
unless yourCOve specifically arranged that it does.
Just put your config file in a more sensible place.

I tried /var/myapache/myapache.conf no change :-(

That is not a sensible place. /etc is for configuration, /var is for
variable state.

# apconf_path=/var/myapache/myapache.conf; while [ "$apconf_path" !=
"/" ]; do ls -ld "$apconf_path"; apconf_path=$(dirname
"$apconf_path"); done;

-rwxrwxrwx. 1 root users 2479 May 13 19:24 /var/myapache/myapache.conf drwxrwxrwx. 2 root users 4096 May 13 19:24 /var/myapache
drwxr-xr-x. 12 root root 4096 May 13 20:19 /var

You need to sort out the file permissions too. Some applications will
refuse to open files with insecure permisssions. I donrCOt know if Apache
is one of them (and I donrCOt care, because I donrCOt make all my files
world writable).

If you want to get somewhere, stop trying to swim against the tide.
--
https://www.greenend.org.uk/rjk/
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/14/26 4:25 AM, J.O. Aho wrote:

On 14/05/2026 02.45, bad sector wrote:

May 13 20:33:20 localhost.localdomain systemd[1]: Starting The Apache
Webserver...
May 13 20:33:20 localhost.localdomain start_apache2[3268]: httpd-
prefork: Syntax error in -C/-c directive: Syntax error on line 2 of /
etc/apache2/sysconfig.d/include.conf: Could not open configuration
file /var/myapache/myapache.conf: Permission denied

Could you run:

sudo getenforce | grep -E "(SELinux status|Current mode)"

# getenforce
no response

and

sudo aa-status

# aa-status

The program 'aa-status' can be found in the following package:
* apparmor-parser [ path: /usr/sbin/aa-status, repository: repo-oss ]

Try installing with:
sudo zypper install apparmor-parser

I know one of them should generate command not found, but just want to
be on the safe side.

Reading the apache documentation https://httpd.apache.org/docs/2.4/mod/core.html#include

even if it allows the full path, it may require that the file is located
in the apache configuration directory structure.

This seems to a part of it, don't know why or since when, it was never
an issue before. Anyway, relocated my add-on config to

/etc/apache2/myapache.conf

and that seems to have fixed the failed start problem
and a new one to surface:

127.0.0.1

You don't have permission to access the requested directory. There is
either no index document or the directory is read-protected.

Don't know if THIS has anything to do with it:

May 14 19:56:25 customer.mntlcan1.isp.starlink.com systemd[1]: Starting
The Apache Webserver...
May 14 19:56:25 customer.mntlcan1.isp.starlink.com start_apache2[3402]: AH00557: httpd-prefork: apr_sockaddr_info_get() failed for customer.mntlcan1.isp.starlink.com
May 14 19:56:25 customer.mntlcan1.isp.starlink.com start_apache2[3402]: AH00558: httpd-prefork: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message


This wasn't a problem before either. What is 'requested directory'?
Everything under htdocs is still 777 (for testing).

/var/log/apache2/error.log says:

[Thu May 14 20:35:53.863279 2026] [core:error] [pid 4579:tid 4579] (13)Permission denied: [client 127.0.0.1:48674] AH00035: access to /temp-pub-buffer/coques-clams.jpg denied (filesystem path '/0/homes/u3/0Link/htdocs/user/temp-pub-buffer/coques-clams.jpg')
because search permissions are missing on a component of the path

"because search permissions are missing on a component of the path"???

I wan't NO auto indexing so trhis is the defalut-server.conf

IndexIgnore * */* .??* *~ *

..or any other form of indexing so there is an index.html file in all directories but most of them just remind the visitor to request a
specific URL.

Since when or on what basis are 'search permissions' a 'requirement'?

Traditionally you would use AllowOverride in the configuration to allow users to use .htaccess files, and maybe that is the way for you to go https://httpd.apache.org/docs/2.4/mod/core.html#allowoverride

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/14/26 5:13 AM, Richard Kettlewell wrote:

bad sector <forgetski@_INVALID.net> writes:

On 5/13/26 7:08 PM, Richard Kettlewell wrote:

u3 can access it, no other user can. Apache wonrCOt be running as u3,
unless yourCOve specifically arranged that it does.
Just put your config file in a more sensible place.

I tried /var/myapache/myapache.conf no change :-(

That is not a sensible place. /etc is for configuration, /var is for
variable state.

Was not a problem before, changed it to

/etc/apache2/myapache.conf

which seems to have fixed the no start issue

You need to sort out the file permissions too. Some applications will
refuse to open files with insecure permisssions. I donrCOt know if Apache
is one of them (and I donrCOt care, because I donrCOt make all my files
world writable).

Wasn't a problem before

If you want to get somewhere, stop trying to swim against the tide.

The error message cited 'permission denied' but you're right, it could
have been because NOW (no idea since when or why) my congfig add-in in a
more restrictive PATH seems to work. File permissions make no difference
as such from

-rwxrwxrwx. 1 u3 users

to

rw-r-----. 1 root root

so it's tha PATH that seems to make the difference



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/13/26 9:05 PM, Lawrence DrCOOliveiro wrote:

On Wed, 13 May 2026 17:54:24 -0400, bad sector wrote:

On 5/13/26 2:01 AM, J.O. Aho wrote:

On 13/05/2026 03.04, bad sector wrote:

the real path is a little longer and I used two versions of it
drwx------. 26 u3 users 4096 May 12 18:56 /home/u3

This is a blocker, only u3 is allowed, chmod so others can access
it.

Even if u3 is the user trying to access it?

Apache normally runs web-facing code under the rCLwww-datarCY user.

Tye only entries with www in them in /etc/groups are

www:x:461:wwwrun
wwwrun:x:460:

Suse does things differently (too often AFAIC)



But I did find something weird while looking at that file:

user u3 belongs to primary group users but the line

users:x:100:

had no u3 entry

I have no idea how come or since when!

Corrected, didn't change anything
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/14/26 5:13 AM, Richard Kettlewell wrote:

bad sector <forgetski@_INVALID.net> writes:

On 5/13/26 7:08 PM, Richard Kettlewell wrote:

u3 can access it, no other user can. Apache wonrCOt be running as u3,
unless yourCOve specifically arranged that it does.
Just put your config file in a more sensible place.

I tried /var/myapache/myapache.conf no change :-(

That is not a sensible place. /etc is for configuration, /var is for
variable state.

Was not a problem before, changed it to

/etc/apache2/myapache.conf

which seems to have fixed the no start issue

You need to sort out the file permissions too. Some applications will
refuse to open files with insecure permisssions. I donrCOt know if Apache
is one of them (and I donrCOt care, because I donrCOt make all my files
world writable).

Wasn't a problem before

If you want to get somewhere, stop trying to swim against the tide.

The error message cited 'permission denied' but you're right, it could
have been because NOW (no idea since when or why) my congfig add-in in a
more restrictive PATH seems to work. File permissions make no difference
as such from

-rwxrwxrwx. 1 u3 users

to

rw-r-----. 1 root root

so it's tha PATH that seems to make the difference



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/14/26 5:13 AM, Richard Kettlewell wrote:

bad sector <forgetski@_INVALID.net> writes:

On 5/13/26 7:08 PM, Richard Kettlewell wrote:

u3 can access it, no other user can. Apache wonrCOt be running as u3,
unless yourCOve specifically arranged that it does.
Just put your config file in a more sensible place.

I tried /var/myapache/myapache.conf no change :-(

That is not a sensible place. /etc is for configuration, /var is for
variable state.

Was not a problem before, changed it to

/etc/apache2/myapache.conf

which seems to have fixed the no start issue

You need to sort out the file permissions too. Some applications will
refuse to open files with insecure permisssions. I donrCOt know if Apache
is one of them (and I donrCOt care, because I donrCOt make all my files
world writable).

Wasn't a problem before

If you want to get somewhere, stop trying to swim against the tide.

The error message cited 'permission denied' but you're right, it could
have been because NOW (no idea since when or why) my congfig add-in in a
more restrictive PATH seems to work. File permissions make no difference
as such from

-rwxrwxrwx. 1 u3 users

to

rw-r-----. 1 root root

so it's tha PATH that seems to make the difference



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/14/26 5:13 AM, Richard Kettlewell wrote:

bad sector <forgetski@_INVALID.net> writes:

On 5/13/26 7:08 PM, Richard Kettlewell wrote:

u3 can access it, no other user can. Apache wonrCOt be running as u3,
unless yourCOve specifically arranged that it does.
Just put your config file in a more sensible place.

I tried /var/myapache/myapache.conf no change :-(

That is not a sensible place. /etc is for configuration, /var is for
variable state.

# apconf_path=/var/myapache/myapache.conf; while [ "$apconf_path" !=
"/" ]; do ls -ld "$apconf_path"; apconf_path=$(dirname
"$apconf_path"); done;

-rwxrwxrwx. 1 root users 2479 May 13 19:24 /var/myapache/myapache.conf
drwxrwxrwx. 2 root users 4096 May 13 19:24 /var/myapache
drwxr-xr-x. 12 root root 4096 May 13 20:19 /var

You need to sort out the file permissions too. Some applications will
refuse to open files with insecure permisssions. I donrCOt know if Apache
is one of them (and I donrCOt care, because I donrCOt make all my files
world writable).

If you want to get somewhere, stop trying to swim against the tide.

On 5/14/26 5:13 AM, Richard Kettlewell wrote:

bad sector <forgetski@_INVALID.net> writes:

On 5/13/26 7:08 PM, Richard Kettlewell wrote:

u3 can access it, no other user can. Apache wonrCOt be running as u3,
unless yourCOve specifically arranged that it does.
Just put your config file in a more sensible place.

I tried /var/myapache/myapache.conf no change :-(

That is not a sensible place. /etc is for configuration, /var is for variable state.

Was not a problem before, changed it to

/etc/apache2/myapache.conf

which seems to have fixed the no start issue

You need to sort out the file permissions too. Some applications will
refuse to open files with insecure permisssions. I donrCOt know if Apache
is one of them (and I donrCOt care, because I donrCOt make all my files world writable).

Wasn't a problem before

If you want to get somewhere, stop trying to swim against the tide.

The error message cited 'permission denied' but you're right, it could
have been because NOW (no idea since when or why) my congfig add-in in a
more restrictive PATH seems to work. File permissions make no difference
as such from

-rwxrwxrwx. 1 u3 users

to

rw-r-----. 1 root root

so it's tha PATH that seems to make the difference



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 15/05/2026 03.16, bad sector wrote:

/var/log/apache2/error.log says:

[Thu May 14 20:35:53.863279 2026] [core:error] [pid 4579:tid 4579] (13)Permission denied: [client 127.0.0.1:48674] AH00035: access to / temp-pub-buffer/coques-clams.jpg denied (filesystem path '/0/homes/ u3/0Link/htdocs/user/temp-pub-buffer/coques-clams.jpg') because search permissions are missing on a component of the path

you could try something like:
chcon -R --type=httpd_sys_rw_content_t /0/homes/ u3/0Link/htdocs

found this stack overflow for it: https://stackoverflow.com/questions/25190043/apache-permissions-are-missing-on-a-component-of-the-path

"because search permissions are missing on a component of the path"???

I wan't NO auto indexing so trhis is the defalut-server.conf

IndexIgnore * */* .??* *~ *

..or any other form of indexing so there is an index.html file in all directories but most of them just remind the visitor to request a
specific URL.

Think this is unrelated, but if you don't want files to be listed, then disable the mod_autoindex, not sure where you do that either it's in the
main config or it's in the server service config as a -D option. It's
been like 8 years since I last played with apache.
--
//Aho
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/15/26 1:56 AM, J.O. Aho wrote:

On 15/05/2026 03.16, bad sector wrote:

/var/log/apache2/error.log says:

[Thu May 14 20:35:53.863279 2026] [core:error] [pid 4579:tid 4579]
(13)Permission denied: [client 127.0.0.1:48674] AH00035: access to /
temp-pub-buffer/coques-clams.jpg denied (filesystem path '/0/homes/
u3/0Link/htdocs/user/temp-pub-buffer/coques-clams.jpg') because search
permissions are missing on a component of the path

you could try something like:
chcon -R --type=httpd_sys_rw_content_t /0/homes/ u3/0Link/htdocs

found this stack overflow for it: https://stackoverflow.com/questions/25190043/apache-permissions-are- missing-on-a-component-of-the-path

Thanks, I'll try that tonight on my desktop, sounds like a maybe (should really just uninstall selinux if I could).


...

It's been like 8 years since I last played with apache.

The only thing I used to use it for was developing and testing my pages
and scripts before uploading to my dns provider. All I want is 127.0.0.1
but that much with absolutely no constraints for scripts, includes or
anything that can work on a web page. Nowadays all I do is the odd edit,
no more dev. or scripting which were never more than amateur efforts anyway.

Problem is, when I get things to work it usually falls apart after a few months when some update fixes what wasn't broken (in terms of my needs).
In the old days it all went into /etc/httpd on all systems but now its scattered all over the place so if I want to avoid tons of duplication
when booting different distros I have to park my rags in a common path accessible from any system.



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 15/05/2026 12.56, bad sector wrote:

On 5/15/26 1:56 AM, J.O. Aho wrote:

you could try something like:
chcon -R --type=httpd_sys_rw_content_t /0/homes/ u3/0Link/htdocs

found this stack overflow for it:
https://stackoverflow.com/questions/25190043/apache-permissions-are-
missing-on-a-component-of-the-path

Thanks, I'll try that tonight on my desktop, sounds like a maybe (should really just uninstall selinux if I could).

You can always switch to permissive mode, kind of a middle ground where
the rules are checked but no active "blocking" done.

...

It's been like 8 years since I last played with apache.

The only thing I used to use it for was developing and testing my pages
and scripts before uploading to my dns provider. All I want is 127.0.0.1
but that much with absolutely no constraints for scripts, includes or anything that can work on a web page. Nowadays all I do is the odd edit,
no more dev. or scripting which were never more than amateur efforts
anyway.

Using enforced selinux will cause a lot of restrictions that are out
over those generally made by the application developers. I feel AppArmor
is a bit more relaxed with their defaults. Sometime even AppArmor can
get badly in the way too, specially if you distro uses some of the
AppArmor default files for applications that have other locations of
file, but that is another story.

Problem is, when I get things to work it usually falls apart after a few months when some update fixes what wasn't broken (in terms of my needs).

This tends to point on a solution that isn't a proper one but a ad-hoc solution, I have always this issue at work, where my co-workers who
ain't that Linux/Unix minded, they just make crazy scripts and think
that solves their problem for it worked when they tested it, but when
the machine is rebooted it don't work anymore, don't really matter how
many times I point out that they may need a service that handles it for
them.

In the old days it all went into /etc/httpd on all systems but now its scattered all over the place so if I want to avoid tons of duplication
when booting different distros I have to park my rags in a common path accessible from any system.

As far as I know, most had /etc/apache and then redhat decided for
/etc/httpd instead, but still I think things are quite organized, /etc/{apache,httpd} for configurations, /var/www for web content, /etc/{default,conf.d} for configure some daemon settings.
--
//Aho

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 2026-05-15 12:56, bad sector wrote:

Problem is, when I get things to work it usually falls apart after a few months when some update fixes what wasn't broken (in terms of my needs).

Then don't use Tumbleweed. Use Leap. :-)

In the old days it all went into /etc/httpd on all systems but now its scattered all over the place so if I want to avoid tons of duplication
when booting different distros I have to park my rags in a common path accessible from any system.

--
Cheers, Carlos.
ESEfc-Efc+, EUEfc-Efc|;
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/15/26 8:20 AM, J.O. Aho wrote:

On 15/05/2026 12.56, bad sector wrote:

On 5/15/26 1:56 AM, J.O. Aho wrote:

you could try something like:
chcon -R --type=httpd_sys_rw_content_t /0/homes/ u3/0Link/htdocs

found this stack overflow for it:
https://stackoverflow.com/questions/25190043/apache-permissions-are-
missing-on-a-component-of-the-path

Thanks, I'll try that tonight on my desktop, sounds like a maybe
(should really just uninstall selinux if I could).

You can always switch to permissive mode, kind of a middle ground where
the rules are checked but no active "blocking" done.

# chcon -R --type=httpd_sys_rw_content_t /home/u3
# chcon -R --type=httpd_sys_rw_content_t /0/homes/u3
# chcon -R --type=httpd_sys_rw_content_t /0/homes/u3/0Link/htdocs
# setenforce 0
# getenforce
Permissive

For TS I'd like to disable, period but don't think that that's where the problem is any more (because aopache now does start).

now I get the access error message

---------------------------
Access forbidden!

You don't have permission to access the requested directory. There is
either no index document or the directory is read-protected. ---------------------------

The error message shouold but does NOT say who 'you' is or what the
'requested directory' is. The web content directories ALL have index
files and none of them are read protected and both of these attributes
are sniffable.








--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/11/26 10:44 PM, bad sector wrote:

# systemctl start apache2.service
Job for apache2.service failed because the control
process exited with error code.
See "systemctl status apache2.service" and "journalctl -xeu
apache2.service" for details.

# systemctl status apache2.service

httpd-prefork: Syntax error in -C/-c directive: Syntax error on line 2
of /etc/apache2/sysconfig.d/include.conf: Could not open configuration
file /path/myapache/myapache.conf: Permission denied

/etc/apache2/sysconfig.d/include.conf

# File generated from /etc/sysconfig/apache2, do not edit. Edit the sysconfig file instead.
Include /path/myapache/myapache.conf

It seems to find a synatx error in my fully qualified path to my config
file which has wide open permissions (using as local server only).

What am I missing?

I reverted EVERYTHING back to the way it was before. This included some
apache directives to be injected from another file (AS PROVIDED FOR IN
APACHE and as had worked before!).

/etc/sysconfig/apache2
APACHE_CONF_INCLUDE_FILES="/etc/apache2/myapache.conf"

The above file included some apache directives. Apache would start but
would also throw an "Access denied" error and no
chcon -R --type=httpd_sys_rw_content_t /0/homes/ u3/0Link/htdocs
or
setenforce 0
wouldn correct it.

So I moved all the additional directives from myapache.conf to

/etc/apache2/default-server.conf

...and that fixed the last problem. So it appears that

APACHE_CONF_INCLUDE_FILES="/etc/apache2/myapache.conf"

is still an existing option but is useless? About the only
directive I can still keep in

/0/homes/u3/0Link/htdocs/user/myapache/myapache.conf

is

DocumentRoot "/0/homes/u3/0Link/htdocs/user"




--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Sun, 5/17/2026 12:57 AM, bad sector wrote:

DocumentRoot "/0/homes/u3/0Link/htdocs/user"

Now, imagine if the apache software had a "default" DocumentRoot.

If you had not defined a DocumentRoot anywhere, it might have
been attempting to use something else (which may or may not exist).

$ sudo nano /etc/apache2/apache2.conf

<Directory /var/www/> <=== presumed DocumentRoot ?
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>

Paul



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/17/26 8:04 AM, Paul wrote:

On Sun, 5/17/2026 12:57 AM, bad sector wrote:

DocumentRoot "/0/homes/u3/0Link/htdocs/user"

Now, imagine if the apache software had a "default" DocumentRoot.

If you had not defined a DocumentRoot anywhere, it might have
been attempting to use something else (which may or may not exist).

$ sudo nano /etc/apache2/apache2.conf

<Directory /var/www/> <=== presumed DocumentRoot ?
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>

Paul

It all started years ago when all distros were using /etc/hhtpd but
advanced features were default disabled. All "I" ever needed or wanted
was an unconstrained LOCAL server for testing without any desire to ever become a web-server specialist. At first I could just drop a link to a
folder in my home or on a remote data drive, then there were periods of assorted constraints none of which were justifiable defaults for a LOCAL server IMHO. As far as I'm concerned I'd like to see a default local
server automatically set up for a user and running with no limitations
on log-in using a folder like maybe ~/localhttpd which that user could optionally link out pointing to any folder using any filesystem anywhere including on the neighbor's piano.

'nuff rant :-)






--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Sun, 17 May 2026 18:19:32 -0400, bad sector wrote:

All "I" ever needed or wanted was an unconstrained LOCAL server for
testing without any desire to ever become a web-server specialist.

You donrCOt even need to run Apache to do that. For example, I can write
a simple test Python program using this <https://docs.python.org/3/library/http.server.html> standard library
module, start it listening on a local port, point my browser at that
port, and IrCOm away.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 5/17/26 6:34 PM, Lawrence DrCOOliveiro wrote:

On Sun, 17 May 2026 18:19:32 -0400, bad sector wrote:

All "I" ever needed or wanted was an unconstrained LOCAL server for
testing without any desire to ever become a web-server specialist.

You donrCOt even need to run Apache to do that. For example, I can write
a simple test Python program using this <https://docs.python.org/3/library/http.server.html> standard library
module, start it listening on a local port, point my browser at that
port, and IrCOm away.

That's over my head and I know less than nothing about py. My provider
uses apache and so if my pages and perl scripts run on my local apache
then chances are that they will also run on his apache web server.



--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Sun, 17 May 2026 22:53:34 -0400, bad sector wrote:

On 5/17/26 6:34 PM, Lawrence DrCOOliveiro wrote:

On Sun, 17 May 2026 18:19:32 -0400, bad sector wrote:

All "I" ever needed or wanted was an unconstrained LOCAL server
for testing without any desire to ever become a web-server
specialist.

You donrCOt even need to run Apache to do that. For example, I can
write a simple test Python program using this
<https://docs.python.org/3/library/http.server.html> standard
library module, start it listening on a local port, point my
browser at that port, and IrCOm away.

That's over my head and I know less than nothing about py. My
provider uses apache and so if my pages and perl scripts run on my
local apache then chances are that they will also run on his apache
web server.

YourCOre not still running CGI scripts, are you?
--- Synchronet 3.22a-Linux NewsLink 1.2