查看: 7618|回复: 11
收起左侧

[软件] centos7安装apache2.4无法启动

[复制链接]
eremiter
发表于 2016-7-27 20:50:53 | 显示全部楼层 |阅读模式
本帖最后由 eremiter 于 2016-8-1 14:44 编辑

是centos7自带rpm:httpd-2.4.6-40.el7.centos.x86_64.rpm包安装的。和以前的apache2.2很不一样

安装一个apache要放怎么多的目录,有好几个都不知有什么用

/run/httpd
/etc/logrotate.d/httpd
/etc/sysconfig/httpd
/etc/httpd
/var/log/httpd
/var/cache/httpd
/usr/sbin/httpd
/usr/lib64/httpd
/usr/share/httpd
/usr/libexec/initscripts/legacy-actions/httpd


[mw_shl_code=shell,true][root@localhost Packages]# ls | grep httpd
httpd-2.4.6-40.el7.centos.x86_64.rpm
httpd-devel-2.4.6-40.el7.centos.x86_64.rpm
httpd-manual-2.4.6-40.el7.centos.noarch.rpm
httpd-tools-2.4.6-40.el7.centos.x86_64.rpm
libmicrohttpd-0.9.33-2.el7.x86_64.rpm
[root@localhost Packages]# find / -name httpd
/run/httpd
/etc/logrotate.d/httpd
/etc/sysconfig/httpd
/etc/httpd
/var/log/httpd
/var/cache/httpd
/usr/sbin/httpd
/usr/lib64/httpd
/usr/share/httpd
/usr/libexec/initscripts/legacy-actions/httpd
[root@localhost Packages]# service httpd start
Redirecting to /bin/systemctl start  httpd.service
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
root@localhost Packages]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since 三 2016-07-27 20:43:21 CST; 31s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 4880 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
  Process: 4878 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=0/SUCCESS)
Main PID: 4878 (code=exited, status=0/SUCCESS)

7月 27 20:43:21 localhost.localdomain systemd[1]: Starting The Apache HTTP Server...
7月 27 20:43:21 localhost.localdomain httpd[4878]: httpd (pid 4592) already running
7月 27 20:43:21 localhost.localdomain kill[4880]: kill: cannot find process ""
7月 27 20:43:21 localhost.localdomain systemd[1]: httpd.service: control process exited, c...=1
7月 27 20:43:21 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.
7月 27 20:43:21 localhost.localdomain systemd[1]: Unit httpd.service entered failed state.
7月 27 20:43:21 localhost.localdomain systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.[/mw_shl_code]

httpd.conf配置如下

[mw_shl_code=shell,true][root@localhost conf]# vi httpd.conf
#
# 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[/mw_shl_code]

今天折腾了一下,好像没什么错,但运行http://192.168.0.116没反应,不知防火墙哪里开放端口

