1014660 - "Error: Application [nucleus] failed to start, see log above." reported to console, but application did not actually fail to start

Status: RESOLVED WORKSFORME

(Infrastructure & Operations :: IT-Managed Tools, task)

Description

[Josh Mize [:jgmize]]

After hanging several times while trying to push nucleus to the dev paas, I finally succeeded in pushing, but had to do a manual "stackato start" b/c it was in a stopped state from failed pushes. At the end of the "stackato start" command, I got the error message in the summary, but the message itself was an error, because the app did in fact start. This has happened to me before, which is why I knew to check before just trying to run "stackato start" again. I'm filing this bug to document the recurring issue.

Comment 1

[Chris Turra [:cturra]]

can you confirm if this is the same or different as bug 979149?

Comment 2

[Josh Mize [:jgmize]]

Yes, this bug is a different intermittent problem from the one described in bug 979149.

Comment 3

[Chris Turra [:cturra]]

... and does this happen every time you deploy nucleus. i guess what i am asking is what are your priorities - do you want me to spend time investigating this, if in fact it was a false positive and did not impact your deployment?

Comment 4

[Josh Mize [:jgmize]]

No, I think I've only run into it 2 or 3 times-- this bug was simply documenting that it occasionally happened, mainly in case others ran into it as well, and is not a priority for me personally.

Comment 5

[Chris Turra [:cturra]]

throwing this back into the unassigned queue. this bug is to track the "failed to start" error. the plan was to evaluate this after a stackato upgrade to 3.x

Comment 6

[:Atoll]

We haven't received any other reports of this issue, so we're going to go ahead and close this bug as WORKSFORME. Feel free to reopen if necessary.