在我在bluemix上部署我的Asp.net核心应用程序时遇到此问题。
托管服务提供商是Bluemix。
日志：
Downloading artifacts...DOWNLOAD SUCCESSFUL Target:
https://api.ng.bluemix.net Using manifest file
/home/pipeline/cb3f3db1-2e27-4c5a-a1f4-e5b8f9ada7f6/manifest.yml
将org myproject_org / space Dev中的app myproject01更新为xyz@gmail.com ...
OK
Using route myproject01.mybluemix.net
Uploading myproject01...
Uploading app files from: /home/pipeline/cb3f3db1-2e27-4c5a-a1f4-e5b8f9ada7f6
Uploading 14.7M, 2061 files
Done uploading
OK
Binding service myproject01-cloudantNoSQLDB to app myproject01 in org myproject_org / space Dev as katoch.rohit@gmail.com...
OK
Stopping app myproject01 in org myproject_org / space Dev as katoch.rohit@gmail.com...
OK
Starting app myproject01 in org myproject_org / space Dev as katoch.rohit@gmail.com...
-----> Downloaded app package (56M)
ASP.NET Core buildpack version: v0.9-20160706-1603
ASP.NET Core buildpack starting compile
-----> Restoring files from buildpack cache
Copied 199 files from /tmp/cache/.dotnet to /tmp/staged/app
Copied 14925 files from /tmp/cache/.nuget to /tmp/staged/app
Copied 37 files from /tmp/cache/libunwind to /tmp/staged/app
OK
-----> Extracting libunwind
OK
-----> Installing Dotnet CLI
OK
-----> Restoring dependencies with Dotnet CLI
log : Restoring packages for /tmp/staged/app/src/myproject.Utility/project.json...
log : Restoring packages for /tmp/staged/app/src/myproject.Core/project.json...
log : Restoring packages for /tmp/staged/app/src/dotnetCloudantWebstarter/project.json...
log : Restoring packages for /tmp/staged/app/project.json...
log : Writing lock file to disk. Path: /tmp/staged/app/src/myproject.Utility/project.lock.json
log : Writing lock file to disk. Path: /tmp/staged/app/src/myproject.Core/project.lock.json
log : src/myproject.Utility/project.json
log : Restore completed in 1752ms.
log : src/myproject.Core/project.json
log : Restore completed in 1753ms.
log : ./project.json
log : Restore completed in 2036ms.
log : Restoring packages for tool 'Microsoft.AspNetCore.Server.IISIntegration.Tools' in /tmp/staged/app/src/dotnetCloudantWebstarter/project.json...
warn : dotnetCloudantWebstarter (>= 1.0.0) -> System.Threading.Tasks.Extensions (>= 4.0.0-rc2-24027)
log : Writing lock file to disk. Path: /tmp/staged/app/src/dotnetCloudantWebstarter/project.lock.json
log : src/dotnetCloudantWebstarter/project.json
log : Restore completed in 4439ms.
OK
-----> Saving to buildpack cache
Copied 0 files from /tmp/staged/app/.dotnet to /tmp/cache
Copied 0 files from /tmp/staged/app/.nuget to /tmp/cache
ASP.NET Core buildpack is done creating the droplet
-----> Uploading droplet (270M)
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
FAILED
Start app timeout
TIP: Application must be listening on the right port. Instead of hard coding the port, use the $PORT environment variable.
Use 'cf logs myproject01 --recent' for more information
Finished: FAILED
请帮我解决这个问题......
感谢。
答案 0 :(得分：0)
The current versions the boilerplates for ASP.NET Core in Bluemix have had their default memory limits increased to 512MB, but it seems that your application was based on an older version of those boilerplates which had the limit set to 256MB.
While this is enough for a basic "Hello World" style of application, once you start adding more functionality to the application it will need more memory at some point and not having enough memory will cause it to crash.
Increasing the memory limit to 512MB may fix the issues that you're having, but I would also start taking care of the warning messages that you're getting about package version mismatches too before that causes other issues. Pulling packages from both RC2 and RTM in the same application can be problematic when things have changed in the RTM version that your code is trying to call but the package that gets installed is from RC2.