Skip to content

Config variables not defined error. #12

@kopepasah

Description

@kopepasah

After updating to PHP 5.5.8, started happening after I updated to PHP 5.5.8 when running ApacheBuddy on my Digital Ocean server (Ubuntu 12.04.3 x64).

########################################################################
# Apache Buddy v 0.3 ###################################################
########################################################################
Gathering information...
We are checking the service running on port 80
The process listening on port 80 is /usr/sbin/apache2
[Tue Feb 11 23:40:26.259005 2014] [core:warn] [pid 4664] AH00111: Config variable ${APACHE_LOCK_DIR} is not defined
[Tue Feb 11 23:40:26.259223 2014] [core:warn] [pid 4664] AH00111: Config variable ${APACHE_PID_FILE} is not defined
[Tue Feb 11 23:40:26.259399 2014] [core:warn] [pid 4664] AH00111: Config variable ${APACHE_RUN_USER} is not defined
[Tue Feb 11 23:40:26.259496 2014] [core:warn] [pid 4664] AH00111: Config variable ${APACHE_RUN_GROUP} is not defined
[Tue Feb 11 23:40:26.259588 2014] [core:warn] [pid 4664] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Tue Feb 11 23:40:26.268925 2014] [core:warn] [pid 4664] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Tue Feb 11 23:40:26.269286 2014] [core:warn] [pid 4664] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Tue Feb 11 23:40:26.269364 2014] [core:warn] [pid 4664] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
AH00526: Syntax error on line 74 of /etc/apache2/apache2.conf:
Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}
Use of uninitialized value $output[0] in pattern match (m//) at
    /tmp/apachebuddy/apachebuddy.pl line 373 (#1)
    (W uninitialized) An undefined value was used as if it were already
    defined.  It was interpreted as a "" or a 0, but maybe it was a mistake.
    To suppress this warning assign a defined value to your variables.

    To help you figure out what was undefined, perl will try to tell you the
    name of the variable (if any) that was undefined. In some cases it cannot
    do this, so it also tells you what operation you used the undefined value
    in.  Note, however, that perl optimizes your program and the operation
    displayed in the warning may not necessarily appear literally in your
    program.  For example, "that $foo" is usually optimized into "that "
    . $foo, and the warning will refer to the concatenation (.) operator,
    even though there is no . in your program.

The process running on port 80 is not Apache

Any idea what may be causing this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions