U-NAS OS 系统故障之，WEB控制管理界面网页登录页面无法显示进入解决方法

摘要：WEB控制界面网页登录页面无法打开导致管理页面进不去，SSH、FTP、SMB共享都能打开。数据还能访问。...

故障描述：

前几日闲来无事，自己生事要给nas系统升级。在线升级，完成后头一次重启web登录还能打开。过一会儿就挂了。

WEB控制界面网页登录页面无法打开导致管理页面进不去，SSH、FTP、SMB共享都能打开。数据还能访问

问题说明：

web 登录不了，如果数据还能访问，一般是2种可能：

1、系统盘撑爆：

SSH登录，使用命令 df -h 看看输出中那个 / 对应的使用百分比，如果达到 / 接近100%,说明系统盘被撑爆了。需要找找哪个目录里有大量数据，一般 /var 和 /tmp 需要好好看看

使用 du -h --max-depth=1 命令可查看目录硬盘使用占比情况

root@U-NAS:/# du -h --max-depth=1
16K     ./lost+found
4.0K    ./home
1.4G    ./usr
14M     ./sbin
4.0K    ./lib64
48K     ./mnt
470M    ./root
4.0K    ./opt
44M     ./unas
36M     ./boot
7.7M    ./etc
9.3M    ./bin
12K     ./srv
0       ./dev
6.0M    ./run
8.0K    ./media
32K     ./tmp
0       ./proc
0       ./sys
236M    ./lib
186M    ./var
2.4G    .

root@U-NAS:/# du -h --max-depth=1 /root
8.0K    /root/.cache
48K     /root/.local
172M    /root/libtorrent-rasterbar-1.1.11
243M    /root/qBittorrent-release-4.1.8
28M     /root/rrshareweb
24K     /root/.config
4.0K    /root/.nano
470M    /root

2、apache的配置文件被修改，有问题

ssh登录，使用命令 service apache2 status 看看是否有报错，有的话，一般会说明那个文件的哪一行有问题。打开那个文件看看对应的行是否有问题。

正常回显

root@U-NAS:~# service apache2 status
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset:
enabled)
   Active: active (running) since Sun 2020-05-03 16:08:31 CST; 44min
ago
  Process: 1059 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCE
SS)
 Main PID: 1405 (apache2)
    Tasks: 6 (limit: 19660)
   Memory: 23.0M
      CPU: 263ms
   CGroup: /system.slice/apache2.service
           ├─1405 /usr/sbin/apache2 -k start
           ├─1436 /usr/sbin/apache2 -k start
           ├─1437 /usr/sbin/apache2 -k start
           ├─1452 /usr/sbin/apache2 -k start
           ├─1455 /usr/sbin/apache2 -k start
           └─1461 /usr/sbin/apache2 -k start

May 03 16:08:30 U-NAS systemd[1]: Starting The Apache HTTP Server...
May 03 16:08:31 U-NAS systemd[1]: Started The Apache HTTP Server.
root@U-NAS:~#

查看 cat /etc/apache2/apache2.conf 配置文件

root@U-NAS:~# 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:${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 webdav.conf
root@U-NAS:~#

---------------------------------- THE END ----------------------------------

故障描述：

问题说明：

1、系统盘撑爆：

2、apache的配置文件被修改，有问题

随机新闻