2012-01-24 62 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