What writes to apps.vhost and breaks Apache

Discussion in 'ISPConfig 3 Priority Support' started by primesoftnz, May 3, 2021.

  1. till

    till Super Moderator Staff Member ISPConfig Developer

    Then you should just create a custom apps vhost file for your system as already mentioned. You do this by copying the file /usr/local/ispconfig/server/conf/apache_apps.vhost.master to /usr/local/ispconfig/server/conf-custom/apache_apps.vhost.master and then modify the copy.
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    I think it should be in /usr/local/ispconfig/server/conf-custom/install/apache_apps.vhost.master :)
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    @Thom: Actually we are both right, the file exists in the installer and the server :) @primesoftnz Please add a custom conf file in the location that thom mentioned plus in the location that ''ve mentioned.
  4. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    I am seeing this problem on a system, and have probably found the problem. Could you share your /etc/apache2/apache2.conf ?
  5. primesoftnz

    primesoftnz Member HowtoForge Supporter

    [email protected]:~# cat /etc/apache2/apache2.conf
    # This is the main Apache server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See http://httpd.apache.org/docs/2.4/ for detailed information about
    # the directives and /usr/share/doc/apache2/README.Debian about Debian specific
    # hints.
    # Summary of how the Apache 2 configuration works in Debian:
    # The Apache 2 web server configuration in Debian is quite different to
    # upstream's suggested way to configure the web server. This is because Debian's
    # default Apache2 installation attempts to make adding and removing modules,
    # virtual hosts, and extra configuration directives as flexible as possible, in
    # order to make automating the changes and administering the server as easy as
    # possible.

    # It is split into several files forming the configuration hierarchy outlined
    # below, all located in the /etc/apache2/ directory:
    # /etc/apache2/
    # |-- apache2.conf
    # | `-- ports.conf
    # |-- mods-enabled
    # | |-- *.load
    # | `-- *.conf
    # |-- conf-enabled
    # | `-- *.conf
    # `-- sites-enabled
    # `-- *.conf
    # * apache2.conf is the main configuration file (this file). It puts the pieces
    # together by including all remaining configuration files when starting up the
    # web server.
    # * ports.conf is always included from the main configuration file. It is
    # supposed to determine listening ports for incoming connections which can be
    # customized anytime.
    # * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
    # directories contain particular configuration snippets which manage modules,
    # global configuration fragments, or virtual host configurations,
    # respectively.
    # They are activated by symlinking available configuration files from their
    # respective *-available/ counterparts. These should be managed by using our
    # helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
    # their respective man pages for detailed information.
    # * The binary is called apache2. Due to the use of environment variables, in
    # the default configuration, apache2 needs to be started/stopped with
    # /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
    # work with the default configuration.

    # Global configuration

    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # NOTE! If you intend to place this on an NFS (or otherwise network)
    # mounted filesystem then please read the Mutex documentation (available
    # at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
    # you will save yourself a lot of trouble.
    # Do NOT add a slash at the end of the directory path.
    #ServerRoot "/etc/apache2"

    # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
    Mutex file:/var/lock/apache2 default

    # PidFile: The file in which the server should record its process
    # identification number when it starts.
    # This needs to be set in /etc/apache2/envvars
    PidFile /var/run/apache2/apache2.pid

    # Timeout: The number of seconds before receives and sends time out.
    Timeout 300

    # KeepAlive: Whether or not to allow persistent connections (more than
    # one request per connection). Set to "Off" to deactivate.
    KeepAlive On

    # MaxKeepAliveRequests: The maximum number of requests to allow
    # during a persistent connection. Set to 0 to allow an unlimited amount.
    # We recommend you leave this number high, for maximum performance.
    MaxKeepAliveRequests 100

    # KeepAliveTimeout: Number of seconds to wait for the next request from the
    # same client on the same connection.
    KeepAliveTimeout 5

    # These need to be set in /etc/apache2/envvars
    User www-data
    Group www-data

    # HostnameLookups: Log the names of clients or just their IP addresses
    # e.g., www.apache.org (on) or (off).
    # The default is off because it'd be overall better for the net if people
    # had to knowingly turn this feature on, since enabling it means that
    # each client request will result in AT LEAST one lookup request to the
    # nameserver.
    HostnameLookups Off

    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog /var/log/apache2/error.log

    # LogLevel: Control the severity of messages logged to the error_log.
    # Available values: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the log level for particular modules, e.g.
    # "LogLevel info ssl:warn"
    LogLevel warn

    # Include module configuration:
    IncludeOptional mods-enabled/*.load
    IncludeOptional mods-enabled/*.conf

    # Include list of ports to listen on
    Include ports.conf

    # Sets the default security model of the Apache2 HTTPD server. It does
    # not allow access to the root filesystem outside of /usr/share and /var/www.
    # The former is used by web applications packaged in Debian,
    # the latter may be used for local directories served by the web server. If
    # your system is serving content from a sub-directory in /srv you must allow
    # access here, or in any related virtual host.
    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Require all denied

    <Directory /usr/share>
    AllowOverride None
    Require all granted

    <Directory /var/www/>
    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted

    #<Directory /srv/>
    # Options Indexes FollowSymLinks
    # AllowOverride None
    # Require all granted

    # AccessFileName: The name of the file to look for in each directory
    # for additional configuration directives. See also the AllowOverride
    # directive.
    AccessFileName .htaccess

    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
    Require all denied

    # The following directives define some format nicknames for use with
    # a CustomLog directive.
    # These deviate from the Common Log Format definitions in that they use %O
    # (the actual bytes sent including headers) instead of %b (the size of the
    # requested file), because the latter makes it impossible to detect partial
    # requests.
    # Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
    # Use mod_remoteip instead.
    LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
    LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %O" common
    LogFormat "%{Referer}i -> %U" referer
    LogFormat "%{User-agent}i" agent

    # Include of directories ignores editors' and dpkg's backup files,
    # see README.Debian for details.

    # Include generic snippets of statements
    IncludeOptional conf-enabled/*.conf

    # Include the virtual host configurations:
    IncludeOptional sites-enabled/
    IncludeOptional sites-enabled/*.vhost

    # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
    [email protected]:~#
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Seems as if the include for sites-enabled has been added twice.

    IncludeOptional sites-enabled/
    IncludeOptional sites-enabled/*.vhost
    Change it to:

    IncludeOptional sites-enabled/
    ahrasis and primesoftnz like this.
  7. primesoftnz

    primesoftnz Member HowtoForge Supporter

    Yes that fixed it. Thank you, but now I have 10 updates stuck, seemingly created 2 each time I previously crashed apache


    Attached Files:

  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Check that you have not commented out server.sh in root crontab.
  9. primesoftnz

    primesoftnz Member HowtoForge Supporter

    I had but had manually run server.sh on all servers before I removed debug and edited crontab
    for the server showing the updates stuck I get

    10.05.2021-08:22 - DEBUG - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'.
    10.05.2021-08:22 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    finished server.php.

    I'm about to upgrade to latest Ispconfig version but wanted to get this sorted first
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    There are no pending updates for the server you ran server.sh on and posted the debug output. Just a guess, do you maybe have one server listed under system > services that does not exist anymore which has pending updates?
  11. primesoftnz

    primesoftnz Member HowtoForge Supporter

    None that I intend to not exist so I guess this is related to my other thread you are helping me with
    Your last suggestion to upgrade slave and choose to reconfigure permissions during update.
    Done that and all stuck update s have disappeared
    Last edited: May 10, 2021
  12. primesoftnz

    primesoftnz Member HowtoForge Supporter

    Opps I spoke too soon
    During update I got

    systemctl status apache2.service
    ● apache2.service - The Apache HTTP Server
    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Mon 2021-05-10 21:03:06 NZST; 20s ago
    Docs: https://httpd.apache.org/docs/2.4/
    Process: 21678 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

    Which I guess is no longer identifying apps.vhost as the culprit. Now ispconfig.vhost . and is now indicating that two services are listening on 8080 as opposed to 8081. Perhaps progress
    Last edited: May 10, 2021
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    Check apache2.conf if you have two includes again.
  14. primesoftnz

    primesoftnz Member HowtoForge Supporter

    That was the first thing I checked.

    /etc/apache2# grep -R 8080 *
    ports.conf:# NameVirtualHost *:8080
    ports.conf:Listen 8080
    sites-available/ispconfig.vhost:# Listen 8080
    sites-available/ispconfig.vhost:#NameVirtualHost *:8080
    sites-available/ispconfig.vhost:<VirtualHost _default_:8080>
    sites-enabled/000-ispconfig.vhost:# Listen 8080
    sites-enabled/000-ispconfig.vhost:#NameVirtualHost *:8080
    sites-enabled/000-ispconfig.vhost:<VirtualHost _default_:8080>

    Is ports.conf meant to define a listening port as well? btw I've edited ispconfg.conf and commented out the Listen 8080 to get apache to run
  15. till

    till Super Moderator Staff Member ISPConfig Developer

    The ispconfig port should not be defined in ports.conf, please remove it there.
  16. primesoftnz

    primesoftnz Member HowtoForge Supporter

    Yes that worked. Thank you

Share This Page