我继续从WHM发送给我的HTTPD失败消息,看似随意… cPanel ChkServd Service Monitor httpd on vds64_centos54 failed. httpd failed A restart was attempted automagically. Failure reason: Service check failed to complete httpd: [!= http/1...] cPanel ChkServd Service Monitor httpd on vds64_centos54 failed. httpd failed A restart was attempted automagically. Failure reason: Service check failed to complete httpd: [!= http/1...] cPanel ChkServd Service Monitor httpd on vds64_centos54 failed. httpd failed A restart was attempted automagically. Failure reason: Service check failed to complete httpd: [!= http/1...]我在重新启动尝试编号18现在…
这是这样的结果:
[root@server ~]# service httpd status Looking up localhost Making HTTP connection to localhost Sending HTTP request. HTTP request sent; waiting for response. Alert!: Unexpected network read error; connection aborted. Can't Access `http://localhost/whm-server-status' Alert!: Unable to access document. lynx: Can't access startfile
一切似乎在服务器上正常运行,但公众…
其他一些信息…这是从/usr/local/apache/logs/error_logs :
[Sat Aug 20 16:03:54 2011] [notice] child pid 12852 exit signal Segmentation fault (11) [Sat Aug 20 16:04:07 2011] [notice] child pid 12854 exit signal Segmentation fault (11) [Sat Aug 20 16:05:02 2011] [notice] child pid 12857 exit signal Segmentation fault (11) [Sat Aug 20 16:05:21 2011] [notice] child pid 12850 exit signal Segmentation fault (11) [Sat Aug 20 16:07:54 2011] [notice] caught SIGTERM, shutting down
看起来好像我每次看到CAUGHT SIGTERM消息时都会从CPanel收到消息
请求web服务器状态的事实是导致服务器的段错误意味着你的mod_status模块以某种方式被破坏。 检查Apache的configuration,以确保它没有加载从一些旧的安装不匹配当前的服务器的stream浪mod_status模块。
编辑
好的,基于另一个问题,它看起来像你的networking服务器被失败的httpd.x86_64 0:2.2.3-45.el5.centos.1包搞砸了。 它可能在错误之前覆盖了一些东西。 你以前使用EasyApache包吗? 你可能不得不重build它,让事情再次正常工作。 如果你走这条路线,你将不得不使用EasyApache来定制安装的php模块,而不是使用centos软件包。 如果使用centos软件包,则可能必须手动重新configuration服务器以支持cpanel / whm(如自定义whm-server-status链接)。 从另外一个问题的日志中可以看出,旧的httpdconfiguration没有被覆盖,所以你可以把configuration文件合并在一起。
编辑2
根据这里的聊天,看起来发生了什么事情,安装Atomic Secured Linux会覆盖由EasyApache安装的mod_security2.so模块,其版本不兼容,并且这在访问状态页面时只会触发segfault。 禁用不兼容的mod_security2.so可以解决这个问题,但是您需要重buildEasyApache以获取被覆盖的mod_security2.so,以及如何做到这一点(或者是否可以重build模块)是一件大事为一个新的问题。