Bug#719280: Error/warn: Config variable .... is not defined - Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}

To: Andre Verwijs <verwijs.pc@gmail.com>, 719280@bugs.debian.org
Subject: Bug#719280: Error/warn: Config variable .... is not defined - Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}
From: "Jean-Michel Vourgère" <jmv_deb@nirgal.com>
Date: Sat, 10 Aug 2013 18:19:04 +0000
Message-id: <[🔎] 201308101819.11635.jmv_deb@nirgal.com>
Reply-to: "Jean-Michel Vourgère" <jmv_deb@nirgal.com>, 719280@bugs.debian.org
In-reply-to: <[🔎] 52067E57.5050501@gmail.com>
References: <[🔎] 52067E57.5050501@gmail.com>

On Saturday 10 August 2013 17:54:31 Andre Verwijs wrote:
> service apache2 start doesn't work because of above reported bug..!!

The errors you are talking about are what you get when you enter "apache2" on
the command line.
apache2 is not supposed to work without the proper environement being set up
first.
This is described  in /usr/share/doc/apache2/README.Debian.gz for example.

Now, if the service doesn't start, that's another matter entierely.

Reply to:

Follow-Ups:
- Bug#719280: Error/warn: Config variable .... is not defined - Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}
  - From: "Jean-Michel Vourgère" <jmv_deb@nirgal.com>

References:
- Bug#719280: Error/warn: Config variable .... is not defined - Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}
  - From: Andre Verwijs <verwijs.pc@gmail.com>

Prev by Date: Bug#719280: Error/warn: Config variable .... is not defined - Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}
Next by Date: Bug#719266: apache2_invoke enconf ignores dependencies disabled by admin
Previous by thread: Bug#719280: Error/warn: Config variable .... is not defined - Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}
Next by thread: Bug#719280: Error/warn: Config variable .... is not defined - Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}
Index(es):
- Date
- Thread