Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Docker Otter 3.0.11 Segmentation fault (core dumped)



  • How to improve the stability of work - [1] periodically crashes if there are servers (tried with ssh and powershell agentless, Otter 3.0.8-3.0.11):

    Running Execution Dispatcher...
    Running Execution Dispatcher...
    Execution Dispatcher completed.
    Execution Dispatcher completed.
    Initializing Log Retention...
    Initializing Log Retention...
    Log Retention initialized.
    Log Retention initialized.
    Running Log Retention...
    Running Log Retention...
    Log Retention completed.
    Log Retention completed.
    Running Server Checker...
    Running Server Checker...
    Checking servers...
    Checking servers...
    Beginning status check for SSH server on pxmx-1002...
    Beginning status check for SSH server on pxmx-1002...
    Attempting to connect to SSH server at 10.72.14.160:22...
    Attempting to connect to SSH server at 10.72.14.160:22...
    Beginning status check for SSH server on pxmx-148...
    Beginning status check for SSH server on pxmx-148...
    Attempting to connect to SSH server at 172.17.0.1:22...
    Attempting to connect to SSH server at 172.17.0.1:22...
    Server Checker completed.
    Server Checker completed.
    info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
    Request starting HTTP/1.1 POST http://pxmx-1013/0x44/Otter.WebApplication/Inedo.Otter.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 0
    info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
    Request finished HTTP/1.1 POST http://pxmx-1013/0x44/Otter.WebApplication/Inedo.Otter.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 0 - 200 30 - 32.1763ms
    Segmentation fault (core dumped)

    1. 'docker start -ai otter' (or "docker rm otter; docker run -it --name=otter ...)
    • Segmentation fault (core dumped)
    1. Workaround: (before 'docker start') clear content of folder "Temp path" (/tmp/otter) on the last server (or otherwise - on all servers)

    2. Quick repeated crash:

    • [2] Creating a new server with incorrect parameters (workaround: delete record from table Servers);
    • (or) [3] Changing the account ("Credentials" of server) with the same "Temp path" (workaround: separated /tmp/otter/username);
    • (or) [4] Run script with any typo (workaround: delete record from table RaftItems).

  • inedo-engineer

    Hello;

    Thanks for all the detailed information, we'll definitely investigate what could be causing a segfault. This definitely shouldn't be the case...

    is anything logged in Admin > Diagnostic Center?

    Thanks.
    Alana



  • Hello, Alana

    In DiagnosticCenter\LogMessages only:
    Error scanning PowerShell agent: MI_RESULT_ACCESS_DENIED ServerCheckerRunner 09/28/2021 03:29:38
    Error scanning PowerShell agent: MI_RESULT_ACCESS_DENIED ServerCheckerRunner 09/26/2021 17:28:59
    Error scanning PowerShell agent: MI_RESULT_ACCESS_DENIED ServerCheckerRunner 09/26/2021 17:28:59
    ...

    here bold - last message before crash.

    I sended some details with tiket '[EDO-7968]':

    1. logs_otter*.txt - last result of command 'docker logs otter';
    2. LogMessages.csv - sql-export of table 'LogMessages'.

    I can collect data what you say.

    Best wishes,
    Igor


  • inedo-engineer

    Hi Igor,

    Thanks for the help in tracking this down. We've now fixed this in an internal build (logged as OT-428) . The fix will be in Otter v3.0.12, scheduled for release on October 8.

    If you'd like to test a prerelease build, you can pull the proget.inedo.com/productimages/inedo/otter:3.0.12-ci.1 image, which already contains the fix.

    -Greg


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation