Spacedust's questions

我已将 CentOS 6.5 安装移至新服务器，但无法在新服务器上使用 chattr：

chattr: symbol lookup error: chattr: undefined symbol: set_com_err_gettext

如何解决这个问题？

我已经使用 MariaDB 10.0.8 在我的 PHP 5.4.26 服务器上启用了 mysqlnd。

我的 SQL 配置包含以下内容：

[mysqlnd]
character-set-server = utf8
collation-server = utf8_general_ci

没有启用 mysqlnd 时一切正常。自从启用它以来，所有特殊的波兰 UTF-8 字符都丢失了。

当我在 server.cnf 配置中禁用这两行时，一切都会再次正常运行。

由于我不喜欢 latin-1 编码并且我想保留 UTF-8 我有一个问题 mysqlnd 默认情况下是否获得 UTF-8 并且不需要这些选项？

我正在尝试向波兰最大的托管公司之一发送电子邮件，但他们的服务器拒绝接收带有消息的邮件：

TLS connect failed: error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3 alert bad record mac; connected to 89.161.199.168.
I'm not going to try again; this message has been in the queue too long.

我已经联系了这家公司并得到了回复：

“我们的验证表明服务器 mail.domainhere.pl 正在尝试通过 SSL/TLS 协议连接到我们的服务器。我们的服务器不支持这种形式的连接，但我想指出我们的服务器配置正确并且匹配当前RFC 标准。以下建立连接的方法对于服务器之间的通信是非标准的。

我在 CentOS 6.5 64 位上使用 Qmailtoaster。即使我不在邮件客户端中使用 SSL，也会发生这种情况！

我的 SMTP 配置示例：

    #!/bin/sh

QMAILDUID=`id -u qmaild`
NOFILESGID=`id -g qmaild`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
BLACKLIST=`cat /var/qmail/control/blacklists`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
RBLSMTPD="/usr/bin/rblsmtpd"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
RECORDIO="/usr/bin/recordio"

### MR -- incresing SOFTLIMITVAR if not enough (example: because 'login fail')
if [ `uname -m` = 'x86_64' ] ; then
        SOFTLIMITVAR="72000000"
else
        SOFTLIMITVAR="18000000"
fi

IP=0
PORT=25

### MR -- SSL must using SMTPS=1 and SSL=1 but non-SSL only SSL=0 (without SMTPS=0)
export SMTPAUTH="!" \
        SSL=0 \
        REQUIRE_AUTH=0 \
        FORCE_TLS=0 \
        DENY_TLS=0 \
        AUTH=1 \
        REQUIRE_AUTH=0 \
        ALLOW_INSECURE_AUTH=1

### MR -- spamhaus.org recommended for not using $RBLSMTPD $BLACKLIST entry before $SMTPD
exec /usr/bin/softlimit -m $SOFTLIMITVAR \
        /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
        -u "$QMAILDUID" -g "$NOFILESGID" $IP $PORT $RECORDIO \
        $SMTPD $VCHKPW /bin/true 2>&1

如何纠正这个？

我正在尝试在我的专用服务器上安装 Wordpress 安装。

复制了所有文件，但它显示内部服务器错误 500。

日志显示了这一点：

[Wed Nov 06 18:12:36 2013] [error] [client 62.21.61.63] FastCGI: comm with server "/home/rafal/domain.com/domain.com.0fake" aborted: error parsing headers: malformed header 'HTTP/1.0 302 Found'

我在 CentOS 6.4 64 位上使用来自 remi repo + php_fpm_event + Apache 2.2.23 + nginxproxy 1.5.6 的 PHP 5.4.21。

我已经在我的测试服务器上测试了相同的配置，它运行良好。那么怎么了？

我在 CentOS 6.4 64 位服务器上使用 MariaDB-server 10.0.4。

PHPMyAdmin 显示：libmysql - 10.0.4-MariaDB

虽然 phpinfo 显示：客户端 API 版本 5.3.12-MariaDB

为什么我有两个版本？如何将客户端 API 版本更改为 10.0.4 ？

我从 10.0.4 安装了 MariaDB-shared。

我的 PowerDNS DNS 服务器 3.3 无法解析 TXT 记录。

