[SOLVED] Apache2 - AH00111: Config variable ${APACHE_RUN_DIR} is not defined

myregm · 08-06-2018, 12:10 PM

Hi. I've some problems with apache2.
When I enter

Code:

service apache2 start

this error appears:

Quote:

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

I tried to enter

Code:

apache2

and this error apears:

Quote:

AH00111: Config variable ${APACHE_RUN_DIR} is not defined apache2: Syntax error on line 80 of /etc/apache2/apache2.conf: DefaultRuntimeDir must be a valid directory, absolute or relative to ServerRoot

In line 80 of /etc/apache2/apache2.conf I have this:

Quote:

DefaultRuntimeDir ${APACHE_RUN_DIR}

I searched on the net to find out where ${APACHE_RUN_DIR} is pointing to but didn't get anything.

Can you please help me?

update:
I've find out where ${APACHE_RUN_DIR} is pointing to. It's

Quote:

/var/run/apache2

I already have this directory but it's empty. Should it be empty? What do you think my problem is?

myregm · 08-06-2018, 12:51 PM

I have solved it by:

Quote:

sudo a2dismod php7.2
sudo a2enmod php7.2
sudo systemctl restart apache2

visit
https://www.tecmint.com/install-diff...ons-in-ubuntu/
for more info.

pegr69 · 10-17-2018, 02:50 AM

Use the new apache2ctl script and all will be fine(should be at least).

jee. · 04-03-2019, 06:57 AM

@myregm That was not the solution of the problem.

Basically you tried to start Apache with an unsupported command that failed with a syntax error. That was the problem.
The supported commands are /etc/init.d/apache2, apachectl and apache2ctl. Do not use the "apache2" command.

By disabling and re-enabling the php module nothing actually changed since that only deleted and recreated a symlink.

When you started Apache server using a supported method the problem went away. Running a valid command was the actual solution as @pegr69 pointed out.

You can see the error by simply running "apache2 -S". This command is safe and won't interfere with your running Apache server.

(see: /usr/share/doc/apache2/README.Debian.gz)

gbell12 · 04-14-2019, 11:29 PM

Quote:

You can see the error by simply running "apache2 -S". This command is safe and won't interfere with your running Apache server.

Meaning, you'll see the same error, but safely because -S just dumps. Probably not useful, since he was getting that error anyway.

But wait, what if you need the functionality of apache2 -S?

jee. points us to /usr/share/doc/apache2/README.Debian.gz, which says, deep down in the FAQ:

Quote:

8) Message "apache2: bad user name ${APACHE_RUN_USER}" when starting apache2
directly

Use apache2ctl (it accepts all the same options as apache2).

Ah, so apache2ctl is what we should be using for everything! A bit odd that there's an available apache2, but "don't use it!" Turns out apache2ctl wraps apache2.

Psype · 03-09-2021, 05:05 PM

Hi guys, sorry for digging, but I found a kind of solution (if you only manage one instance of Apache2)

I added that line right before DefaultRuntimeDir in /etc/apache2/apache2.conf :

Code:

SetEnvIf APACHE_RUN_DIR ^$ APACHE_RUN_DIR=/var/run/apache2
DefaultRuntimeDir ${APACHE_RUN_DIR}

... So if somehow it works again, it won't go in the SetEnvIf...
Of course you might need mod_setenvif I guess.

Cheers