graceful kill fail, sending SIGKILL【已解决!】
本帖最后由 wwwimlgmcom 于 2017-9-16 17:40 编辑宝塔windows面板目前最新版本imap是不是有问题?
错误我不知道怎么得到,我从upupw搬过来的,然后网站的评论邮件就发不出去
搬回去upupw又正常!
目前我又迁回到宝塔了,谁来测试一下
系统: Windows Server 2008 R2 Enterprise x64
WINNT; Apache2.4.27; PHP 5.2.17; mysqli; curl
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
admin@example.com to inform them of the time this error occurred,
and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
</body></html>
mod_fcgid: process 6672 graceful kill fail, sending SIGKILL
mod_fcgid: process 8740 graceful kill fail, sending SIGKILL
mod_fcgid: process 6816 graceful kill fail, sending SIGKILL
mod_fcgid: process 3516 graceful kill fail, sending SIGKILL
mod_fcgid: process 6148 graceful kill fail, sending SIGKILL
mod_fcgid: process 7320 graceful kill fail, sending SIGKILL
mod_fcgid: process 7276 graceful kill fail, sending SIGKILL
mod_fcgid: process 6280 graceful kill fail, sending SIGKILL
测试请用www.bs-st.com
www.imlgm.com已经不是宝塔了
已解决!
1,先检查25端口,如果用465端口就检查465端口是否可用;
2,宝塔后台软件管理设置你的PHP看下imap扩展是否已安装;
3,检查自己的邮件发送执行程序源码或者账号等信息是否正确!
私信提供下面板账号密码,还有具体怎么操作出现错误的 如果说25端口是被封了!那么465试试?
mod_fcgid: process 3904 graceful kill fail, sending SIGKILL
mod_fcgid: process 564 graceful kill fail, sending SIGKILL
mod_fcgid: process 1384 graceful kill fail, sending SIGKILL
依旧 我也是这个问题 senwell 发表于 2017-9-13 10:40
我也是这个问题
同一个主机,装UPUPW没事~那绝对就是宝塔的邮件扩展有问题 本帖最后由 178885979 于 2017-9-16 22:30 编辑
wwwimlgmcom 发表于 2017-9-13 11:02
同一个主机,装UPUPW没事~那绝对就是宝塔的邮件扩展有问题
大佬啊!这里都遇到大谋了,缘分。宝塔的邮件扩展确实有问题,我的zb后台邮件提醒插件也用不了!也是win+iis+宝塔启用imap,换过465. 178885979 发表于 2017-9-16 22:22
大佬啊!这里都遇到大谋了,缘分。宝塔的邮件扩展确实有问题,我的zb后台邮件提醒插件也用不了!也是win+i ...
通过你这个启发,我也解决了,摸索半天,用阿里企业邮,25端口被封,465也不行,解决办法是smtp直接用cname原纪录“smtp.mxhichina.com”,端口465,然后就成功了!
页:
[1]