数据库如下所示：

PowerDNS 数据库

当我尝试挖掘我的服务器以获取 TXT 条目时，它们没有被显示：

[root@nowosci powerdns]# dig @ns1.nowosci.org private._domainkey.nowosci.org TXT

; <<>> DiG 9.9.3-rpz2+rl.13208.13-P2-RedHat-9.9.3-4.P2.el6 <<>> @ns1.nowosci.org private._domainkey.nowosci.org TXT
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58314
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 2800
;; QUESTION SECTION:
;private._domainkey.nowosci.org.        IN      TXT

;; AUTHORITY SECTION:
nowosci.org.            1800    IN      SOA     ns1.nowosci.org. admin.adminonline.gr. 2013092526 3600 1800 604800 1800

;; Query time: 9 msec
;; SERVER: 62.21.44.49#53(62.21.44.49)
;; WHEN: śro wrz 25 13:36:45 CEST 2013
;; MSG SIZE  rcvd: 119

和

[root@nowosci powerdns]# dig @ns1.nowosci.org nowosci.org TXT

; <<>> DiG 9.9.3-rpz2+rl.13208.13-P2-RedHat-9.9.3-4.P2.el6 <<>> @ns1.nowosci.org nowosci.org TXT
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3920
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 2800
;; QUESTION SECTION:
;nowosci.org.                   IN      TXT

;; AUTHORITY SECTION:
nowosci.org.            1800    IN      SOA     ns1.nowosci.org. admin.adminonline.gr. 2013092526 3600 1800 604800 1800

;; Query time: 3 msec
;; SERVER: 62.21.44.49#53(62.21.44.49)
;; WHEN: śro wrz 25 13:37:31 CEST 2013
;; MSG SIZE  rcvd: 100

如何解决这个问题？

我在我的网站 elixnews.com 上使用以下代码从以下位置删除 php 扩展：

RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d 
RewriteRule ^([^\.]+)$ $1.php [NC,L]

要从我的链接中删除 www 和 php 扩展名，但它不起作用：http ://elixnews.com/todays_news - 怎么了？

在我的服务器的控制面板中添加一个新域时，它比平时花费的时间要长得多。

CPU 在一个核心上显示 100% 使用率，而 strace 报告如下：

poll([{fd=7, events=POLLIN|POLLERR|POLLHUP}], 1, -64771072) = 1 ([{fd=7, revents=POLLIN}])
recvfrom(7, "OiJsb2NhbCI7fWk6NTQ0O2E6NTp7czo1"..., 8192, MSG_DONTWAIT, NULL, NULL) = 8192
poll([{fd=7, events=POLLIN|POLLERR|POLLHUP}], 1, -64771072) = 1 ([{fd=7, revents=POLLIN}])
recvfrom(7, "bm5hbWUiO3M6MjI6ImJhZHppZXdpYXJ6"..., 8192, MSG_DONTWAIT, NULL, NULL) = 8192
poll([{fd=7, events=POLLIN|POLLERR|POLLHUP}], 1, -64771072) = 1 ([{fd=7, revents=POLLIN}])
recvfrom(7, "IjtzOjExOiJ3ZWJtYWlscHJvZyI7czow"..., 8192, MSG_DONTWAIT, NULL, NULL) = 8192

可能是什么原因？

我的操作系统是 CentOS 5.9 64 位。尝试了不同的硬件和内核，但总是一样的......

我正在尝试从以下位置运行测试 phpinfo 页面：

/home/admin/testdomain.com

但它显示这样的错误：

Internal Server Error

Directory / is not owned by admin
suPHP 0.7.1

我的 /etc/suphp.conf 是这样的：

[global]
logfile=/var/log/httpd/suphp_log
loglevel=info
webserver_user=apache
docroot=/
env_path=/bin:/usr/bin
umask=0022
min_uid=500
min_gid=48

; Security options
allow_file_group_writeable=true
allow_file_others_writeable=false
allow_directory_group_writeable=true
allow_directory_others_writeable=false

;Check wheter script is within DOCUMENT_ROOT
check_vhost_docroot=false

;Send minor error messages to browser
errors_to_browser=true

[handlers]
;Handler for php-scripts
x-httpd-php="php:/usr/bin/php-cgi"
; x-httpd-php52="php:/usr/local/lxlabs/ext/php/bin/php_cgi"
x-httpd-php52="php:/usr/local/lxlabs/ext/php/etc/lxphpcgi.sh"

;Handler for CGI-scripts
x-suphp-cgi="execute:!self"

我想从以下位置获得第一个号码：

[root@nowosci /]# quota -u testclient
Ograniczenia dyskowe user testclient (uid 7798):
System plików   bloki miękki  twardy  pobł.   pliki miękki  twardy  pobł.
/dev/root  100256  51200000 51200000              34       0       0

所以它只会返回 100256

到目前为止，我去了这个：

quota -u testclient | grep -Eo '[0-9]{6,10}'                          
100256
51200000
51200000

我的 Apache 抛出 Internal Server Error 500 错误和如下日志：

> [Sun Apr 07 23:35:24 2013] [error] [client 124.162.30.45] (2)No such
> file or directory: FastCGI: failed to connect to server
> "/home/magda_00aa/sportxxx.pl/sportxxx.pl.0fake": socket file
> descriptor (1063) is larger than FD_SETSIZE (1024), you probably need
> to rebuild Apache with a larger FD_SETSIZE, referer:
> http://www.surf4web.com/surfing.php?id=haoduodeng2012

我在里面提高了 FD 限制：

cat /usr/include/bits/typesizes.h | grep FD
#define __FD_SETSIZE            65536

和

cat /usr/include/linux/posix_types.h | grep FD_SETSIZE
#undef __FD_SETSIZE
#define __FD_SETSIZE    65536
#define __FDSET_LONGS   (__FD_SETSIZE/__NFDBITS)

并且

/sbin/sysctl fs.file-max
fs.file-max = 512000

ulimit -n
1000000

但它没有帮助。如果超过 350 个虚拟主机，我的 Apache 仍然会崩溃：/

我在 CentOS 5.9 64 位 - 内核 3.0.65-1.el5.elrepo

我无法让我的 qmailtoaster 在 CentOS 5.9 64 位上工作：

[root@nowosci supervise]# qmailctl stat
authlib: up (pid 2653) 212 seconds
clamd: up (pid 2658) 212 seconds
imap4: up (pid 2663) 212 seconds
imap4-ssl: up (pid 2652) 212 seconds
pop3: up (pid 2667) 212 seconds
pop3-ssl: up (pid 2659) 212 seconds
send: up (pid 13957) 0 seconds
smtp: up (pid 2665) 212 seconds
spamd: up (pid 2655) 212 seconds
submission: up (pid 2643) 212 seconds
authlib/log: up (pid 2656) 212 seconds
clamd/log: up (pid 2666) 212 seconds
imap4/log: up (pid 2664) 212 seconds
imap4-ssl/log: up (pid 2654) 212 seconds
pop3/log: up (pid 2660) 212 seconds
pop3-ssl/log: up (pid 2657) 212 seconds
send/log: up (pid 2644) 212 seconds
smtp/log: up (pid 2661) 212 seconds
spamd/log: up (pid 2650) 212 seconds
submission/log: up (pid 2662) 212 seconds

发送已关闭。手动运行时我得到：

[root@nowosci send]# ./run
alert: cannot start: unable to switch to queue directory

这里有什么问题吗：

    [root@nowosci /]# ls -l /var/qmail/
razem 48K
drwxr-sr-x  2 alias  qmail 4,0K sty 22 17:26 alias
drwxr-xr-x  2 root   qmail 4,0K lut 18 23:57 bin
drwxr-xr-x  2 root   qmail 4,0K lut 18 23:56 boot
drwxr-xr-x  4 root   qmail 4,0K lut 18 23:57 control
drwxr-xr-x  2 root   qmail 4,0K lut 18 23:56 doc
drwxr-xr-x 10 root   qmail 4,0K lut 18 23:56 man
drwxr-xr-- 12 qmailq qmail 4,0K lut 18 23:56 queue
-rwxr-xr-x  1 root   qmail  215 sty 22 17:26 rc
drwxr-x---  3 clamav root  4,0K sty 22 17:28 simscan
drwxr-xr-x  3    201 qmail 4,0K lut  3 21:58 spamdyke
drwxr-xr-x 12 qmaill qmail 4,0K lut 18 23:57 supervise
drwxr-xr-x  2 root   qmail 4,0K lut 18 23:56 users

还是这里？

    [root@nowosci /]# ls -l /var/qmail/queue/
razem 40K
drwxr--r--  2 qmails qmail 4,0K sty 22 17:26 bounce
drwxr--r-- 25 qmails qmail 4,0K lut 18 23:56 info
drwxr--r--  2 qmailq qmail 4,0K lut 19 00:16 intd
drwxr--r-- 25 qmails qmail 4,0K lut 18 23:56 local
drwxr-xr--  2 qmailq qmail 4,0K lut 18 23:56 lock
drwxr-xr-- 25 qmailq qmail 4,0K lut 18 23:56 mess
drwxr--r--  2 qmailq qmail 4,0K lut 19 00:16 pid
drwxr--r-- 25 qmails qmail 4,0K lut 18 23:56 remote
drwxr-xr--  2 qmailq qmail 4,0K lut 19 00:16 todo
drwxr-xr-x  2 root   root  4,0K sty 28 15:19 yanked

我在我的服务器上使用 php_fpm_event，在执行 30 秒后进程被终止，我看到内部服务器错误。

但是我设置了更大的值：

[admin]
listen = 127.0.0.1:57797
listen.backlog = -1
listen.allowed_clients = 127.0.0.1
user = admin
group = admin
pm = dynamic
pm.max_children = 30
pm.start_servers = 2
pm.min_spare_servers = 2
pm.max_spare_servers = 6
pm.max_requests = 1000
;pm.status_path = /status
;ping.path = /ping
;ping.response = pong
request_terminate_timeout = 300s
request_slowlog_timeout = 300s
slowlog = /var/log/php-fpm/slow.log
rlimit_files = 1024
rlimit_core = 0
;chroot =
;chdir = /var/www
catch_workers_output = yes
security.limit_extensions = .php .php3 .php4 .php5

env[HOSTNAME] = $HOSTNAME
env[PATH] = /usr/local/bin:/usr/bin:/bin
env[TMP] = /tmp
env[TMPDIR] = /tmp
env[TEMP] = /tmp

;php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f [email protected]
;php_flag[display_errors] = off
php_admin_value[error_log] = /var/log/php-fpm/error.log
php_admin_value[session.save_path] = /var/lib/php/session
php_admin_flag[log_errors] = on
php_admin_value[memory_limit] = 256M

Phpinfo 确认 execution_time 为 300 秒。那么为什么会这样呢？

5 分钟后，我得到了这样的日志：

[17-Feb-2013 22:35:36] WARNING: [pool admin] child 7308, script '/home/admin/nowosci.org/td/odpal.php' (request: "GET /td/odpal.php") executing too slow (306.607536 sec), logging
[17-Feb-2013 22:35:44] WARNING: [pool admin] child 7308, script '/home/admin/nowosci.org/td/odpal.php' (request: "GET /td/odpal.php") execution timed out (313.981994 sec), terminating
[17-Feb-2013 22:35:44] WARNING: [pool admin] child 7308 exited on signal 15 (SIGTERM) after 679.176797 seconds from start

为什么它在 30 秒后显示内部服务器错误？

我正在使用带有客户独立池的 php-fpm。

有时页面冻结，然后显示 500 内部服务器错误，我在错误日志中收到此类错误：

[11-Feb-2013 22:12:39] ERROR: unable to read what child say: Bad file descriptor (9)
[11-Feb-2013 22:12:39] ERROR: unable to read what child say: Bad file descriptor (9)
[11-Feb-2013 22:12:42] WARNING: [pool oferty] child 31186 exited on signal 11 (SIGSEGV) after 198.250454 seconds from start

我当前的设置是：

    [admin]
listen = 127.0.0.1:51006
listen.backlog = -1
listen.allowed_clients = 127.0.0.1
user = admin
group = admin
pm = dynamic
pm.max_children = 10
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 2
pm.max_requests = 1000
;pm.status_path = /status
;ping.path = /ping
;ping.response = pong
request_terminate_timeout = 180s
request_slowlog_timeout = 180s
slowlog = /var/log/php-fpm/slow.log
rlimit_files = 1024
rlimit_core = 0
;chroot =
;chdir = /var/www
catch_workers_output = yes
security.limit_extensions = .php .php3 .php4 .php5

