apache serverName 的启动问题
2008-06-13 10:53
393 查看
最近用apache时出现启动问题,如下:
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.100.38 for ServerName
[Fri Jun 13 10:24:52 2008] [notice] Apache/2.2.8 (Win32) configured -- resuming normal operations
[Fri Jun 13 10:24:52 2008] [notice] Server built: Jan 18 2008 00:37:19
[Fri Jun 13 10:24:52 2008] [notice] Parent: Created child process 1728
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.100.38 for ServerName
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.100.38 for ServerName
[Fri Jun 13 10:24:53 2008] [notice] Child 1728: Child process is running
[Fri Jun 13 10:24:53 2008] [notice] Child 1728: Acquired the start mutex.
[Fri Jun 13 10:24:53 2008] [notice] Child 1728: Starting 64 worker threads.
[Fri Jun 13 10:24:53 2008] [notice] Child 1728: Starting thread to listen on port 80.
修改serverName,重装apache后问题依旧,最后发现host配置不正确,
httpd.conf 中serverName 为www.zudar.com
host 中 127.0.0.1 www.zudar.com
改为 192.168.100.38 www.zudar.com
后正确启动
问题是由于 ip 地址 与 域名没有正确匹配引起
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.100.38 for ServerName
[Fri Jun 13 10:24:52 2008] [notice] Apache/2.2.8 (Win32) configured -- resuming normal operations
[Fri Jun 13 10:24:52 2008] [notice] Server built: Jan 18 2008 00:37:19
[Fri Jun 13 10:24:52 2008] [notice] Parent: Created child process 1728
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.100.38 for ServerName
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.100.38 for ServerName
[Fri Jun 13 10:24:53 2008] [notice] Child 1728: Child process is running
[Fri Jun 13 10:24:53 2008] [notice] Child 1728: Acquired the start mutex.
[Fri Jun 13 10:24:53 2008] [notice] Child 1728: Starting 64 worker threads.
[Fri Jun 13 10:24:53 2008] [notice] Child 1728: Starting thread to listen on port 80.
修改serverName,重装apache后问题依旧,最后发现host配置不正确,
httpd.conf 中serverName 为www.zudar.com
host 中 127.0.0.1 www.zudar.com
改为 192.168.100.38 www.zudar.com
后正确启动
问题是由于 ip 地址 与 域名没有正确匹配引起
相关文章推荐
- Linux中启动Apache中的Could not reliably determine the server's fully qualified domain name问题
- linux下apache启动问题(dummy-host.example.com does not exist, Could not..127.0.0.1 for ServerName)
- hbase无法启动Regionserver:ClassNotFoundException: org.apache.hadoop.util.PlatformName问题解决
- Apache启动提示Could not reliably determine the server's fully ...:1 for ServerName
- Hadoop 故障问题 org.apache.hadoop.hdfs.server.namenode.DecommissionManager: Interrupted Monitor
- 解决apache/nginx做反向代理导致request.getServerName()外网环境获取不到代理地址(或域名)的问题
- 解决apache/nginx做反向代理导致request.getServerName()外网环境获取不到代理地址(或域名)的问题
- 解决apache/nginx做反向代理导致request.getServerName()外网环境获取不到代理地址(或域名)的问题
- warmserver apache无法启动,mysql无法打开的问题
- Ubuntu Eclipse的Tomcat小问题:不能输入server name,不能启动tomcat
- 启动apache遇到错误:httpd: Could not reliably determine the server's fully qualified domain name
- 找不到或无法加载主类 org.apache.hadoop.hdfs.server.namenode.NameNode 问题解决
- 解决apache/nginx做反向代理导致request.getServerName()外网环境获取不到代理地址(或域名)的问题
- 解决apache/nginx做反向代理导致request.getServerName()外网环境获取不到代理地址(或域名)的问题
- 解决apache/nginx做反向代理导致request.getServerName()外网环境获取不到代理地址(或域名)的问题
- 解决apache/nginx做反向代理导致request.getServerName()外网环境获取不到代理地址(或域名)的问题
- 解决apache/nginx做反向代理导致request.getServerName()外网环境获取不到代理地址(或域名)的问题
- Apache启动出现错误:httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
- 安装nagios时apache启动时出现错误using localhost.localdomain for ServerName
- 启动apache遇到错误:httpd: Could not reliably determine the server's fully qualified domain name