Messaging Gateway

 View Only

  • 1.  Messaging Gateway 9.5 - Malloc error while attempting to allocate memory

    Posted Mar 13, 2012 10:18 AM

    Hi everyone!

    If you can help me with this error I will be most appreciate.

    Malloc error while attempting to allocate memory - Already saw the article http://www.symantec.com/docs/HOWTO73122 and I increase the memory to 8GB on the virtual machine and 2GB for the Esx.

    After a while, the problem appears again. Any ideas?

    THX!



  • 2.  RE: Messaging Gateway 9.5 - Malloc error while attempting to allocate memory

    Broadcom Employee
    Posted Mar 13, 2012 02:30 PM

    Can you explain what you mean by 8Gb for the virtual machine and 2Gb for the ESX?



  • 3.  RE: Messaging Gateway 9.5 - Malloc error while attempting to allocate memory

    Posted Mar 13, 2012 03:20 PM

    Yes of course,

    SMG: 7GB (virtual machine ).

    ESX: 2GB

    Physical server: 9

    Swap free: 4GB

    Swap usage: 0.08 Mb



  • 4.  RE: Messaging Gateway 9.5 - Malloc error while attempting to allocate memory

    Broadcom Employee
    Posted Mar 13, 2012 03:52 PM

    I am not sure how accomplished 9Gb of memory, but what you posted should work fine. What was allocated to the Messaging Gateway before? Have you logged in as the support user and run 'top' so see a snapshot of the memory usage?



  • 5.  RE: Messaging Gateway 9.5 - Malloc error while attempting to allocate memory
    Best Answer

    Posted Mar 27, 2012 05:53 AM

    Hi,

     

    I hope this KB helps clarifying the issue a bit better:

     

    http://www.symantec.com/docs/HOWTO58882

     

    There is a solution map provided in the article please read through it.

    It might help to restart the MTA in these cases to free up RAM.

    The memory allocated to the appliacne should also be reserved since Memory ballooning and other advanced memory allocation techniques which VmWare would do are not supported by the software.

     

    Shold you be running on version 9.5.3 and still experienceing this issue please open up a support ticket.