AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe80::1
是因為ServerName不可用 改成ServerName localhost:80或者其他可以的servername就可以了
相關推薦
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe80::1
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe80::1
解決httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName解決辦法非常簡單：[email protecte
linux Could not reliably determine the server's fully qualified domain name
今天在安裝httpd之後，搞了一下apache2.2和tomcat7的整合； 在重啟apache2.2的時候，出現了： [[email protected] conf]# service httpd restart 停止 httpd：
解決apache啟動錯誤：Could not reliably determine the server's fully qualified domain name
原文地址：http://www.2cto.com/os/201201/117797.html 啟動apache遇到錯誤：httpd: Could not reliably determine the server's fully qualified domain name
Apache啟動時報錯Could not reliably determine the server's fully qualified domain name
apache無法啟動，提示： 正在啟動 httpd：httpd: apr_sockaddr_info_get() failed for CentOS httpd: Could not reliab
AH00558: httpd.exe: Could not reliably determine the server's fully qualified do main name, using fe
Apache的配置檔案則是conf目錄下的httpd.conf檔案，將其開啟： 首先找到ServerName（約213行），將其設定為localhost:80，並將前面的井號刪除，雖然這一步如果不修改的話也可以正常執行，但啟動Apache服務時會有一條煩人的提示（AH
httpd: Could not reliably determine the server's fully
httpdStarting httpd: httpd: Could not reliably determine the server‘s fully qualified domain name, using 192.168.229.152 for ServerName(2)No such file or d
httpd: Could not reliably determine the server's fully qualified domain name
httpd: Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1 for ServerName 解決辦法非常簡單： #vim /web/apache/conf/h
解決apache啟動錯誤"httpd:Could not reliably determine
啟動apache遇到錯誤：httpd: Could not reliably determine the server's fully qualified domain name [[email protected] httpd-2.2.4]# /usr/l
invalid LOC header 與 Could not publish to the server. java.lang.IndexOutOfBoundsException 錯誤處理
1. 專案eclipse 部署問題 Could not publish to the server. java.lang.IndexOutOfBoundsException 原因： pom.xml 依賴的jar包有錯誤，maven 下載jar時，檔案為下載文章
Eclipse中啟動Tomcat時（MAVEN專案），報錯：Could not publish to the server. java.lang.IndexOutOfBoundsException的解決過程
Eclipse中啟動Tomcat時（MAVEN專案），報錯：Could not publish to the server. java.lang.IndexOutOfBoundsException，tomcat啟動失敗， 原因：該MAVEN專案下載的本地jar包存在下載失敗的情況 &nbs
mysql報錯 MySQL server PID file could not be found The server quit without updating PID file (/var/l
執行mysql重啟命令突然報錯： 後面的/var/lib/mysql/192.168.1.139.pid給了我們提示 我們進入/var/lib/mysql資料夾 發現了一個好東西 192.168.1.139.err(不用想錯誤資訊肯定在這裡面) 檢視日
eclipse配置tomcat，讓java web專案執行起來！ Tomcat v9.0 Could not publish to the server. java.lang.IndexOutOfBoundsException
做專案，搞開發。開發環境配置時第一步。只有環境搭好了，以後的事情才能順利進行！ 這不需求來了，負一屏專案有新功能需要新增，臨時接手，要進行伺服器前端開發。這個專案是以前後臺java人員進行開發的。都是jsp頁面，那個叫心塞的啊，看的一臉不爽。但是，工作還得繼續，沒接觸過的，就得去趟趟，試試水。 把專案cl
tomcat 啟動報Could not publish to the server. Please assign JRE to the server的解決方法
" shutdown="SHUTDOWN"> <Listener className="org.apache.catalina.startup.VersionLoggerListener" /> <!-- Security listener. Documentation at
tomcat啟動報錯Could not publish to the server. java.lang.NullPointerException
tomcat部署好後用了很久，突然啟動報錯： Could not publish to the server. java.lang.NullPointerException 解決方法： 在e
關於tomcat報錯Could not publish to the server
最近在學習相關課程的時候，啟動tomcat時，發現報錯Could not publish to the server. 然後把自己之前上傳的專案開啟以後再次啟動就可以了。 總結了原因： 啟動tomcat時 必須保證已經上傳發布到其中的專案要處於可訪問狀態，也就是要開啟專案
maven+ssm啟動Tomcat報錯 Could not publish to the server. java.lang.IndexOutOfBoundsException 解決辦法
1找到你maven安裝目錄D:\studys\apache-maven-3.5.3-bin\apache-maven-3.5.3\conf找到settings.xml開啟2，新增這段程式碼<mirror> <id>alimaven</id&
ssh: Could not resolve hostname git.*****-inc.com : Temporary failure in name resolution fatal: The remote end hung up unexpectedly
配置 soft mic target clas 無法執行 ssh pull 開發 問題出現的情景：使用git pull拉取開發的代碼到測試服務器，報錯： ssh: Could not resolve hostname git.****-inc.com : Tempo
Xcode報錯 The document “xxx.h” could not be saved. The file doesn’t exist.
文件的 ren xcode ould 退出 文件夾 問題 lean 內部 記錄一個問題 場景：Xcode編輯一個工程時直接在工程內部修改了某個目錄的文件夾名字，而後刪除了其下的某 .h.m 文件 之後總是提示上述錯誤且無法強制退出Xcode，clean等操作基本沒用 查找本
fatal: initialization error: could not initialize application. the application has not been initiali
ipmi dell 報錯: fatal: initialization error: could not initialize application. the application has not been initialized, 解決方法: # sed 's/jdk.