无法连接到 Win XP 64 位上 XAMPP 下的本地 apache 安装。 帮助!

发布于 2024-07-10 23:56:37 字数 1701 浏览 6 评论 0原文

我在 Win XP-64 位计算机上使用 XAMPP v1.7,我的 Symantec AV 已关闭,Windows 防火墙也已关闭,并且我无法从浏览器连接到本地主机。

我最初有这些错误:
[Wed Jan 07 16:24:55 2009] [错误] (OS 10038)尝试对非套接字的操作。 :子 2716:接受客户端连接时遇到太多错误。 可能的原因:动态地址更新、VPN 或防火墙软件不兼容。 尝试使用 Win32DisableAcceptEx 指令

在我将 Win32DisableAcceptEx 指令添加到 httpd.conf 后,这些错误消失了,但最终结果仍然相同:没有乐趣。

现在,我收到以下错误:
[Wed Jan 07 16:40:15 2009] [通知] Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11
OpenSSL/0.9.8i mod_autoindex_color PHP/5.2.8 配置 -- 恢复正常操作
[Wed Jan 07 16:40:15 2009] [通知] 服务器搭建时间:2008年12月10日 00:10:06
[Wed Jan 07 16:40:15 2009] [通知] 父进程:已创建子进程 5916
[Wed Jan 07 16:40:15 2009] [通知] 禁用 AcceptEx() WinSock2 API
[Wed Jan 07 16:40:15 2009] [通知] 摘要:生成摘要身份验证的秘密
... [Wed Jan 07 16:40:15 2009] [通知] 摘要:完成
[Wed Jan 07 16:40:15 2009] [通知] 子进程 5916:子进程正在运行
[Wed Jan 07 16:40:15 2009] [通知]子进程 5916:获取了启动互斥体。
[Wed Jan 07 16:40:15 2009] [通知] Child 5916:启动 250 个工作线程。
[Wed Jan 07 16:40:15 2009] [通知] 子进程 5916:监听端口 443。
[Wed Jan 07 16:40:15 2009] [通知] 子进程 5916:监听端口 80。
[Wed Jan 07 16:40:15 2009] [错误] (OS 10038)尝试对非套接字的内容进行操作。 :选择循环中错误太多。 子进程退出。
[Wed Jan 07 16:40:15 2009] [通知] Child 5916:已发出退出事件信号。 子进程正在结束。
[Wed Jan 07 16:40:16 2009] [通知] Child 5916:释放了启动互斥体
[Wed Jan 07 16:40:17 2009] [通知] Child 5916:所有工作线程已退出。
[Wed Jan 07 16:40:17 2009] [通知] 子进程 5916:子进程正在退出
[Wed Jan 07 16:40:17 2009] [通知] 父进程:子进程已退出,状态为 0 -- 正在重新启动。
[Wed Jan 07 16:40:17 2009] [通知] 摘要:生成摘要身份验证的秘密 ...
[Wed Jan 07 16:40:17 2009] [notice] 摘要:完成

而且,apache 似乎崩溃了(Windows 告诉我是这样,我可以在系统事件中看到崩溃。)

我是 n00b到apache,但需要让它运行。 有想法吗? 马库斯

I'm using XAMPP v1.7 on an Win XP-64 bit machine, my Symantec AV is turned off as is my Windows Firewall, and I can't connect to localhost from a browser.

I originally had these errors:
[Wed Jan 07 16:24:55 2009] [error] (OS 10038)An operation was attempted on something that is not a socket. : Child 2716: Encountered too many errors accepting client connections. Possible causes: dynamic address renewal, or incompatible VPN or firewall software. Try using the Win32DisableAcceptEx directive

These errors went away after I added the Win32DisableAcceptEx directive to httpd.conf, but the net result remains the same: no joy.

Now, I get these errors:
[Wed Jan 07 16:40:15 2009] [notice] Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11
OpenSSL/0.9.8i mod_autoindex_color PHP/5.2.8 configured -- resuming normal operations
[Wed Jan 07 16:40:15 2009] [notice] Server built: Dec 10 2008 00:10:06
[Wed Jan 07 16:40:15 2009] [notice] Parent: Created child process 5916
[Wed Jan 07 16:40:15 2009] [notice] Disabled use of AcceptEx() WinSock2 API
[Wed Jan 07 16:40:15 2009] [notice] Digest: generating secret for digest authentication
...
[Wed Jan 07 16:40:15 2009] [notice] Digest: done
[Wed Jan 07 16:40:15 2009] [notice] Child 5916: Child process is running
[Wed Jan 07 16:40:15 2009] [notice] Child 5916: Acquired the start mutex.
[Wed Jan 07 16:40:15 2009] [notice] Child 5916: Starting 250 worker threads.
[Wed Jan 07 16:40:15 2009] [notice] Child 5916: Listening on port 443.
[Wed Jan 07 16:40:15 2009] [notice] Child 5916: Listening on port 80.
[Wed Jan 07 16:40:15 2009] [error] (OS 10038)An operation was attempted on something that
is not a socket. : Too many errors in select loop. Child process exiting.
[Wed Jan 07 16:40:15 2009] [notice] Child 5916: Exit event signaled. Child process is ending.
[Wed Jan 07 16:40:16 2009] [notice] Child 5916: Released the start mutex
[Wed Jan 07 16:40:17 2009] [notice] Child 5916: All worker threads have exited.
[Wed Jan 07 16:40:17 2009] [notice] Child 5916: Child process is exiting
[Wed Jan 07 16:40:17 2009] [notice] Parent: child process exited with status 0 -- Restarting.
[Wed Jan 07 16:40:17 2009] [notice] Digest: generating secret for digest authentication ...
[Wed Jan 07 16:40:17 2009] [notice] Digest: done

And, apache seems to be crashing (Windows tells me so, and I can see the crash in the system events.)

I'm a n00b to apache, but need to get this running. Ideas?
Marcus

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

生生漫 2024-07-17 23:56:37

如果有人遇到此问题,请尝试

运行netsh Winsock RESET

从命令行 。 这对我有用。

If anyone comes across this, try running

netsh winsock RESET

from the command line. It worked for me.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文