Rocket U2 | UniVerse & UniData

 View Only
Back to discussions
Expand all | Collapse all

Did you know... On UV 11.2.5 if a phantom with an active COMO aborts the UV error message is not captured in the COMO

  • 1.  Did you know... On UV 11.2.5 if a phantom with an active COMO aborts the UV error message is not captured in the COMO

    PARTNER
    Posted 02-18-2021 00:51
    Edited by Gregor Scott 02-18-2021 00:52
    I stumbled across this when digging into a transaction related issue.
    Knowing about this might help someone in the future.

    Context: UV 11.2.5 on RHEL7

    We had a phantom process that would die unexpectedly during processing.

    The phantom had an active COMO recording going at the time it died, but the COMO file did not capture the error message produced by the phantom.
    The only way I could track why the phantom process was aborting was to have the pid launch a unix strace in background that traces the pid of the phantom, and check the trace file output at the end.
    The strace output file did capture the phantom's error message

    The reason appears to be that the UV phantom's COMO is only capturing the standard output (stdout). The error messages produced by the uv phantom are still sent to standard error (stderr), and this is not included in the COMO recording.

    #como #strace #UniVerse #rhel​​

    ------------------------------
    Gregor Scott
    gregors
    ------------------------------
    ​​