env[HOSTNAME] = $HOSTNAME
env[PATH] = /usr/local/bin:/usr/bin:/bin
env[TMP] = /tmp
env[TMPDIR] = /tmp
env[TEMP] = /tmp

;php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f [email protected]
;php_flag[display_errors] = off
php_admin_value[error_log] = /var/log/php-fpm/error.log
php_admin_value[session.save_path] = /var/lib/php/session
php_admin_flag[log_errors] = on
php_admin_value[memory_limit] = 128M

应该增加什么？我的服务器使用 Intel Core i7 2600 3.4 GHz（8 线程）+ 32 GB RAM，2xSSD 120 GB Software RAID1 + 2x HDD 3 TB Software RAID

我正在尝试从我的 aol.pl 帐户下载电子邮件，但它们被我本地邮件服务器上的 Spamdyke 阻止了。邮件似乎是从我不正确的电子邮件发送的，而不是在此本地服务器上。如何纠正这个？

[root@online /]# fetchmail -d0 -vk pop.aol.com
fetchmail: UWAGA: Uruchamianie jako root jest niezalecane.
fetchmail: 6.3.6 łączy się z pop.aol.com (protokół POP3) o godzinie sob 26 sty 2013 00:02:34 CET: odpytywanie rozpoczęte
Próba połączenia z 205.188.170.17/995...połączono.
fetchmail: Organizacja wystawcy: America Online Inc.
fetchmail: CommonName wystawcy: AOL Member CA
fetchmail: CommonName serwera: imap.aol.com
fetchmail: Subject Alternative Name: imap.aol.com
fetchmail: Subject Alternative Name: imap.aim.com
fetchmail: Subject Alternative Name: imap.cs.com
fetchmail: Subject Alternative Name: client.imap.aol.com
fetchmail: Subject Alternative Name: imap.au.aol.com
fetchmail: Subject Alternative Name: imap.ar.aol.com
fetchmail: Subject Alternative Name: imap.br.aol.com
fetchmail: Subject Alternative Name: imap.ca.aol.com
fetchmail: Subject Alternative Name: imap.cl.aol.com
fetchmail: Subject Alternative Name: imap.de.aol.com
fetchmail: Subject Alternative Name: imap.fr.aol.com
fetchmail: Subject Alternative Name: imap.in.aol.com
fetchmail: Subject Alternative Name: imap.jp.aol.com
fetchmail: Subject Alternative Name: imap.mx.aol.com
fetchmail: Subject Alternative Name: imap.uk.aol.com
fetchmail: Subject Alternative Name: pop.aol.com
fetchmail: Subject Alternative Name: pop.aim.com
fetchmail: Subject Alternative Name: pop.mcom.com
fetchmail: Subject Alternative Name: imap.mcom.com
fetchmail: Subject Alternative Name: pop.goowy.com
fetchmail: Subject Alternative Name: imap.goowy.com
fetchmail: Subject Alternative Name: imap.tunome.com
fetchmail: Subject Alternative Name: pop.tunome.com
fetchmail: Subject Alternative Name: imap.mda.aol.com
fetchmail: Subject Alternative Name: east.us.imap.aol.com
fetchmail: Subject Alternative Name: east.us.pop.aol.com
fetchmail: Subject Alternative Name: alf.imap.aol.com
fetchmail: Subject Alternative Name: imap.angeliamail.com
fetchmail: Subject Alternative Name: pop.angeliamail.com
fetchmail: Subject Alternative Name: imap.csi.com
fetchmail: Subject Alternative Name: pop.csi.com
fetchmail: Subject Alternative Name: nginx.aol.com
fetchmail: Subject Alternative Name: imap.about.me
fetchmail: Subject Alternative Name: pop.about.me
fetchmail: Odcisk klucza pop.aol.com: 8F:EA:FB:4F:81:F0:94:9E:A0:06:C3:74:0B:96:7F:3D
fetchmail: POP3< +OK POP3 ready
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< SASL LOGIN PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER [email protected]
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK server ready
fetchmail: POP3> STAT
fetchmail: POP3< +OK 1 3261
1 list dla [email protected] na pop.aol.com(3261 bajtów).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 3261
fetchmail: POP3> RETR 1
fetchmail: POP3< +OK message follows
pobieram list [email protected]@nginx.mx.aol.com.aol.akadns.net:1 z 1 (3261 bajtów)
Próba połączenia z 127.0.0.1/25...połączono.
fetchmail: SMTP< 220 mail.domain.pl - Welcome to Qmail ESMTP
fetchmail: SMTP> EHLO domain.pl
fetchmail: SMTP< 250-mail.domain.pl - Welcome to Qmail
fetchmail: SMTP< 250-STARTTLS
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250-8BITMIME
fetchmail: SMTP< 250-SIZE 268435456
fetchmail: SMTP< 250 AUTH LOGIN PLAIN CRAM-MD5
fetchmail: SMTP> MAIL FROM:<[email protected]> SIZE=3261
fetchmail: SMTP< 250 Refused. You have no reverse DNS entry.
fetchmail: SMTP> RCPT TO:<[email protected]>
fetchmail: SMTP< 421 Refused. You have no reverse DNS entry.
fetchmail: błąd SMTP: 421 Refused. You have no reverse DNS entry.
fetchmail: SMTP> RSET
fetchmail: SMTP< 554 Refused. You have no reverse DNS entry.
. nie został skasowany
fetchmail: POP3> QUIT
fetchmail: POP3< +OK core-doe004a.r1000.mail.aol.com closing connection
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 Refused. You have no reverse DNS entry.
fetchmail: 6.3.6 łączy się z pop.aol.com (protokół POP3) o godzinie sob 26 sty 2013 00:02:36 CET: odpytywanie zakończone
fetchmail: praca zakończona poprawnie, kod wyjścia 0

