2012-01-24 60 views
2

我已經安裝了的Cloud Foundry插件我的Grails項目,我已經成功地一次把我的項目到雲,但云部署時,我試圖用更新我的應用程序,錯誤而使用的Cloud Foundry

grails prod cf-update 

命令。當我這樣做,我得到以下錯誤:

ERROR - Application 'scheduleNew' failed to start, logs information below. 

==== logs/stderr.log ==== 
Jan 23, 2012 2:45:02 AM org.apache.coyote.http11.Http11Protocol init 
INFO: Initializing Coyote HTTP/1.1 on http-8963 
Jan 23, 2012 2:45:02 AM org.apache.catalina.startup.Catalina load 
INFO: Initialization processed in 378 ms 
Jan 23, 2012 2:45:02 AM org.apache.catalina.realm.JAASRealm setContainer 
INFO: Set JAAS app name Catalina 
Jan 23, 2012 2:45:02 AM org.apache.catalina.core.StandardService start 
INFO: Starting service Catalina 
Jan 23, 2012 2:45:02 AM org.apache.catalina.core.StandardEngine start 
INFO: Starting Servlet Engine: Apache Tomcat/6.0.35 
Jan 23, 2012 2:45:02 AM org.apache.catalina.startup.HostConfig deployDirectory 
INFO: Deploying web application directory ROOT 
Jan 23, 2012 2:45:12 AM org.apache.catalina.core.StandardContext start 
SEVERE: Error listenerStart 
Jan 23, 2012 2:45:12 AM org.apache.catalina.core.StandardContext start 
SEVERE: Context [] startup failed due to previous errors 
Jan 23, 2012 2:45:12 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads 
SEVERE: The web application [] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. 
Jan 23, 2012 2:45:12 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads 
SEVERE: The web application [] appears to have started a thread named [[email protected]] but has failed to stop it. This is very likely to create a memory leak. 
Jan 23, 2012 2:45:12 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads 
SEVERE: The web application [] appears to have started a thread named [org.example.SecRole.data] but has failed to stop it. This is very likely to create a memory leak. 
Jan 23, 2012 2:45:12 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads 
SEVERE: The web application [] appears to have started a thread named [org.hibernate.cache.UpdateTimestampsCache.data] but has failed to stop it. This is very likely to create a memory leak. 
Jan 23, 2012 2:45:12 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads 
SEVERE: The web application [] appears to have started a thread named [org.hibernate.cache.StandardQueryCache.data] but has failed to stop it. This is very likely to create a memory leak. 

==== logs/stdout.log ==== 

Configuring Spring Security Core ... 
... finished configuring Spring Security Core 

Stopping Tomcat because the context stopped. 

當我再次運行相同的命令(grails prod cf-update),錯誤信息得到改變:

ERROR - Application 'scheduleNew' failed to start, logs information below. 

==== logs/stderr.log ==== 
Jan 23, 2012 2:52:14 AM org.apache.coyote.http11.Http11Protocol init 
INFO: Initializing Coyote HTTP/1.1 on http-45003 
Jan 23, 2012 2:52:14 AM org.apache.catalina.startup.Catalina load 
INFO: Initialization processed in 379 ms 
Jan 23, 2012 2:52:14 AM org.apache.catalina.realm.JAASRealm setContainer 
INFO: Set JAAS app name Catalina 
Jan 23, 2012 2:52:14 AM org.apache.catalina.core.StandardService start 
INFO: Starting service Catalina 
Jan 23, 2012 2:52:14 AM org.apache.catalina.core.StandardEngine start 
INFO: Starting Servlet Engine: Apache Tomcat/6.0.35 
Jan 23, 2012 2:52:14 AM org.apache.catalina.startup.HostConfig deployDirectory 
INFO: Deploying web application directory ROOT 

我真不明白怎麼回事在這。

這些錯誤信息說什麼?我哪裏出錯了?

回答

2

還有其他的日誌文件。如果您使用http://grails-plugins.github.com/grails-cloud-foundry/docs/manual/ref/Scripts/cf-list-files.html命令,則可以獲取目錄列表。運行grails cf-list-files /以獲取頂級目錄的列表(它將包含一個logs和一個tomcat目錄)。 logs目錄可能只包含您已經看到的stderr和stdout文件,但在tomcat目錄下有另一個日誌目錄:grails cf-list-files /tomcat/logs。這應該有其他更豐富的日誌文件。同時檢查tomcat目錄中是否有stacktrace.log

一旦找到想要查看的文件,請使用http://grails-plugins.github.com/grails-cloud-foundry/docs/manual/ref/Scripts/cf-get-file.html命令查看它們,例如,

grails cf-get-file /tomcat/stacktrace.log 

grails cf-get-file /tomcat/logs/catalina.2012-01-24.log