IDS Forum

RE: ER crashing ...

Posted By: Andrew Grantham
Date: Wednesday, 31 August 2011, at 5:22 p.m.

In Response To: ER crashing ... (MARK JALKIEWICZ)

Mark, Sorry to sound critical of your words but you have to accept the product for what it is and deal with it. If crap is thrown at the port you are using how about using a different port or find the offending process and stop it sending crap to the port? As you are using an unsupported version you are not going to get much help. We are using 10.00.FC10 at the moment and we do not get network problems at all and it works like a dream. I realise changing the port is a pain in the bum but its not that hard. What port number are you using by the way? Are you sure its unique? Regards Andy G.
> To: ids@iiug.org
> From: mark.jalkiewicz@verizon.net
> Subject: ER crashing ... [24810]
> Date: Wed, 31 Aug 2011 17:08:22 -0400
>
> 10.00.UC9
>
> our ER server is crashing several times a day since yesterday with the
> following Assert Failure:
>
> 14:34:17 Assert Failed: Condition Failed (Bad allocation size (0) for pool
> 'CDR
> ' (0x715f0020)), In (mt_shm_malloc_segid)
> 14:34:17 Who: Session(8180, root@EastServer, 0, 73e27440)
>
> Thread(11568, CDRD_60, 70272a60, 7)
>
> File: mtshpool.c Line: 3218
> 14:34:17 Action: Please notify IBM Informix Technical Support.
> 14:34:17 Stack for thread: 11568 CDRD_60
>
> base: 0x73e7f000
> len: 69632
>
> pc: 0x10070940
> tos: 0x73e8e978
> state: running
>
> vp: 7
>
> 0x10070ad4 (oninit)afstack
> 0x10072344 (oninit)afhandler
> 0x1006c10c (oninit)mem_asfail
> 0x1006eb5c (oninit)mt_shm_malloc_segid
> 0x1006ec80 (oninit)mt_shm_malloc
> 0x10474f4c (oninit)cdr_mt_shm_malloc
> 0x108ccfbc (oninit)rmStreamHdrRead
> 0x108d3348 (oninit)rmiCreateDSCollisionBM
> 0x108d26a0 (oninit)rmiGetNextPendingTxn
> 0x108d9708 (oninit)rmNextMsg
> 0x108cac68 (oninit)dsiResolverThread
> 0x1046b820 (oninit)cdrTrampolineThread
> 0x10abbf98 (oninit)startup
>
> tech has told us we need to "fix" our network as we are getting garbage data
> placed on the port where ER listens. The engine will crash when the following
> is detected on the other server in the ER pair :
>
> 14:39:10 CDR NIF receive failed asfcode: -25582 oserr 0
>
> 14:39:10 CDR connection to server lost, id 11, name <east_serv>
> Reason: connection lost
>
> However we feel that the engine should be able to handle this in a more
> gracefull manner
>
> anyone else thoughs ?
>
>
> *******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>

Messages In This Thread

• ER crashing ...
  MARK JALKIEWICZ -- Wednesday, 31 August 2011, at 5:08 p.m.
  • RE: ER crashing ...
    Andrew Grantham -- Wednesday, 31 August 2011, at 5:22 p.m.
    • RE: ER crashing ...
      Plugge, Joe R. -- Wednesday, 31 August 2011, at 8:18 p.m.
  • Re: ER crashing ...
    Madison Pruet -- Friday, 2 September 2011, at 9:03 a.m.
    • Re: ER crashing ...
      MARK JALKIEWICZ -- Friday, 2 September 2011, at 12:57 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.