我遇到了这样的内核恐慌：

    EXT4-fs error (device md2): ext4_ext_find_extent: bad header/extent in inode #97911179: invalid magic - magic 5f69, entries 28769, max 26988(0), depth 24939(0)
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at fs/ext4/extents.c:1973
invalid opcode: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:00.0/irq
CPU 6
Modules linked in: iptable_filter ipt_REDIRECT ip_nat_ftp ip_conntrack_ftp iptable_nat ip_nat ip_tables xt_state ip_conntrack_netbios_ns ip_conntrack nfnetlink netconsole ipt_iprange xt_tcpudp autofs4 hwmon_vid coretemp cpufreq_ondemand acpi_cpufreq freq_table mperf x_tables be2iscsi ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp bnx2i cnic ipv6 xfrm_nalgo crypto_api uio cxgb3i libcxgbi cxgb3 8021q libiscsi_tcp libiscsi2 scsi_transport_iscsi2 scsi_transport_iscsi ext3 jbd dm_mirror dm_multipath scsi_dh video backlight sbs power_meter hwmon i2c_ec dell_wmi wmi button battery asus_acpi acpi_memhotplug ac lp joydev sg shpchp parport_pc parport r8169 mii serio_raw tpm_tis tpm tpm_bios i2c_i801 i2c_core pcspkr dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache raid10 raid456 xor raid0 sata_nv aacraid 3w_9xxx 3w_xxxx sata_sil sata_via ahci libata sd_mod scsi_mod raid1 ext4 jbd2 crc16 uhci_hcd ohci_hcd ehci_hcd
Pid: 9374, comm: httpd Not tainted 2.6.18-308.20.1.el5debug 0000001
RIP: 0010:[<ffffffff8806ccda>] [<ffffffff8806ccda>] :ext4:ext4_ext_put_in_cache+0x21/0x6a
RSP: 0018:ffff8101c2df7678 EFLAGS: 00010246
RAX: 00000000fffffbf1 RBX: ffff810758115dc8 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff810758115958
RBP: ffff810758115958 R08: 0000000000000002 R09: 0000000000000000
R10: ffff8101c2df75a0 R11: 0000000000000100 R12: 0000000000000000
R13: 0000000000000002 R14: 0000000000000000 R15: 0000000000000000
FS: 00002ab948d31f70(0000) GS:ffff81081f4ba4c8(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000001de9e4e0 CR3: 000000014ae88000 CR4: 00000000000006a0
Process httpd (pid: 9374, threadinfo ffff8101c2df6000, task ffff8101cdf74d80)
Stack: 000181070000040f ffff810758115dc8 ffff8103f15d7ff4 ffff8107581157f0
 ffff810758115958 000000000000040f 0000000000000000 ffffffff8806f621
 ffff8101c2df76d8 ffff8101c2df7738 0000000000000000 ffff81034900c310
Call Trace:
 [<ffffffff8806f621>] :ext4:ext4_ext_get_blocks+0x258/0x16f3
 [<ffffffff80013994>] poison_obj+0x26/0x2f
 [<ffffffff800331e2>] cache_free_debugcheck+0x20b/0x21a
 [<ffffffff8805b4ac>] :ext4:ext4_get_blocks+0x43/0x1d2
 [<ffffffff8805b4cf>] :ext4:ext4_get_blocks+0x66/0x1d2
 [<ffffffff8805c16a>] :ext4:ext4_get_block+0xa7/0xe6
 [<ffffffff8805c3be>] :ext4:ext4_block_truncate_page+0x215/0x4f1
 [<ffffffff8806e832>] :ext4:ext4_ext_truncate+0x65/0x909
 [<ffffffff8805b4f9>] :ext4:ext4_get_blocks+0x90/0x1d2
 [<ffffffff8805ccfc>] :ext4:ext4_truncate+0x91/0x53b
 [<ffffffff80041e5d>] pagevec_lookup+0x17/0x1e
 [<ffffffff8002d3cf>] truncate_inode_pages_range+0x1f3/0x2d5
 [<ffffffff8803b78b>] :jbd2:jbd2_journal_stop+0x1f1/0x201
 [<ffffffff8805f3c1>] :ext4:ext4_da_write_begin+0x1ea/0x25b
 [<ffffffff80010896>] generic_file_buffered_write+0x151/0x6c3
 [<ffffffff800174b1>] __generic_file_aio_write_nolock+0x36c/0x3b9
 [<ffffffff800482ab>] do_sock_read+0xcf/0x110
 [<ffffffff80022d49>] generic_file_aio_write+0x69/0xc5
 [<ffffffff88056c0a>] :ext4:ext4_file_write+0xcb/0x215
 [<ffffffff8001936b>] do_sync_write+0xc7/0x104
 [<ffffffff8000d418>] dnotify_parent+0x1f/0x7b
 [<ffffffff800efead>] do_readv_writev+0x26e/0x291
 [<ffffffff800a8192>] autoremove_wake_function+0x0/0x2e
 [<ffffffff80035b9f>] do_setitimer+0x62a/0x692
 [<ffffffff8002e6a5>] mntput_no_expire+0x19/0x8d
 [<ffffffff80049aa0>] sys_chdir+0x55/0x62
 [<ffffffff800178c6>] vfs_write+0xce/0x174
 [<ffffffff800181ba>] sys_write+0x45/0x6e
 [<ffffffff80060116>] system_call+0x7e/0x83


Code: 0f 0b 68 3e 27 08 88 c2 b5 07 eb fe 48 8d 9f 08 05 00 00 48
RIP [<ffffffff8806ccda>] :ext4:ext4_ext_put_in_cache+0x21/0x6a
 RSP <ffff8101c2df7678>
 <0>Kernel panic - not syncing: Fatal exception
 <0>Rebooting in 1 seconds..

我的系统是 CentOS 5.8 64 位。

/dev/md2        /home   ext4    rw,noatime,nodiratime,usrjquota=aquota.user,grpjquota=aquota.group,usrquota,grpquota,jqfmt=vfsv0     0       0

内核：2.6.18-308.20.1.el5debug

md2 : active raid1 sdc3[0] sdd3[1]
      2914280100 blocks super 1.0 [2/2] [UU]
      [>....................]  resync =  0.2% (7252288/2914280100) finish=13468.3min speed=3595K/sec

/dev/md2              2,7T  1,8T  908G  67% /home

我怎样才能解决这个问题 ？

即使重新同步我的阵列，卸载文件系统，然后检查并修复所有错误，它在大约一周的时间内一切正常，然后显示小的 ext4 错误，最后它开始内核恐慌。

我的服务器崩溃了，我找不到原因的答案。这一切都是在我的数据中心将 RAM 从 16 GB 升级到 32 GB 之后开始的。

我还在 dmesg 中找到了这样的日志——它们在第一次内核崩溃之前就开始显示了：

EXT4-fs error (device md2): ext4_ext_find_extent: bad header/extent in inode #97911179: invalid magic - magic 5f69, entries 28769, max 26988(0), depth 24939(0)
EXT4-fs error (device md2): ext4_ext_remove_space: bad header/extent in inode #97911179: invalid magic - magic 5f69, entries 28769, max 26988(0), depth 24939(0)
EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 20974: 8589 blocks in bitmap, 54896 in gd
JBD: Spotted dirty metadata buffer (dev = md2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
EXT4-fs error (device md2): ext4_ext_split: inode #97911179: (comm pdflush) eh_entries 28769 != eh_max 26988!
EXT4-fs (md2): delayed block allocation failed for inode 97911179 at logical offset 1039 with max blocks 1 with error -5

This should not happen!!  Data will be lost
EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 21731: 5 blocks in bitmap, 60762 in gd
JBD: Spotted dirty metadata buffer (dev = md2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.

我的系统是 CentOS 5.8 64 位，最新内核为 2.6.18-308.20.1.el5。如何在无法访问 KVM 的情况下检查内核恐慌的原因是什么？

我已经告诉我的数据中心管理员检查服务器中的内存。

我正在尝试使用以下命令导入 641 MB MySQL 数据库：

mysql -u root -p ddamiane_fakty < domenyin_damian_fakty.sql

但我得到一个错误：

ERROR 1064 (42000) at line 2351406: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '<br />
<b>Fatal error</b>:  Maximum execution time of 300 seconds exceeded in <b' at line 253

但是限制设置得更高：

mysql> show global variables like "interactive_timeout";
+---------------------+-------+
| Variable_name       | Value |
+---------------------+-------+
| interactive_timeout | 28800 |
+---------------------+-------+
1 row in set (0.00 sec)

和

mysql> show global variables like "wait_timeout";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| wait_timeout  | 28800 |
+---------------+-------+
1 row in set (0.00 sec)

我在使用 2000 个虚拟主机重新启动 Apache 时遇到了一些问题。

我在 CentOS 5.8 64 位上使用 Apache 2.2.22 + PHP 5.4.6。

当我尝试重新启动时，它显示：

    /etc/init.d/httpd restart
Stopping httpd:                                       [FAILED]
Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
                                                           [FAILED]

当我这样做killall -9 httpd时，一段时间后它又发生了：/

我在 dmesg 中收到这样的警告：

EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619328(bit 15808 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619329(bit 15809 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619330(bit 15810 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619331(bit 15811 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619332(bit 15812 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619333(bit 15813 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619334(bit 15814 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619335(bit 15815 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619336(bit 15816 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619337(bit 15817 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619338(bit 15818 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619339(bit 15819 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619340(bit 15820 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619341(bit 15821 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619342(bit 15822 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619343(bit 15823 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619344(bit 15824 in group
EXT4-fs error (device md2): mb_free_blocks: double-free of inode 0's block 602619767(bit 16247 in group
JBD: Spotted dirty metadata buffer (dev = md2, blocknr = 0). There's a risk of filesystem corruption in
EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group 18390: 7176 blocks in bitmap, 7211 in
JBD: Spotted dirty metadata buffer (dev = md2, blocknr = 0). There's a risk of filesystem corruption in

这只是在一段时间后发生的。服务器未重新启动。所有磁盘都很好。我在两个 3TB 驱动器上使用软件 RAID1 设置。我没有看到任何问题、不稳定或其他问题。

有一次我在夜间运行了 e4fsck。它纠正了所有 tje 错误，然后又开始发生，但服务器根本没有重新启动。

有什么可担心的吗？

核心：

2.6.18-308.4.1.el5 #1 SMP Tue Apr 17 17:08:00 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux