Page 1 of 1

Apache Config Notfall

Posted: Fri 21. Dec 2018, 20:58
by Tobi_BB21
Ich brauche mal ganz schnell bitte Hilfe.

Ich habe Zeug installiert und mit VirtualHost Einstellungen herumgespielt. Allerdings aus KeyHelp wieder entfernt. Alles lief gut. Nach Neustart erscheint nun überall die Apache Hilfeseite.

Dann jeman schnell sagen, das ich machen muss? Kann ja nur eine kurze Einstellung in den conf-files sein, die ich irgendwie überschrieben haben muss...

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 21:08
by ShortSnow
Hast du in /etc/apache2/ an den Dateien was verändert? Oder wo genau hast Du Einstellungen verändert?

Gruß Arne

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 21:24
by Tobi_BB21
Über KeyHelp die domainspez. Einstellungen.

Sieht so aus als nimmt der die Standard config Files anstatt die aus /etc/apache2/keyhelp

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 21:27
by OlliTheDarkness
Tobi_BB21 wrote: Fri 21. Dec 2018, 21:24 Über KeyHelp die domainspez. Einstellungen.

Sieht so aus als nimmt der die Standard config Files anstatt die aus /etc/apache2/keyhelp
Apache2 Config sollte so aussehn

/etc/apache2/apache2.conf

Code: Select all

# 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:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#

DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# 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 ${APACHE_PID_FILE}

#
# 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 ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (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 ${APACHE_LOG_DIR}/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>

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

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

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




# 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
</FilesMatch>


#
# 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/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

#Include KeyHelp vHosts
Include keyhelp/keyhelp.conf

Im Ordner sites-enabled sollte nicht´s drin sein.

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 21:31
by ShortSnow
Ok,

Du könntest das Versuchen:

- als root anmelden
-die Datei /etc/apache2/keyhelp/keyhelp.conf bearbeiten
-IncludeOptional keyhelp/vhosts/*.conf auskommentieren und speichern
-Apache2 neustarten: service apache2 restart

In Keyhelp das fehlerhafte wieder löschen und das include wieder zurückändern

Nur auf die schnelle. Könnte klappen.

Gruß Arne

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 21:38
by Tobi_BB21
Ok super, ich versuche es dann gleich und sage Bescheid!

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 21:39
by OlliTheDarkness
ShortSnow wrote: Fri 21. Dec 2018, 21:31 Ok,

Du könntest das Versuchen:

- als root anmelden
-die Datei /etc/apache2/keyhelp/keyhelp.conf bearbeiten
-IncludeOptional keyhelp/vhosts/*.conf auskommentieren und speichern
-Apache2 neustarten: service apache2 restart

In Keyhelp das fehlerhafte wieder löschen und das include wieder zurückändern

Nur auf die schnelle. Könnte klappen.

Gruß Arne
Er schreibt ja
Nach Neustart erscheint nun überall die Apache Hilfeseite
Das, so hört es sich für mich an, schließt die KeyHelp Panel Site mit ein was also auf ein vorgelagertes Problem in dem Fall die Apache Conf hinweißt.

Wir brauchen eindeutig mehr Info´s :D

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 23:10
by Tobi_BB21
Genau. Ich hatte vorher versucht Mastodon nach der Anleitung zu installieren: https://github.com/tootsuite/documentat ... n-guide.md

Ich bin dort bis PostgrSQL gekommen. Dann versuchte ich die Apache Einstellungen anzupassen. Das habe ich in Keyhelp aber rückgängig gemacht, weil die anderen Domains dann ein Ausrufezeichen bekaen. Nachdem es rückgängig gemacht wurde, funktionierte alles und alles war erreichbar!

Ich habe dann nur den Server rebootet, danach ging nix mehr.

Apache2 als service läuft nicht, status sagt, connection already in use...

D.h. die vorgenannten Sachen halfen nicht, die config-Datei sieht gut aus. Irgendein andere Service blockiert, so scheint es.

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 23:13
by Tobi_BB21

Code: Select all

-- Unit apache2.service has begun starting up.
Dec 21 23:11:09 hostnamereplacedwiththis apachectl[5597]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Dec 21 23:11:09 hostnamereplacedwiththis apachectl[5597]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:
Dec 21 23:11:09 hostnamereplacedwiththis apachectl[5597]: no listening sockets available, shutting down
Dec 21 23:11:09 hostnamereplacedwiththis apachectl[5597]: AH00015: Unable to open logs
Dec 21 23:11:09 hostnamereplacedwiththis apachectl[5597]: Action 'start' failed.
Dec 21 23:11:09 hostnamereplacedwiththis apachectl[5597]: The Apache error log may have more information.
Dec 21 23:11:09 hostnamereplacedwiththis systemd[1]: apache2.service: Control process exited, code=exited status=1
Dec 21 23:11:09 hostnamereplacedwiththis systemd[1]: apache2.service: Failed with result 'exit-code'.
Dec 21 23:11:09 hostnamereplacedwiththis systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit apache2.service has failed.

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 23:15
by Tobi_BB21
Irgendwie muss ich das rückgängig machen.

Re: Apache Config Notfall

Posted: Fri 21. Dec 2018, 23:18
by Tobi_BB21
Allerdings kann an an dem installierten Zeug auch nur begrenzt liegen, denn es funktionierte alles bevor ich neugestartet habe.

Re: Apache Config Notfall

Posted: Sat 22. Dec 2018, 00:03
by ShortSnow
Hi, das heißt du hast nginx installiert?

Mach mal bitte

systemctl stop nginx

Und dann starte apache2.

Evtl. ist es das

Gruß Arne

Re: Apache Config Notfall  [GELÖST]

Posted: Sat 22. Dec 2018, 00:22
by Tobi_BB21
Ja das war es. Dank super Hilfe über Teamviewer durch OlliTheDarkness gelöst.

Vielen lieben Dank allen! :)

Re: Apache Config Notfall

Posted: Sat 22. Dec 2018, 00:26
by OlliTheDarkness
Tobi_BB21 wrote: Sat 22. Dec 2018, 00:22 Ja das war es. Dank super Hilfe über Teamviewer durch OlliTheDarkness gelöst.

Vielen lieben Dank allen! :)
Kein Problem, gerne ;)

Neben Nginx kam noch dazu das er seine source.list zerlegt hat (wie auch immer er es geschaft hat)

Aber jetzt is wieder alles tuti , in diesem Sinne, Gute Nacht ZzZzZzZz 8-)

Re: Apache Config Notfall

Posted: Sat 22. Dec 2018, 00:30
by ShortSnow
Super, das freut mich.

Gruß Arne