• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

Hostname Fehler

S

ShiftyTCS

Guten morgen,

kann mir jemand bei diesem Problem helfen ?

Code: 
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message

Verstehe nicht wie man den hostnamen ändern soll, hatte das damals schon gemacht und immer ein Fehler bekommen:

Code: 
** server can't find nagios.***-******.net: NXDOMAIN


Beste grüße,
Shifty
 
OP
S

ShiftyTCS

Jau, nur leider weiß ich nicht wo da genau, benutze ubuntu 14.04 LTS. Es gibt keine httpd.conf mehr dafür die apache.conf
Die sieht so aus:

Code: 
# 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

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

                                    # 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

:???:
 
M

marce

Schon mal nach der Direktive gegreppt?

Schon mal versucht, sie einzutragen?

Wo es bei Dir am sinnvollsten ist - solltest Du wissen, schließlich administrierst Du das System ja und weißt, wo Du so Deine Eintragungen für Domains, VirtualServer und so machst...
 
OP
S

ShiftyTCS

Okey ich komme absolut nicht weiter.

habe meine /etc/hosts/ so angepasst:

Code: 
127.0.0.1       localhost
127.0.1.1       nagios
192.168.100.32  nagios.***-*******.net nagios

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

und /etc/hostname/ so:

Code: 
nagios


Leider funktioniert das ganze immer noch nicht. Bei dem befehel nslookup 192.168.100.32 bekomme ich folgende ausgabe:

Code: 
root@nagios:/usr/local/nagios/var# nslookup 192.168.100.32
Server:		127.0.1.1
Address:	127.0.1.1#53

** server can't find 32.100.168.192.in-addr.arpa: SERVFAIL


bei nslookup nagios.***-********.net bekomme ich folgende fehlermeldung:

Code: 
root@nagios:/usr/local/nagios/var# nslookup nagios.***-**********.net
Server:		127.0.1.1
Address:	127.0.1.1#53

** server can't find nagios.***-*******.net: NXDOMAIN


Beste Grüße,
Shifty
 
M

marce

Ähm, sorry, aber das eine hat mit dem anderen nichts zu tun.

-> Die Meldung vom Apache -> Behebung in der Apache-Konfig.

alles andere (nagios.xxx.xxx soll aufgelöst werden können) - bedingt einen DNS-Server, auf dem das eingerichtet werden muss. Einfach in die /etc/hosts eingtragen funktioniet für Tools wie nslookup nicht.
 
OP
S

ShiftyTCS

aber der nagios.***-******.net soll nicht als dns server dienen, er ist sozusagen nur ein dns client von unseren anderen dns servern.
Oder muss man dann auf dem Ubuntu auch noch n DNS server einrichten oO ? :???:
 
M

marce

Nein. Aber Du musst den Eintrag im DNS-Server machen.

Ein wenig merkwürdig ist diesbezüglich ist, daß der Server bei sich selbst nachfragt - da scheint die /etc/resolv.conf nicht zu passen.
 
OP
S

ShiftyTCS

Danke für deine Antworten!
In meiner resolv.conf steht folgendes eingetragen:

Code: 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1
search ***-*******.net
 
M

marce

naja, nach Deinen Aussagen passt das nicht :)

Was da wirklich rein muss (oder ob Du vielleicht doch einen DNS-Server auf dem Ding selbst installieren willst und den sauber konfigurieren) - muss Dir wohl jemand anders sagen...
 
Geier0815

Geier0815

127.0.1.1 ist eine loopback Adresse, von daher verweist er zur Namensauflösung auf sich selbst. Trage mal per yast den richtigen DNS ein. Der sollte dann auch in der reolv.conf auftauchen. Dann den nagios im richtigen DNS eintragen und dann sollte das klappen. Zusätzlich solltest Du den loopbackeintrag in der /etc/hosts raus nehmen. Danach sollte jeder andere Rechner im Netz den Namen richtig auflösen und dein Server darauf auch reagieren. Kannste am Besten mit "ping NAME" testen.
 
OP
S

ShiftyTCS

Danke, hat sich gerade erledigt :) Hab einfach im Firefox ein paar Proxy einstellungen vorgenommen. Der squid hat mich drauf hingeweisen unter der Apache meldung : :eek:ps:
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Oben