How to debug Cloud deployment problems¶

    There is also a complete decision tree for the debugging process.

    Does the Control Panel show a “Last deployment failed” error message?

    -
    - The error message is not shown

    The Control Panel shows a Last deployment failed message¶

    Open the log. The relevant section will be towards the end, so work backwards from the end. Any error will be clearlystated.

    What does the deployment log contain?


    Probable fault: temporary problem¶

    Please try again. This is a rare and usually temporary problem. You may need to wait a few minutes for thecondition to clear. If the issue is urgent, or you have already tried again, please contact Divio Support.

    The deployment log contains no obvious error¶

    Check the site’s runtime logs (via the Logs menu).

    Do you see any obvious errors in the runtime logs for the container (of the appropriate server, Test or Live)?


    Probably your application took so long to start up that it triggered a timeout condition. Onour platform, if a site is not up and running within a certain period after its build hascompleted, then the deployment is marked as failed.

    This could happen because it is waiting for another external resource to become available, or theprocessing it needs to do at start-up is excessive. These issues generally represent a programmingproblem that needs to be resolved.

    Build the site locally and start up the application to investigate why it is taking so long.

    Restart the checklist

    Probable fault: programming error in runtime code¶

    Probably the issue is a programming error in the site that takes down Django as it launches (typically, this willbe an ). The runtime log will reveal the error.

    Restart the checklist

    The deployment log contains an error¶

    The end of the log will contain the key error.

    What does the error most closely resemble?


    Probable fault: dependency conflict¶

    An error that starts:

    indicates that two or more of the components in your system have specified incompatible Python dependencies.

    See .

    Restart the checklist

    Example:

    In this case one of the Node component installation processes has failed. If the error is not clear from the log,contact Divio support for advice.

    Probable fault: An import error halts one of the site build routines¶

    Example:

    In this case a Python application launched by an instruction in the has caused Django to halt with anerror while it was trying to run the command. This is a programming error. The traceback will showwhere it occurred.

    Restart the checklist

    Probable fault: temporary timeout error (read timeout)¶

    Example:

    This may occasionally occur when our deployment infrastructure is under heavy load. In most cases you can simply tryagain. If the issue is urgent, or you have already tried again, please contact Divio Support.

    Restart the checklist

    Probable fault: A runtime error¶

    If you are not sure what the error message reveals, please contact Divio support for assistance.

    Restart the checklist

    Sometimes there is no failed deployment log, but the site fails to start. This is typically causedby a programming error that becomes apparent at runtime.

    Usually, the browser will show a Django traceback, if the site is in mode (this is the default for the Test_server). Under some circumstances, it might not, but the error will be shown in the site’s runtime logs, available fromthe _Logs menu in the Control Panel.

    Decision tree¶

    This tree represents the logic of the debugging checklist.