-
Notifications
You must be signed in to change notification settings - Fork 67
Unable to start PCF-Dev environment: Timed out after 3600 seconds. #273
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. |
Hi @stalv, Sorry for the delay! Can you provide more info about the hardware you're running PCF Dev on? Does it start successfully without |
Hi @sclevine, |
How about with If you email me ([email protected]) the archive generated by running |
PCF Dev start up fails about 50% of the time for me. Mid-2012 Macbook Pro with 16GB Ram and 2.9GHz
|
@sclevine same thing with
|
Facing similar issues .. any solutions on it ? 2018-02-12T05:29:48.30-0800 [CELL/0] OUT Starting health monitoring of container |
Just started happening after most recent MacOS update (10.13.3). It was working fine until then.
Virtualbox 5.2.6 |
Virtualbox 5.1.14
SSHing inside with cf dev ssh and looking at the monit processes, I see
Looking at the log file:
I see this certificate error continuously
|
Appreciate if someone can point to a solution for this problem. Started seeing this behavior a couple of days ago. Running on:
|
Same issue. Started seeing the same issue a couple of days ago. |
I started the services successful once, since then the service provisioning stops at 55 services (0.26) or 57 services (0.28). any help appreciated ... debug output (cf dev debug) is attached |
Hi, I'm having the same problem as @firasag ... It used to work (around 20 days ago), but in the mean time I've applied Windows 10 updates (not sure if that is the reason, just saying...). Today I tried to start it again, and it timed out. I'm running:
|
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 on 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
|
Ah, great analysis of the problem. So best solution IMHO is to create a new VM including a new certificate, run cf dev destroy and then start over. |
Hi there, "... in my and folder |
@sclevine Can you look at this please? |
We are very aware of this issue. I will provide an update here after the holiday weekend, once I have a chance to chat with the team. |
holiday? |
Having the same problem here on a Windows 10 machine. It starts the services and repeats in the end "57 out of 58 running" until it times out. In the past it was enough to destroy the old VM and create a new one to fix the problem temporarily. This doesn't work anymore. Computer was not changed, no windows updates. I updated from PCF dev 27 to version 28, still the same result. I would be really thankfull for every help/fix because I'm reliant at PCF dev at the moment and really need to get it working again. Update: Downgraded to version 24. Now it runs. But would be really nice to have some help/fixes to use the actual version again :). |
@menza12 https://en.wikipedia.org/wiki/Presidents_Day @Marcel2267 We're hoping to cut a patch release that fixes this issue and release the first alpha of the rewrite (with a functional BOSH director + native hypervisor support!) this week. |
@sclevine can you post here with an update on when this is expected to be resolved? PCF Dev is pretty handy, and the alternatives are not as easy to use. Thanks :) |
Fixed in v0.29 |
Issue still persists when deploying v0.29 $ ./pcfdev-v0.29.0+PCF1.11.0-linux $ cf dev start looking into /var/vcap/monit/monit.log: also linked result of |
It looks like your Also, is this error consistent every time you |
Yes, i've tried a couple of times.
I think i can get logs only after holidays, on monday.. |
Thank you for the new version. I was able to get it working. |
$ cat /var/vcap/sys/log/galera-healthcheck/galera-healthcheck.stdout.log
$ cat /var/vcap/sys/log/galera-healthcheck/galera-healthcheck.stderr.log
My host machine is proxyed via cntlm, which is sitting on 3128 port. |
Submitted new issue (#300), since it seems to be proxy-related. |
I'm unable to start PCF-Dev environment on my local linux machine. The command
cf dev start
failing after 3600 sec timeout.Virutal machine is up and running and I can ssh to it with
cf dev ssh
. There is only one suspicious thing in the logs in/var/vcap
directoryMy system details:
Ubuntu 17.10 x64 4.13.0-16-generic
VirtualBox 5.1.30_Ubuntu r118389
PCF Dev version 0.28.0 (CLI: 5cda315, OVA: 0.547.0)
The text was updated successfully, but these errors were encountered: