Clarity Service Management

Expand all | Collapse all

Webengine restarts

Jump to Best Answer
  • 1.  Webengine restarts

    Posted 04-01-2019 11:31 AM

    We just had a webengine restart apparently on its own.  Does anyone know what would cause that?



  • 2.  Re: Webengine restarts

    Posted 04-01-2019 11:36 AM

    Patsy, there are many reasons a webengine restarts and I think the best place to get some idea is to check stdlog and OS env log. Thanks _Chi



  • 3.  Re: Webengine restarts

    Posted 04-01-2019 11:39 AM

    Thanks Chi

    I have been going over stdlogs.  When in the OS would cause Service Desk to restart the webengine?



  • 4.  Re: Webengine restarts

    Posted 04-01-2019 12:31 PM

    if webengine crashes there should be something in the event view. 

    Reasons like some run away custom/system spel code, some weird string etc.



  • 5.  Re: Webengine restarts

    Posted 04-01-2019 12:43 PM

    This is from the Windows log

     

    Faulting application name: webengine.exe, version: 14.1.0.224, time stamp: 0x5aaeda9d
    Faulting module name: webengine.exe, version: 14.1.0.224, time stamp: 0x5aaeda9d
    Exception code: 0xc0000005
    Fault offset: 0x0024464c
    Faulting process id: 0x2b64
    Faulting application start time: 0x01d4e61aa3d74bed
    Faulting application path: C:\PROGRA~2\CA\SERVIC~1\bin\webengine.exe
    Faulting module path: C:\PROGRA~2\CA\SERVIC~1\bin\webengine.exe
    Report Id: 725f151f-548e-11e9-8114-005056b27aa3
    Faulting package full name:
    Faulting package-relative application ID:



  • 6.  Re: Webengine restarts
    Best Answer

    Posted 04-01-2019 04:38 PM

    yes webengine crashed but without crash dump the windows event log alone can't tell why.

    maybe it is time to work with Broadcom Support to enable crash dump so next time it happens Broadcom DEV can help review the crash dump?



  • 7.  Re: Webengine restarts

    Posted 04-01-2019 02:26 PM

    Perhaps the WebEngine process reached its 2GB memory usage and crashed as a result.

     

    Do you have interval logging enabled to check to see how much memory the process was using?