* * *
Benvenuto! Effettua l'accesso oppure registrati.
Hai perso l'e-mail di attivazione?
19 Ottobre 2018, 15:56:58

Inserisci il nome utente, la password e la durata della sessione.

Links

ads

Benvenuto


Benvenuto su la Community CentOS-Italia.Org

La Community Italiana di Linux CentOS e' lieta di averti tra noi , CentOS-Italia.Org e' un risorsa di guide e forum dal principiante al sistemista senior.
Clicca qua per registrati ora

La registrazione e' gratuita e ti consente di avere pieno accesso alle risorse di CentOS-Italia.org , come uso della ricerca avanzata , le funzioni interattive del portale e visualizzare i links nei post.
Gli utenti registrati non visualizzano gli ads, quindi registrati subito se non l'hai gia fatto.

Lo staff di CentOS-Italia.Org cerca di rendere la community un posto piacevole e il piu' produttivo possibile, invitiamo quindi i nuovi utenti a leggere le regole base.
Per info o problemi di registrazione scrivere a centos (at) centos-italia.org .

Autore Topic: Failed to start The Apache HTTP Server  (Letto 1488 volte)

Offline LOGOS582

  • Newbie
  • *
  • Post: 15
    • Mostra profilo
Failed to start The Apache HTTP Server
« il: 24 Settembre 2018, 15:44:59 »
Ciao a tutti,
ho installato Apache e digitando IP-SERVER:80 restituiva la pagine di cortesia di Apache...tutto bene.
Volendo gestire i virtual host stavo seguendo questa guida:
Citazione
https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-centos-7
Seguita passo passo...ma al momento di ri-avviare Apache ottendo il messaggio sotto:


Codice: [Seleziona]
[root@localhost ~]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since lun 2018-09-24 15:37:55 CEST; 2min 30s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 1639 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
  Process: 1638 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 1638 (code=exited, status=1/FAILURE)

set 24 15:37:55 localhost.localdomain systemd[1]: Starting The Apache HTTP Server...
set 24 15:37:55 localhost.localdomain httpd[1638]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set t...his message
set 24 15:37:55 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
set 24 15:37:55 localhost.localdomain kill[1639]: kill: cannot find process ""
set 24 15:37:55 localhost.localdomain systemd[1]: httpd.service: control process exited, code=exited status=1
set 24 15:37:55 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.
set 24 15:37:55 localhost.localdomain systemd[1]: Unit httpd.service entered failed state.
set 24 15:37:55 localhost.localdomain systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@localhost ~]#

Offline LOGOS582

  • Newbie
  • *
  • Post: 15
    • Mostra profilo
Re:Failed to start The Apache HTTP Server
« Risposta #1 il: 24 Settembre 2018, 18:16:51 »
update:
ho tolto dal file:
Codice: [Seleziona]
/etc/httpd/conf/httpd.confla riga che avevo aggiunto in fondo:
Codice: [Seleziona]
IncludeOptional sites-enabled/*.confIl servizio ripartito
Ho modificato il file "hosts"del mio computer:
Codice: [Seleziona]
127.0.0.1   localhost
127.0.1.1   guest-desktop
server_ip_address example.com
server_ip_address example2.com

ottengo che digitando:
server_ip_address
oppure
http://example.com
oppure
http://example2.com
la pagina di cortesia di Apache, mentre dovrei ottenere il contenuto dei 2 siti che ho indicato
Dove mi sono perso ?
Grazie


Offline LonelyWolf

  • Moderator
  • Hero Member
  • *****
  • Post: 1325
    • Mostra profilo
    • Traversate dei laghi
Re:Failed to start The Apache HTTP Server
« Risposta #2 il: 25 Settembre 2018, 08:55:37 »
Per sapere cosa non va servirebbero i log, leggendo quello che hai scritto non possibile capire dove sta il problema.

La modifica al file hosts non permette di identificare i domini (eventualmente presenti), ma solo l'host che li (dovrebbe) ospitare.

Per tentativi:
i permessi file/cartelle che hai creato sono a posto?
I permessi sui file di configurazione sono a posto?

Offline LOGOS582

  • Newbie
  • *
  • Post: 15
    • Mostra profilo
Re:Failed to start The Apache HTTP Server
« Risposta #3 il: 25 Settembre 2018, 09:26:47 »
Buongiorno LonelyWolf
non riesco ad allegare dei files...
Che permessi dovrebbero avere i files/cartelle ?
Hai gentilmente una guida ben fatta su come impostare i virtualhosts in centos?
Quali log potrei allegare?

Grazie del prezioso supporto
Ciauu

Offline LOGOS582

  • Newbie
  • *
  • Post: 15
    • Mostra profilo
Re:Failed to start The Apache HTTP Server
« Risposta #4 il: 25 Settembre 2018, 09:33:30 »
Codice: [Seleziona]
#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned. 
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used.  If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/etc/httpd"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
Include conf.modules.d/*.conf

#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch. 
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User apache
Group apache

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin root@localhost

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80

#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
    AllowOverride none
    Require all denied
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/var/www/html"

#
# Relax access to content within /var/www.
#
<Directory "/var/www">
    AllowOverride None
    # Allow open access:
    Require all granted
</Directory>

# Further relax access to the default document root:
<Directory "/var/www/html">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
    Require all denied
</Files>

#
# 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 "logs/error_log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    #CustomLog "logs/access_log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    CustomLog "logs/access_log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"

</IfModule>

#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
</Directory>

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig /etc/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml
</IfModule>

#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default.  To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8

<IfModule mime_magic_module>
    #
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type.  The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #
    MIMEMagicFile conf/magic
</IfModule>

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on

# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf

Offline LOGOS582

  • Newbie
  • *
  • Post: 15
    • Mostra profilo
Re:Failed to start The Apache HTTP Server
« Risposta #5 il: 25 Settembre 2018, 09:34:22 »
Ti ho allegato il contenuto di httpd.conf
Chiedo ammenda ma il forum non mi permette di modificare il post precedente
Grazie

Offline LOGOS582

  • Newbie
  • *
  • Post: 15
    • Mostra profilo
Re:Failed to start The Apache HTTP Server
« Risposta #6 il: 25 Settembre 2018, 12:00:32 »
update:
da ulteriore verifiche ho scoperto che aggiungendo la stringa:
Codice: [Seleziona]
IncludeOptional sites-enabled/*.confal file httpd.conf, il servizio apache non parte
Chiaramente non sapendo dove sono i virtualhost senza quella stringa, i domini non funzionano
C' qualcosa che non capisco

Offline LonelyWolf

  • Moderator
  • Hero Member
  • *****
  • Post: 1325
    • Mostra profilo
    • Traversate dei laghi
Re:Failed to start The Apache HTTP Server
« Risposta #7 il: 25 Settembre 2018, 17:47:04 »
Ripeto, senza i log non si pu sapere dov' il problema, cerca nella cartella /var/log quello di apache e leggi cosa succede.
In base a quello che scrivi posso supporre che il problema sia dovuto ai permessi dei file di configurazione "sites-enabled/*.conf" o al percorso errato.

Offline LOGOS582

  • Newbie
  • *
  • Post: 15
    • Mostra profilo
Re:Failed to start The Apache HTTP Server
« Risposta #8 il: 25 Settembre 2018, 17:56:23 »
dopo aver passato tutto il pomeriggio, come scritto prima...il problema di fondo era data dall' inserimento della stringa nel file httpd.conf
che non faceva partire correttamente il servizio
Usando il comando:
Codice: [Seleziona]
sudo setenforce 0ho seguito il riavvio del servizio httpd che stavolta partita correttamente
adesso i virtualhost funzionano
Grazie

Offline LonelyWolf

  • Moderator
  • Hero Member
  • *****
  • Post: 1325
    • Mostra profilo
    • Traversate dei laghi
Re:Failed to start The Apache HTTP Server
« Risposta #9 il: 26 Settembre 2018, 08:31:26 »
Hai un problema di permessi/autorizzazioni di accesso ai file, non di riga nel file di configurazione.
Quel comando ha solo detto alla macchina di ignorare la cosa, inoltre al prossimo riavvio tutto torner com'era prima.

Offline LOGOS582

  • Newbie
  • *
  • Post: 15
    • Mostra profilo
Re:Failed to start The Apache HTTP Server
« Risposta #10 il: 26 Settembre 2018, 08:34:05 »
ok...allora faccio dei controlli pi approfonditi
Grazie per il supporto

 

Notizie

Per un veloce Download di CentOS 6 http://mi.mirror.garr.it/mirrors/CentOS/6.4/isos/ Per una ricerca veloce su google linux http://www.google.it/linux

Collegamenti

Posts Recenti

Utenti
Statistiche
  • Post in totale: 12947
  • Topic in totale: 2893
  • Online Oggi: 268
  • Massimi online: 536
  • (26 Luglio 2012, 11:06:17)
Utenti Online
Utenti: 0
Visitatori: 192
Totale: 192

Permessi

-no content-

ShoutBox!

Ultimo 5 Shout:

fzphoto

19 Febbraio 2018, 09:18:24
Ciao a tutti. Ho installato l'ultima versione di centos 7 per poter lavorare comodamente con DaVinci resolve 14. Solo che non riesco, ne a installare il programma Davinci, ne tanto meno, il driver nvidia per la scheda grafica geoforce 1080 ti. Sul web non trovo niente che mi aiuti. Premetto che sono

aner64

07 Febbraio 2018, 11:21:40
Buongiorno. Ho installato l'ultima versione di CENTOS7 aggiornata alla 7.0.4.1708. Ho bisogno di fare un restore di file da un filesystem reiserfs. CENTOS7 non ha reiserfs tra i FS e bisogna installarlo. Quando di cerca di installare kmod-reiserfs-0.0-2.el7.elrepo.x86_64.rpm escono errori per mancan
 

LonelyWolf

28 Dicembre 2017, 08:37:34
da ieri non vedo pi il css solo un problema mio?

inetryconydot

08 Settembre 2017, 07:44:23

inetryconydot

20 Maggio 2017, 10:00:13
Stromectol is used for treating infections caused by certain parasites. Stromectol is an anthelmintic. It works by killing sensitive parasites.
 
Stromectol as known as: Ivectin, Ivenox, Ivera, Ivergot, Ivermec, Ivermectina, Ivermectine, Ivermectinum, Ivert, Ivexterm, Kilox, Mectizan, Quan

Mostra ultimi 50