Topic
3 replies Latest Post - ‏2013-01-10T14:17:44Z by swlinn
SystemAdmin
SystemAdmin
6772 Posts
ACCEPTED ANSWER

Pinned topic How to read backtrace.txt file

‏2013-01-08T08:41:59Z |
We had a problem with our production appliance (XI50) where it reloads itself because Out of memory. When DataPower reloads, it generate backtrace file where among other says:

Memory redistributed 0x00000ee0 times (possibly OOM) since 20130102T083957Z.
death_action: signum 0x0000000b, si_addr 0x00000007, eip 0x0939e26a, thread 0xee9fbb90
SecsUp 0x000f9984, si_code 0x00000001, xactid 0x03660ca1
Thread 0xee9fbb90: Component=xmlfirewall, Domain=****, Config=****

What does that mean?

On our appliance we have only one application domain and one service running (XML Firewall). When DataPower was reloading it was using 1,3GB (30%) memory and 0% CPU. Load was 60 - 70 transaction per second, so I wouldn't say that there was heavy load.

Does anyone know how to read backtrace file?
Updated on 2013-01-10T14:17:44Z at 2013-01-10T14:17:44Z by swlinn
  • RCW
    RCW
    232 Posts
    ACCEPTED ANSWER

    Re: How to read backtrace.txt file

    ‏2013-01-08T08:51:32Z  in response to SystemAdmin
    You should contact support to investigate the backtrace. The backtrace is not readable for users except for a few parts.
  • SystemAdmin
    SystemAdmin
    6772 Posts
    ACCEPTED ANSWER

    Re: How to read backtrace.txt file

    ‏2013-01-10T09:01:55Z  in response to SystemAdmin
    We opened a PMR, but I would like to know what does Memory redistributed 0x00000ee0 times (possibly OOM) since 20130102T083957Z really mean.
    • swlinn
      swlinn
      1344 Posts
      ACCEPTED ANSWER

      Re: How to read backtrace.txt file

      ‏2013-01-10T14:17:44Z  in response to SystemAdmin
      When the appliance becomes memory starved, it attempts to free any memory that may have been allocated but is not used. In your case it did this 3808 times (xee0) starting at the timestamp provided. If this number were small, it would indicate that you had a temporary memory situation that rectified itself, but with a number this large, it is in an out of memory scenario for a while and continually attempting to do whatever it can to free up memory.

      Regards,
      Steve