Replication problems

I am trying to use Enterprise Replication on 2 HP servers. It seemed to work fine for a few hours. It came down and when I bring Informix up I get the following message and then Informix comes down. (Both systems are the same level of OS and Informix.) 17:57:01 On-Line Mode 17:57:02 Checkpoint Completed: duration was 0 seconds. 17:57:02 CDR catalog verification (repdef) 17:57:02 CDR catalog verification (partdef) 17:57:02 CDR catalog verification (servdef) 17:57:02 CDR catalog verification (pendingstates) 17:57:02 CDR catalog verification (cdr_errors) 17:57:02 CDR catalog verification (replaytab) 17:57:02 CDR catalog verification (recvcntldup) 17:57:02 CDR catalog verification (collectdef) 17:57:02 CDR catalog verification (collpartdef) 17:57:02 CDR catalog verification (cdrstate) 17:57:02 CDR catalog verification (deltabdef) 17:57:02 CDR catalog verification (deltabrep) 17:57:02 CDR catalog verification (freqdef) 17:57:02 CDR catalog verification (servroute) 17:57:02 CDR Catalogs verification complete 17:57:02 CDR GC: catalog recovery begin 17:57:02 CDR GC: server recovery complete 17:57:11 (4) connection rejected - no calls allowed for cdraccept 17:57:11 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 17:57:16 CDR GC: replicate recovery complete 17:57:16 CDR GC: replicate pending state recovery complete 17:57:16 CDR GC: group recovery complete 17:57:16 CDR GC: group pending state recovery complete 17:57:16 CDR GC: delete table recovery complete 17:57:16 CDR GC: delete mapping recovery complete 17:57:16 CDR GC: catalog recovery complete 17:57:16 CDR queuer initialization complete 17:57:17 CDR NIF site: 20 <gr_waco> clocks differ by 21 seconds 17:57:17 Assert Failed: yield_processor: Stack overflow in thread 46 17:57:17 Informix Dynamic Server Version 7.31.FC7 17:57:17 Who: Session(21, informix@poole, 0, 508074032) Thread(46, CDRD_0, c00000001e457e90, 1) File: mt.c Line: 2213 17:57:17 stack trace for pid 1665 written to /tmp/af.4162d4c 18:00:08 See Also: /tmp/af.4162d4c 18:00:08 mt.c, line 2213, thread 46, proc id 1665, yield_processor: Stack overflow in thread 46. 18:00:08 PANIC: Attempting to bring system down 18:00:08 semctl: errno = 22 18:00:08 semctl: errno = 22 18:00:08 semctl: errno = 22 Does anyone had a suggestion. Thanks

Please include the stack. My guess is that the triggers are firing and there is a rather complex stored procedure associated with that trigger. You might be able to increase the stacksize by increasing STACKSIZE in the onconfig. I think that the default size is 32K. You might try to set it to 64K. "Harry Johnson" <hjohnson@keeneinfo.com> wrote in message news:6830f442.0406141510.45f4d2b7@posting.google.com... > I am trying to use Enterprise Replication on 2 HP servers. It seemed to work fine > for a few hours. It came down and when I bring Informix up I get the following > message and then Informix comes down. (Both systems are the same level of OS and > Informix.) > > > 17:57:01 On-Line Mode > 17:57:02 Checkpoint Completed: duration was 0 seconds. > 17:57:02 CDR catalog verification (repdef) > 17:57:02 CDR catalog verification (partdef) > 17:57:02 CDR catalog verification (servdef) > 17:57:02 CDR catalog verification (pendingstates) > 17:57:02 CDR catalog verification (cdr_errors) > 17:57:02 CDR catalog verification (replaytab) > 17:57:02 CDR catalog verification (recvcntldup) > 17:57:02 CDR catalog verification (collectdef) > 17:57:02 CDR catalog verification (collpartdef) > 17:57:02 CDR catalog verification (cdrstate) > 17:57:02 CDR catalog verification (deltabdef) > 17:57:02 CDR catalog verification (deltabrep) > 17:57:02 CDR catalog verification (freqdef) > 17:57:02 CDR catalog verification (servroute) > 17:57:02 CDR Catalogs verification complete > 17:57:02 CDR GC: catalog recovery begin > 17:57:02 CDR GC: server recovery complete > 17:57:11 (4) connection rejected - no calls allowed for cdraccept > 17:57:11 listener-thread: err = -27002: oserr = 0: errstr = : Noconnections ar > e allowed in Dynamic Server quiescent mode. > 17:57:16 CDR GC: replicate recovery complete > 17:57:16 CDR GC: replicate pending state recovery complete > 17:57:16 CDR GC: group recovery complete > 17:57:16 CDR GC: group pending state recovery complete > 17:57:16 CDR GC: delete table recovery complete > 17:57:16 CDR GC: delete mapping recovery complete > 17:57:16 CDR GC: catalog recovery complete > 17:57:16 CDR queuer initialization complete > 17:57:17 CDR NIF site: 20 <gr_waco> clocks differ by 21 seconds > 17:57:17 Assert Failed: yield_processor: Stack overflow in thread 46 > 17:57:17 Informix Dynamic Server Version 7.31.FC7 > 17:57:17 Who: Session(21, informix@poole, 0, 508074032) > Thread(46, CDRD_0, c00000001e457e90, 1) > File: mt.c Line: 2213 > 17:57:17 stack trace for pid 1665 written to /tmp/af.4162d4c > 18:00:08 See Also: /tmp/af.4162d4c > 18:00:08 mt.c, line 2213, thread 46, proc id 1665, yield_processor: Stackoverf > low in thread 46. > 18:00:08 PANIC: Attempting to bring system down > 18:00:08 semctl: errno = 22 > 18:00:08 semctl: errno = 22 > 18:00:08 semctl: errno = 22> > > Does anyone had a suggestion. > > Thanks

"Harry Johnson" <hjohnson@keeneinfo.com> wrote in message news:6830f442.0406141510.45f4d2b7@posting.google.com... > I am trying to use Enterprise Replication on 2 HP servers. It seemed to work fine > for a few hours. It came down and when I bring Informix up I get the following > message and then Informix comes down. (Both systems are the same level of OS and > Informix.) > 17:57:17 Assert Failed: yield_processor: Stack overflow in thread 46 Stack overflow... - increase ONCONFIG parmeter STACKSIZE? - Check kernel parmaters to do with maxiumum stacksize for a process? > 17:57:17 Informix Dynamic Server Version 7.31.FC7 > 17:57:17 Who: Session(21, informix@poole, 0, 508074032) > Thread(46, CDRD_0, c00000001e457e90, 1) > File: mt.c Line: 2213 > 17:57:17 stack trace for pid 1665 written to /tmp/af.4162d4c > 18:00:08 See Also: /tmp/af.4162d4c > 18:00:08 mt.c, line 2213, thread 46, proc id 1665, yield_processor: Stackoverf > low in thread 46. > 18:00:08 PANIC: Attempting to bring system down > 18:00:08 semctl: errno = 22 > 18:00:08 semctl: errno = 22 > 18:00:08 semctl: errno = 22> > > Does anyone had a suggestion. > > Thanks