Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 815CBC0FC for ; Wed, 7 Jan 2015 17:20:51 +0000 (UTC) Received: (qmail 88792 invoked by uid 500); 7 Jan 2015 17:20:49 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 88756 invoked by uid 500); 7 Jan 2015 17:20:49 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 88746 invoked by uid 99); 7 Jan 2015 17:20:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2015 17:20:49 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [147.194.32.2] (HELO eagle.reach.net) (147.194.32.2) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2015 17:20:22 +0000 Received: from server.stormy.ca ([70.52.195.238]) (authenticated bits=0) by eagle.reach.net (8.14.4/8.14.4) with ESMTP id t07HKJ0E022076 for ; Wed, 7 Jan 2015 12:20:19 -0500 Message-Id: <5.2.1.1.2.20150107103949.047ffe48@stormy.ca> X-Sender: stormy@stormy.ca X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Wed, 07 Jan 2015 12:20:19 -0500 To: users@httpd.apache.org From: Stormy Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Checked: Checked by ClamAV on apache.org Subject: [users@httpd] 2.4.7 setup Ubuntu 14.04 LTS I'm looking for some help, please, in understanding *if* I have problems, and recommendations for what to do (Google has not yet been my friend.) Brand new server Ubuntu 14.04.1 LTS with Ubuntu package Apache/2.4.7, appears to be working, but I'm not certain that all envvars are set up correctly, as I keep getting "Define" warnings/messages, which I'd like to eleiminate. (Our production servers use 2.2, with none of these messages. This new server is LAN only at the moment.) apachectl configtest reports "Syntax OK" Log has intermittent "[core:warn] [pid 2620:tid 140267284031360] AH00111: Config variable ${APACHE_LOG_DIR} is not defined" with ${APACHE_LOCK_DIR} ${APACHE_PID_DIR} and ${APACHE_RUN_DIR} appearing very occasionally. I've tried using mpm_event with occasional "[mpm_event:notice] [pid 1322:tid 140096310007680] AH00493: SIGUSR1 received. Doing graceful restart" I've also tried mpm_worker with mpm_itk (recommended/required for one open-source package we use), and get numerous "[mpm_prefork:notice] [pid 1475] AH00163: Apache/2.4.7 (Ubuntu) mpm-itk/2.4.6-01 configured -- resuming normal operations." (I realize mpm_itk may be problematic.) apachectl -S gives me: VirtualHost configuration: [snipped -- all good] ServerRoot: "/etc/apache2" Main DocumentRoot: "/var/www" Main ErrorLog: "/var/log/apache2/error.log" Mutex default: dir="/var/lock/apache2" mechanism=fcntl Mutex mpm-accept: using_defaults Mutex watchdog-callback: using_defaults Mutex rewrite-map: using_defaults PidFile: "/var/run/apache2/apache2.pid" Define: DUMP_VHOSTS Define: DUMP_RUN_CFG Define: ENABLE_USR_LIB_CGI_BIN User: name="www-data" id=33 not_used Group: name="www-data" id=33 not_used but apache2 -S gives me: [Wed Jan 07 10:51:31.785510 2015] [core:warn] [pid 4783] AH00111: Config variable ${APACHE_LOCK_DIR} is not defined [Wed Jan 07 10:51:31.785542 2015] [core:warn] [pid 4783] AH00111: Config variable ${APACHE_PID_FILE} is not defined [Wed Jan 07 10:51:31.785550 2015] [core:warn] [pid 4783] AH00111: Config variable ${APACHE_RUN_USER} is not defined [Wed Jan 07 10:51:31.785553 2015] [core:warn] [pid 4783] AH00111: Config variable ${APACHE_RUN_GROUP} is not defined [Wed Jan 07 10:51:31.785562 2015] [core:warn] [pid 4783] AH00111: Config variable ${APACHE_LOG_DIR} is not defined [Wed Jan 07 10:51:31.786574 2015] [core:warn] [pid 4783] AH00111: Config variable ${APACHE_RUN_DIR} is not defined [Wed Jan 07 10:51:31.786825 2015] [core:warn] [pid 4783] AH00111: Config variable ${APACHE_LOG_DIR} is not defined [Wed Jan 07 10:51:31.786890 2015] [core:warn] [pid 4783] AH00111: Config variable ${APACHE_LOG_DIR} is not defined [Wed Jan 07 10:51:31.786897 2015] [core:warn] [pid 4783] AH00111: Config variable ${APACHE_LOG_DIR} is not defined AH00526: Syntax error on line 76 of /etc/apache2/apache2.conf: Invalid Mutex directory in argument file:${APACHE_LOCK_DIR} [N.B. line 76 of apache2.conf is "Mutex file:${APACHE_LOCK_DIR} default"] Thoughts? Where and how should these variables be defined? Many thanks -- Paul --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org