[FOLIO-1601] Intermittent Vagrant box startup failure Created: 30/Oct/18 Updated: 29/Jan/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ci, sprint50, sprint51, sprint52, sprint53, sprint54 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
| Sprint: | |
| Development Team: | Core: Platform |
| Description |
|
Ian Ibbotson (Use this one) reports:
Okapi log attached ( okapi (1).log |
| Comments |
| Comment by Wayne Schneider [ 30/Oct/18 ] |
|
I believe the log messages come from the containers, not from Okapi itself. It almost seems that the container comes up before the network is fully available. I have not been able to reliably recreate this condition, though it happens quite reliably for Ian Ibbotson (Use this one) |
| Comment by Ian Ibbotson (Use this one) [ 28/Nov/18 ] |
|
A bit of googling finds https://bbs.archlinux.org/viewtopic.php?id=171496 which isn't exactly related, but might be a clue. My suspicion is that network-online.target is being reached as the docker0 interface comes online, but eth0 (10.0.2.15) isn't appearing until after. Just a guess tho. |
| Comment by Ian Ibbotson (Use this one) [ 15/Jan/19 ] |
|
I see this has gone to in progress - FYI - > service okapi stop is a viable workaround. |
| Comment by David Crossley [ 24/Jan/19 ] |
|
I experienced this today with the folio/Q4-2018 VM. I could do 'vagrant halt, destroy, up' repeatedly, and it keeps happening. Using another VM folio/snapshot-core is okay. Then back to the folio/Q4-2018 VM and it is still happening. Wayne tried today and it is okay for him. Attached a fresh okapi.log (but essentially same as the existing log). So i did sudo systemctl restart okapi and all is well. But after 'vagrant halt, destroy, up' same again. Did 'vagrant box remove folio/Q4-2018; vagrant up' and now it is happy. |