[root@localhost httpd]# cd /bin
[root@localhost bin]# systemctl start httpd.service
[root@localhost bin]# ps -A
  PID TTY          TIME CMD
    1 ?        00:00:02 systemd
    2 ?        00:00:00 kthreadd
    3 ?        00:00:00 ksoftirqd/0
    6 ?        00:00:00 kworker/u2:0
    7 ?        00:00:00 migration/0
    8 ?        00:00:00 rcu_bh
    9 ?        00:00:00 rcuob/0
   10 ?        00:00:00 rcu_sched
   11 ?        00:00:00 rcuos/0
   12 ?        00:00:00 watchdog/0
   13 ?        00:00:00 khelper
   14 ?        00:00:00 kdevtmpfs
   15 ?        00:00:00 netns
   16 ?        00:00:00 perf
   17 ?        00:00:00 writeback
   18 ?        00:00:00 kintegrityd
   19 ?        00:00:00 bioset
   20 ?        00:00:00 kblockd
   21 ?        00:00:00 md
   26 ?        00:00:00 khungtaskd
   27 ?        00:00:00 kswapd0
   28 ?        00:00:00 ksmd
   29 ?        00:00:00 khugepaged
   30 ?        00:00:00 fsnotify_mark
   31 ?        00:00:00 crypto
   39 ?        00:00:00 kthrotld
   40 ?        00:00:00 kworker/u2:1
   41 ?        00:00:00 kmpath_rdacd
   42 ?        00:00:00 kpsmoused
   43 ?        00:00:00 ipv6_addrconf
   63 ?        00:00:00 deferwq
   93 ?        00:00:00 kauditd
   94 ?        00:00:01 kworker/0:3
  258 ?        00:00:00 ata_sff
  263 ?        00:00:00 scsi_eh_0
  264 ?        00:00:00 scsi_tmf_0
  265 ?        00:00:00 scsi_eh_1
  266 ?        00:00:00 scsi_tmf_1
  349 ?        00:00:00 kdmflush
  350 ?        00:00:00 bioset
  359 ?        00:00:00 kdmflush
  360 ?        00:00:00 bioset
  375 ?        00:00:00 xfsalloc
  376 ?        00:00:00 xfs_mru_cache
  377 ?        00:00:00 xfs-buf/dm-0
  378 ?        00:00:00 xfs-data/dm-0
  379 ?        00:00:00 xfs-conv/dm-0
  380 ?        00:00:00 xfs-cil/dm-0
  381 ?        00:00:00 xfsaild/dm-0
  466 ?        00:00:00 systemd-journal
  491 ?        00:00:00 lvmetad
  496 ?        00:00:00 systemd-udevd
  497 ?        00:00:00 rpciod
  559 ?        00:00:00 xfs-buf/sda1
  560 ?        00:00:00 xfs-data/sda1
  561 ?        00:00:00 xfs-conv/sda1
  562 ?        00:00:00 xfs-cil/sda1
  563 ?        00:00:00 xfsaild/sda1
  587 ?        00:00:00 auditd
  596 ?        00:00:00 audispd
  599 ?        00:00:00 sedispatch
  611 ?        00:00:00 alsactl
  612 ?        00:00:00 smartd
  615 ?        00:00:00 dbus-daemon
  621 ?        00:00:00 ModemManager
  623 ?        00:00:00 abrtd
  625 ?        00:00:00 abrt-watch-log
  626 ?        00:00:00 lsmd
  628 ?        00:00:00 abrt-watch-log
  636 ?        00:00:00 chronyd
  637 ?        00:00:00 rsyslogd
  638 ?        00:00:00 systemd-logind
  642 ?        00:00:00 firewalld
  663 ?        00:00:00 gssproxy
  734 ?        00:00:00 NetworkManager
  819 ?        00:00:00 wpa_supplicant
  820 ?        00:00:00 polkitd
1308 ?        00:00:00 dhclient
1350 ?        00:00:00 tuned
1352 ?        00:00:00 sshd
1355 ?        00:00:00 cupsd
1368 ?        00:00:00 atd
1371 ?        00:00:00 crond
1388 tty1     00:00:00 agetty
1916 ?        00:00:00 master
1953 ?        00:00:00 pickup
1954 ?        00:00:00 qmgr
2532 ?        00:00:00 sshd
2536 pts/0    00:00:00 bash
2582 ?        00:00:00 kworker/0:2H
2599 ?        00:00:00 kworker/0:0H
2600 ?        00:00:00 kworker/0:1
2611 ?        00:00:00 kworker/0:0
2628 ?        00:00:00 httpd
2629 ?        00:00:00 httpd
2630 ?        00:00:00 httpd
2631 ?        00:00:00 httpd
2632 ?        00:00:00 httpd
2633 ?        00:00:00 httpd
2639 pts/0    00:00:00 ps
[root@localhost bin]# ps -A | grep httpd
2628 ?        00:00:00 httpd
2629 ?        00:00:00 httpd
2630 ?        00:00:00 httpd
2631 ?        00:00:00 httpd
2632 ?        00:00:00 httpd
2633 ?        00:00:00 httpd
[root@localhost bin]#
thelord
发表于 2016-7-29 11:40:40 | 显示全部楼层
httpd -t 可以检查配置文件是否有错误
海南仙岛
发表于 2016-7-30 02:52:44 | 显示全部楼层
service httpd start
看看错误信息.
一般都是 /etc/httpd/ 这个目录是配置信息目录 /usr/lib64/httpd 这个是安装目录

find / -name httpd.conf
看看都有哪些配置文件

其实服务器来说的话, centos6x 最好用,也最稳定 7x更新了太多内容,
海南仙岛
发表于 2016-7-30 03:02:52 | 显示全部楼层
本帖最后由 海南仙岛 于 2016-7-30 03:11 编辑

不好意思,刚才没看清楚你已经贴了启动错误报告, 我搜了一下, 好像网络上有人的解决方法是禁用 selinux
你看一看你的系统中是否安装并开启了selinux
$sudo vi /etc/selinux/config
修改成  SELINUX=disable 禁用SeLinux;
修改成  SELINUX=enforcing 使用SeLinux
海南仙岛
发表于 2016-7-30 03:25:55 | 显示全部楼层
你的配置文件是不是没贴完呀, 我印像中httpd.conf配置文件不止这些内容的呀.
eremiter
 楼主| 发表于 2016-8-1 14:30:13 | 显示全部楼层
thelord 发表于 2016-7-29 11:40
httpd -t 可以检查配置文件是否有错误

没有错误
eremiter
 楼主| 发表于 2016-8-1 14:30:40 | 显示全部楼层
海南仙岛 发表于 2016-7-30 02:52
service httpd start
看看错误信息.
一般都是 /etc/httpd/ 这个目录是配置信息目录 /usr/lib64/httpd 这 ...

已经是这样设置了,重启了,才来发贴了
eremiter
 楼主| 发表于 2016-8-1 14:31:14 | 显示全部楼层
海南仙岛 发表于 2016-7-30 03:25
你的配置文件是不是没贴完呀, 我印像中httpd.conf配置文件不止这些内容的呀.

linux的配置文件 和 windown 是有些不同,已经是完整的,354行
eremiter
 楼主| 发表于 2016-8-1 14:32:17 | 显示全部楼层
海南仙岛 发表于 2016-7-30 02:52
service httpd start
看看错误信息.
一般都是 /etc/httpd/ 这个目录是配置信息目录 /usr/lib64/httpd 这 ...

和你的目录一样

[root@localhost ~]# find / -name httpd.conf
/etc/httpd/conf/httpd.conf
/usr/lib/tmpfiles.d/httpd.conf
eremiter
 楼主| 发表于 2016-8-1 14:53:01 | 显示全部楼层
谢谢各位,也不知我动了什么,最后查看了端口,加一个端口就行了  iptables -I INPUT -p tcp --dport 80 -j ACCEPT

但错误的提示,我好像也没做什么,今天就没有了,现在可以访问了
您需要登录后才可以回帖 登录 | 快速注册

本版积分规则

手机版|杀毒软件|软件论坛| 卡饭论坛

Copyright © KaFan  KaFan.cn All Rights Reserved.

Powered by Discuz! X3.4( 沪ICP备2020031077号-2 ) GMT+8, 2025-1-31 02:18 , Processed in 0.132754 second(s), 16 queries .

卡饭网所发布的一切软件、样本、工具、文章等仅限用于学习和研究,不得将上述内容用于商业或者其他非法用途,否则产生的一切后果自负,本站信息来自网络,版权争议问题与本站无关,您必须在下载后的24小时之内从您的电脑中彻底删除上述信息,如有问题请通过邮件与我们联系。

快速回复 客服 返回顶部 返回列表