WordPress 网站运行几分钟后,网站出现故障,并出现数百个“无法为池分配内存”错误

WordPress 网站运行几分钟后,网站出现故障,并出现数百个“无法为池分配内存”错误

我正在迁移一台机器,并已迁移了几个流量最小的 WordPress 网站(最大的网站每天有大约 200 个独立用户)。一切似乎都运行良好,但过了一会儿,我再次加载它时,浏览器中显示“未收到数据”。打开 PHP 警告/错误消息后,我看到数百条“无法为池分配内存”消息。如果我重新启动 Apache,网站会再次运行一段时间,然后再次停止。

有几件事对我来说毫无意义:

  • Apache 重启解决问题
  • 同一服务器上的另一个 WordPress 网站在另一个网站出现问题时继续正常运行
  • 当前 php.ini 分配的内存比旧版本多(我移走了一些更改,但将内存等项目保留为默认值,即 128 MB 左右,在旧服务器上是 16 MB)
  • 在寻求帮助时,我看到了对 APC 的引用,但我没有看到任何证据表明这里使用了 APC
  • 我尝试禁用所有插件,但没有变化。

背景是,这次迁移是 Apache 版本从 1.x 到 2.x 的转变,但对于 PHP 版本来说只是相对较小的变化。

我不知道现在该怎么办。

请帮助?

昆西

这是我的 PHP.ini,希望它有帮助(注释被删除以适合帖子长度):

[PHP]

engine = On
short_open_tag = On
asp_tags = Off
precision = 14
y2k_compliance = On
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = 100
allow_call_time_pass_reference = On
safe_mode = Off
safe_mode_gid = Off
safe_mode_include_dir =
safe_mode_exec_dir =
safe_mode_allowed_env_vars = PHP_
safe_mode_protected_env_vars = LD_LIBRARY_PATH
disable_functions =
disable_classes =
expose_php = On
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = Off
error_log = /var/log/php.log
variables_order = "GPCS"
request_order = "GP"
register_globals = On
register_long_arrays = On
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 10M
magic_quotes_gpc = Off
magic_quotes_runtime = Off
magic_quotes_sybase = Off
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
doc_root =
user_dir =
enable_dl = On
file_uploads = On
upload_max_filesize = 10M
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[Date]
[filter]
[iconv]
[intl]
[sqlite]
[sqlite3]
[Pcre]
[Pdo]
[Phar]
[Syslog]
define_syslog_variables  = Off
[mail function]
SMTP = localhost
smtp_port = 25
sendmail_path = /usr/sbin/sendmail -t -i
mail.add_x_header = On
[SQL]
sql.safe_mode = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[MySQL]
mysql.allow_persistent = On
mysql.max_persistent = -1
mysql.max_links = -1
mysql.default_port =
mysql.default_socket =
mysql.default_host =
mysql.default_user =
mysql.default_password =
mysql.connect_timeout = 60
mysql.trace_mode = Off
[MySQLi]
mysqli.max_links = -1
mysqli.default_port = 3306
mysqli.default_socket =
mysqli.default_host =
mysqli.default_user =
mysqli.default_pw =
mysqli.reconnect = Off
[PostgresSQL]
pgsql.allow_persistent = On
pgsql.auto_reset_persistent = Off
pgsql.max_persistent = -1
pgsql.max_links = -1
pgsql.ignore_notice = 0
pgsql.log_notice = 0
[Sybase-CT]
sybct.allow_persistent = On
sybct.max_persistent = -1
sybct.max_links = -1
sybct.min_server_severity = 10
sybct.min_client_severity = 10
[bcmath]
bcmath.scale = 0
[browscap]
[Session]
session.save_handler = files
session.save_path = "/var/lib/php/session"
session.use_cookies = 1
session.use_only_cookies = 1
session.name = PHPSESSID
session.auto_start = 0
session.cookie_lifetime = 0
session.cookie_path = /
session.cookie_domain =
uch as JavaScript.
session.cookie_httponly =
session.serialize_handler = php
session.gc_probability = 1
session.gc_divisor = 1000
session.gc_maxlifetime = 1440
session.bug_compat_42 = Off
session.bug_compat_warn = Off
session.referer_check =
session.entropy_length = 0
session.entropy_file =
session.cache_limiter = nocache
session.cache_expire = 180
session.use_trans_sid = 0
session.hash_function = 0
session.hash_bits_per_character = 5
url_rewriter.tags = "a=href,area=href,frame=src,input=src,form=fakeentry"
[MSSQL]
mssql.allow_persistent = On
mssql.max_persistent = -1
mssql.max_links = -1
mssql.min_error_severity = 10
mssql.min_message_severity = 10
mssql.compatability_mode = Off
mssql.secure_connection = Off
[Assertion]
[COM]
[mbstring]
[gd]
[exif]
[Tidy]
tidy.clean_output = Off
[soap]
soap.wsdl_cache_enabled=1
soap.wsdl_cache_dir="/tmp"
soap.wsdl_cache_ttl=86400
[sysvshm]

apc.ini(安装时的默认设置)。我并没有刻意使用 APC,但 WordPress 也许会使用它(删除注释):

extension = apc.so
apc.enabled=1
apc.shm_segments=1
apc.shm_size=64M
apc.num_files_hint=1024
apc.user_entries_hint=4096
apc.ttl=7200
apc.use_request_time=1
apc.user_ttl=7200
apc.gc_ttl=3600
apc.cache_by_default=1
apc.filters
apc.mmap_file_mask=/tmp/apc.XXXXXX
apc.file_update_protection=2
apc.enable_cli=0
apc.max_file_size=1M
apc.stat=1
apc.stat_ctime=0
apc.canonicalize=0
apc.write_lock=1
apc.report_autofilter=0
apc.rfc1867=0
apc.rfc1867_prefix =upload_
apc.rfc1867_name=APC_UPLOAD_PROGRESS
apc.rfc1867_freq=0
apc.rfc1867_ttl=3600
apc.include_once_override=0
apc.lazy_classes=0
apc.lazy_functions=0
apc.coredump_unmap=0
apc.file_md5=0
apc.preload_path

答案1

打开 PHP 警告/错误消息

这应该已经打开了——我假设 php.ini 文件是您打开了错误日志记录。

我没有看到任何证据表明这里使用了 APC/我没有有意识地使用 APC

这个答案相当模糊。你应该知道如何确定。说真的。

如果您运行 Wordpress,那么某种操作码缓存就非常重要。

APC 附带了一个非常有用的脚本(apc.php,可通过http://example.com/php-apc/在我的盒子上),它报告了许多有用的信息,包括配置 + 当前正在使用的缓存量 + 它被什么使用。后一个事实相当重要 - Wordpress 速度非常慢,有很多插件试图加快它的速度 - 其中一些使用 APC 作为存储后端。禁用插件后,您是否重置了 APC 缓存?

(您也可以在 APC 的源代码分发中找到此脚本)

相关内容