Where is the procore/protrace? - Forum - OpenEdge RDBMS - Progress Community

Where is the procore/protrace?

 Forum

Where is the procore/protrace?

This question is not answered

Hi,

I'm seeing error 49, followed by "** Save file named core... " in the db server log.

I've searched in client and server computers and couldn't find any file procore* neither protrace*.

Where can I find those files?

TIA!

All Replies
  • Hi Joey,

    These files are generated in the working directory of the process that generated it.  You should include the entire line from the db log as there are indicators about where the crash is happening there.

    What OS are you running?  On *nix operating systems you may see a core file.  

    You can generate a protrace using a core file using the instructions in the below kb article:

    knowledgebase.progress.com/.../3167

    Cheers,

    Ken McIntosh

    Progress Technical Support

    Kenneth S. McIntosh

    Principal Technical Support Engineer

     

     

  • Hi Ken,

    Here's the line:

    [2020/03/18@22:37:54.000+0000] P-29904      T-139836513474336 I ABL    59: (562)   HANGUP signal received.

    [2020/03/18@22:46:11.000+0000] P-27564      T-140714196502304 I ABL    66: (49)    SYSTEM ERROR: Memory violation.

    [2020/03/18@22:46:11.000+0000] P-27564      T-140714196502304 I ABL    66: (439)   ** Save file named core for analysis by Progress Software Corporation.

    [2020/03/18@22:53:53.000+0000] P-3619       T-140637170202400 I ABL    59: (49)    SYSTEM ERROR: Memory violation.

    [2020/03/18@22:53:53.000+0000] P-3619       T-140637170202400 I ABL    59: (439)   ** Save file named core for analysis by Progress Software Corporation.

    [2020/03/18@15:58:54.041-0700] P-16400      T-140602164492032 I SRV    14: (794)   Usernum 321 terminated abnormally.

    [2020/03/18@15:58:54.042-0700] P-16400      T-140602164492032 I SRV    14: (-----) TCP/IP write error occurred with errno 32

    [2020/03/18@23:00:04.000+0000] P-4518       T-139698841507616 I ABL    59: (49)    SYSTEM ERROR: Memory violation.

    [2020/03/18@23:00:04.000+0000] P-4518       T-139698841507616 I ABL    59: (439)   ** Save file named core for analysis by Progress Software Corporation.

    [2020/03/18@16:01:26.080-0700] P-3559       T-139739083007744 I SRV    15: (562)   HANGUP signal received.

    [2020/03/18@23:04:11.000+0000] P-4963       T-140132590528288 I ABL    66: (49)    SYSTEM ERROR: Memory violation.

    [2020/03/18@23:04:11.000+0000] P-4963       T-140132590528288 I ABL    66: (439)   ** Save file named core for analysis by Progress Software Corporation.

    [2020/03/18@16:31:29.046-0700] P-16400      T-140602164492032 I SRV    14: (562)   HANGUP signal received.

    Does the above indicate where is happening?

    Server is RHEL 6.2.

    Citrix client on Win 2012 R2.

    I did search in the working dir, session temp dir. Then tried searching starting from the root.

    TIA!

  • As you've surmised, the user is an ABL client process.  Since it's on Windows this changes things a bit.

    A lot depends on what OS version you're running.

    I would open a case with the support center in your region to help you figure out how to get to the bottom of this.

    Meantime look at the pdbfiles articles.  Having the correct pdbfiles in place (depending on version) sometimes makes the difference when trying to generate crash forensics.

    Kenneth S. McIntosh

    Principal Technical Support Engineer

     

     

  • Hi Ken,

    From the log, how were you able to tell it's a client process?

    So strange there is no core file anywhere on the system.

    Thanks for your time.

  • prokb:

    On Windows, antivirus packages can prevent protrace file generation when a Progress process dies.
    If protraces are not being created consider testing excluding the Progress executables in DLC/bin from the antivirus.

  • (-----) Protrace location: <path/to/protrace.PID>

    The message was introduced in V11.7

  • > Server is RHEL 6.2

    Article: Why is a core or protrace file not created when a Progress process abnormally terminates?

    knowledgebase.progress.com/.../000039632

  • Because of the ABL string in before the message:.

    Note: ABL is an ABL client directly connected, so *actually* this is not a Windows user, but rather a Linux user who is connected self-service.

    ABL    59: (439)   ** Save file named core for analysis by Progress Software

    Note that the server also reported the missing user (Indicated by SRV where you saw ABL in the previous line):

    [2020/03/18@15:58:54.041-0700] P-16400      T-140602164492032 I SRV    14: (794)   Usernum 321 terminated abnormally.

    [2020/03/18@15:58:54.042-0700] P-16400      T-140602164492032 I SRV    14: (-----) TCP/IP write error occurred with errno 32

    Research backward in the log for user 321 to find out which user it was and that may provide insight into the working directory of the process.

    Kenneth S. McIntosh

    Principal Technical Support Engineer

     

     

  • Note that if the failing process was connected to the database via TCP/IP, then the core file will be on the client machine from which the TCP/IP connection originated.

  • Hi All,

    Today saw similar entry in the db log. The DB this time is on a Windows box. Both OE 11.3.3.

    SRV     3: (49)    SYSTEM ERROR: Memory violation.

    SRV     3: (14658) Previous message sent on behalf of user 46, server pid 4036, broker pid 6272. (5512)

    SRV     3: (439)   ** Save file named core for analysis by Progress Software Corporation.

    SRV     3: (14658) Previous message sent on behalf of user 46, server pid 4036, broker pid 6272. (5512)

    Still cannot find *core* or *trace* files in the server or client.

    Created a program that has recursion to simulate a core dump and run it inside the app. Indeed it crashed.

    SRV     4: (5407)  WARNING: -nb exceeded. Automatically increasing from 300 to 400.

    SRV     4: (14658) Previous message sent on behalf of user 71, server pid 6872, broker pid 2024. (5512)

    SRV     4: (5635)  SYSTEM ERROR: -s exceeded. Raising STOP condition and attempting to write stack trace to file 'procore'. Consider increasing -s startup parameter.

    This time, however, a procore.pid can be found in the session temp dir of the client.

    What could be special with "SYSTEM ERROR: Memory violation" that it does not create a dump file?

    TIA!

  • Edit %DLC%\promsgs file in hex editor (but first stop Admin Server):

    replace:

    ** Invalid character in numeric input %c. (76)

    by

    %G Invalid character in numeric input %c. (76)

    Then run:

    INTEGER("a").

    The session will die but it will create protrace.PID and procore.PID in its working directory.