作为部署前的一个测试平台，我正在运行带有双 Xeon E5-2620v4 和 64GB RAM 的 Supermicro X10DRL-i。我在 16x 插槽中有一个蓝宝石 AMD Vega56。
我今天运行了一些压力测试来检查系统稳定性，我在 Win10 上遇到了 Furmark 的问题，GPU 通过并应用了轻微的超频。系统似乎运行良好，但偶尔，主板会快速连续发出 4 声哔哔声，类似于进行基于 IPMI 的重置时的哔哔声模式。
我似乎在 Windows 或 IPMI 事件日志中找不到任何错误，而且系统看起来很稳定，即使是那些哔哔声。关闭 Furmark 压力测试阻止了那些哔哔声的发生，但它甚至可能导致类似的事情似乎很奇怪。
任何人有任何见解？
我一直在尝试让 fail2ban 与 Xeams 电子邮件垃圾邮件过滤器一起使用。但是，我无法弄清楚我应该使用什么可能的正则表达式来匹配日志。日志采用这种格式。
61.240.144.65 1451702136946 5
185.130.5.240 1451702444872 5
192.237.159.38 1451705774912 5
185.130.5.240 1451712868825 5
日志的每一部分都由一个 Tab 分隔（我认为），第一部分是主机 IP。我不知道其他部分是做什么的。
我尝试了以下正则表达式，但根据 fail2ban-regex 它不起作用。
<HOST> 1451.* .*
也：
<HOST> .* .*
老实说，我不知道如何匹配这些日志。
我正在运行安装了 Apache 的 Ubuntu 14.04 LTS 服务器。我设置了 3 个虚拟主机，还有另一个默认服务器来捕获所有其他未处理的请求。默认服务器的文档根目录为 /var/www/。其他 3 个虚拟主机的文档根目录为 /var/www/html/.../。
我在各自的域名上启用了所有三个虚拟主机，此时仅可用于本地访问以进行测试。但是，每当我尝试访问三个虚拟主机之一时，我都会立即启动到默认服务器的文档根目录。
这是其中一个虚拟主机的配置，其他的几乎相同，除了一些显然必须更改的字段（文档根目录、服务器名称）。我已经替换了服务器名称和文档根目录，但两者都是合法的并且存在于服务器上，如果这很重要的话。
<VirtualHost [example.com]>
DocumentRoot "/var/www/html/[Directory]“
<Directory "/var/www/html/[Directory]“>
allow from all
Options None
Require all granted
</Directory>
ServerName [example.com]
</VirtualHost>
这是 default-ssl.conf 文件。
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on
# A self-signed (snakeoil) certificate can be created by installing
# the ssl-cert package. See
# /usr/share/doc/apache2/README.Debian.gz for more info.
# If both key and certificate are stored in the same file, only the
# SSLCertificateFile directive is needed.
SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem
SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
# Server Certificate Chain:
# Point SSLCertificateChainFile at a file containing the
# concatenation of PEM encoded CA certificates which form the
# certificate chain for the server certificate. Alternatively
# the referenced file can be the same as SSLCertificateFile
# when the CA certificates are directly appended to the server
# certificate for convinience.
#SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt
# Certificate Authority (CA):
# Set the CA certificate verification path where to find CA
# certificates for client authentication or alternatively one
# huge file containing all of them (file must be PEM encoded)
# Note: Inside SSLCACertificatePath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCACertificatePath /etc/ssl/certs/
#SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt
# Certificate Revocation Lists (CRL):
# Set the CA revocation path where to find CA CRLs for client
# authentication or alternatively one huge file containing all
# of them (file must be PEM encoded)
# Note: Inside SSLCARevocationPath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCARevocationPath /etc/apache2/ssl.crl/
#SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl
# Client Authentication (Type):
# Client certificate verification type and depth. Types are
# none, optional, require and optional_no_ca. Depth is a
# number which specifies how deeply to verify the certificate
# issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth 10
# SSL Engine Options:
# Set various options for the SSL engine.
# o FakeBasicAuth:
# Translate the client X.509 into a Basic Authorisation. This means that
# the standard Auth/DBMAuth methods can be used for access control. The
# user name is the `one line' version of the client's X.509 certificate.
# Note that no password is obtained from the user. Every entry in the user
# file needs this password: `xxj31ZMTZzkVA'.
# o ExportCertData:
# This exports two additional environment variables: SSL_CLIENT_CERT and
# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
# server (always existing) and the client (only existing when client
# authentication is used). This can be used to import the certificates
# into CGI scripts.
# o StdEnvVars:
# This exports the standard SSL/TLS related `SSL_*' environment variables.
# Per default this exportation is switched off for performance reasons,
# because the extraction step is an expensive operation and is usually
# useless for serving static content. So one usually enables the
# exportation for CGI and SSI requests only.
# o OptRenegotiate:
# This enables optimized SSL connection renegotiation handling when SSL
# directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
<Directory /usr/lib/cgi-bin>
SSLOptions +StdEnvVars
</Directory>
# SSL Protocol Adjustments:
# The safe and default but still SSL/TLS standard compliant shutdown
# approach is that mod_ssl sends the close notify alert but doesn't wait for
# the close notify alert from client. When you need a different shutdown
# approach you can use one of the following variables:
# o ssl-unclean-shutdown:
# This forces an unclean shutdown when the connection is closed, i.e. no
# SSL close notify alert is send or allowed to received. This violates
# the SSL/TLS standard but is needed for some brain-dead browsers. Use
# this when you receive I/O errors because of the standard approach where
# mod_ssl sends the close notify alert.
# o ssl-accurate-shutdown:
# This forces an accurate shutdown when the connection is closed, i.e. a
# SSL close notify alert is send and mod_ssl waits for the close notify
# alert of the client. This is 100% SSL/TLS standard compliant, but in
# practice often causes hanging connections with brain-dead browsers. Use
# this only for browsers where you know that their SSL implementation
# works correctly.
# Notice: Most problems of broken clients are also related to the HTTP
# keep-alive facility, so you usually additionally want to disable
# keep-alive for those clients, too. Use variable "nokeepalive" for this.
# Similarly, one has to force some clients to use HTTP/1.0 to workaround
# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
# "force-response-1.0" for this.
BrowserMatch "MSIE [2-6]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# MSIE 7 and newer should be able to use keepalive
BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown
</VirtualHost>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
这是 000-default.conf。我不知道为什么除了这条线之外什么都没有显示。
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
如何让虚拟主机在访问时显示正确的目录？如果有任何区别，我将在 Ubuntu Server 14.04 LTS 上通过 Webmin 1.750 管理 Apache 服务器
我在某处读到需要为默认服务器指定服务器名称，否则它将捕获所有请求，因为它是列表中的第一个服务器。这是真的？如果是这样，我该怎么做？