-
Notifications
You must be signed in to change notification settings - Fork 67
cf dev start is stuck at "57 out of 58 running" #294
Comments
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
MacBook Pro (13-inch, Late 2016)/Intel Core i7 2,4 GHz dual-core/16Gb Memory/ 500 Gb SSD All was running fine last week, but since yesterday (February 18th, 2018) it fails to complete startup as only 57 of 58 services will start.
Gathering log files using cf dev debug command and ssh’ing into the virtual machine teaches me that it’s the service syslog_drain_binder that doesn’t start because its certificate (/var/vcap/jobs/syslog_drain_binder/config/certs/syslogdrainbinder.crt) expired at Feb 15 22:35:39 2018 GMT As such it seems we need to update the certificate to make it work again. The information in the logs that lead me to this conclusion are below: /var/pcfdev/provision.log
/var/vcap/monit/monit.log
var/vcap/sys/log/syslog_drain_binder/syslog_drain_binder.log
|
Looks like this is a duplicate of #293 |
Yes that's true. You can close this issue if you want. |
Fixed in v0.29 |
Executing "cf dev start" gives the following result:
Using existing image.
Allocating 4096 MB out of 15715 MB total system memory (11282 MB free).
Importing VM...
Starting VM...
Provisioning VM...
Waiting for services to start...
7 out of 58 running
7 out of 58 running
7 out of 58 running
7 out of 58 running
35 out of 58 running
39 out of 58 running
55 out of 58 running
57 out of 58 running
...
57 out of 58 running
I'm already waiting around half an hour for it to finish. It seems like one service fails to start. Please tell me how to access the logs of the pcfdev VM to find out what's the problem.
cf version: cf version 6.34.1+bbdf81482.2018-01-17
cf dev version: PCF Dev version 0.28.0 (CLI: 5cda315, OVA: 0.547.0)
Virtualbox version: Version 5.1.32 r120294 (Qt5.5.1)
The text was updated successfully, but these errors were encountered: