Ilogin crashes backend engine

Posted in 1999

Topics: Installation, Setup & Upgrades, Error Codes & Troubleshooting, Server Administration, Versions, Editions & End-of-Life

Keith Fang — 26 Oct 1999 23:06:46 GMT — source: Informix-list mailing list archive (1991-1998)

We currently have two NT/SP4 machine, DB1 running IDS 7.30TC5 as backend server, WEB1 runs I-Connect 9.14 as client. This worked fine for the past 4 months. We then added two more machine (DB2 and WEB2) as backup system with identical Informix installation. After all are in place, we encountered the following situation: WEB1 can successfully ilogin to both DB1 and DB2. WEB2 can successfully ilogin to DB1, but crash the instance on DB2 everytime when we run ilogin. The log on DB2 says: 21:51:36 Informix Dynamic Server Version 7.30.TC5 Software Serial Number AAC#J777797 21:51:36 Assert Failed: No Exception Handler 21:51:36 Who: Session(71, informix@, 0, 0) Thread(9, soctcplst, 0, 1) Exception at Addr: 0x77f64a5c, TOS: 0xc37b54c, FP:0xc37b628, Exc: c0000005 21:51:36 Results: Exception Caught. Type: MT_EX_OS, Context: mem 21:51:36 Action: Please notify Informix Technical Support. We've tried re-install NT and informix on DB2 and then Informix on WEB2 and still seeing this failure. Has anyone seen this before? Can you help? TIA Keith Fang DBA Object Works, Inc.

↪ replying to Keith Fang

Tim Schaefer — Thu, 28 Oct 1999 00:49:58 -0400 — source: Informix-list mailing list archive (1991-1998)

Yes, Switch to UNIX. If you can't switch to UNIX, get Linux. NT: BWAHAHAHAHAHAHAHAHAHAHAHA! :-) Seriously, why waste your time with NT! It's not a real server, just a pretty face for PC-DOS. If you want a real server situation on x86, then why not at least go with a UNIX of some flavor, at the very least Linux. You can use the same hardware, and get more out of it by switching away from NT. Of course you'll have to go through NT-withdrawl but it can be done, not unlike quitting smoking cigarettes. :-) Tim Keith Fang wrote: > > We currently have two NT/SP4 machine, DB1 running IDS 7.30TC5 as backend server, > WEB1 runs I-Connect 9.14 as client. This worked fine for the past 4 months. > We then added two more machine (DB2 and WEB2) as backup system with identical > Informix installation. After all are in place, we encountered the following > situation: WEB1 can successfully ilogin to both DB1 and DB2. WEB2 can successfully > ilogin to DB1, but crash the instance on DB2 everytime when we run ilogin. > > The log on DB2 says: > > 21:51:36 Informix Dynamic Server Version 7.30.TC5 Software Serial Number AAC#J777797 > > 21:51:36 Assert Failed: No Exception Handler > 21:51:36 Who: Session(71, informix@, 0, 0) > Thread(9, soctcplst, 0, 1) > Exception at Addr: 0x77f64a5c, TOS: 0xc37b54c, FP:0xc37b628, Exc: c0000005 > 21:51:36 Results: Exception Caught. Type: MT_EX_OS, Context: mem > 21:51:36 Action: Please notify Informix Technical Support.> > We've tried re-install NT and informix on DB2 and then Informix on WEB2 and still > seeing this failure. Has anyone seen this before? Can you help? > > TIA > > Keith Fang > DBA > Object Works, Inc. -- . .- .-- .--- .---- Tim Schaefer .----- tschaefe@bellsouth.net .---- http://www.inxutil.com .--- http://www.datad.com .-- .- .

↪ replying to Keith Fang

Rainer Ruehs — Thu, 28 Oct 1999 09:37:53 +0200 — source: , line -1, thread 9, proc id 167, No Exception Handler.@@NL@@13:42:38 PANIC: Attempting to bring system down@@NL@@@@NL@@One system failed this way only once. The other (SP5) failed several times@@NL@@in the last@@NL@@two weeks and since two days the server fails every time any client tries to@@NL@@connect.@@NL@@@@NL@@The bug seems to be known at Informix, but we actually got no workaround.@@NL@@@@NL@@R.D. Ruehs@@NL@@@@NL@@Keith Fang schrieb in Nachricht <7v5c66$2sk$1@nntp8.atl.mindspring.net>...@@NL@@>@@NL@@>We currently have two NT/SP4 machine, DB1 running IDS 7.30TC5 as backend@@NL@@server,@@NL@@>WEB1 runs I-Connect 9.14 as client. This worked fine for the past 4 months.@@NL@@>We then added two more machine (DB2 and WEB2) as backup system with@@NL@@identical@@NL@@>Informix installation. After all are in place, we encountered the following@@NL@@>situation: WEB1 can successfully ilogin to both DB1 and DB2. WEB2 can@@NL@@successfully@@NL@@>ilogin to DB1, but crash the instance on DB2 everytime when we run ilogin.@@NL@@>@@NL@@>The log on DB2 says:@@NL@@>@@NL@@>21:51:36 Informix Dynamic Server Version 7.30.TC5 Software Serial Number@@NL@@AAC#J777797@@NL@@>@@NL@@>21:51:36 Assert Failed: No Exception Handler@@NL@@>21:51:36 Who: Session(71, informix@, 0, 0)@@NL@@> Thread(9, soctcplst, 0, 1)@@NL@@> Exception at Addr: 0x77f64a5c, TOS: 0xc37b54c, FP:0xc37b628, Exc: c0000005@@NL@@>21:51:36 Results: Exception Caught. Type: MT_EX_OS, Context: mem@@NL@@>21:51:36 Action: Please notify Informix Technical Support.@@NL@@>@@NL@@>We've tried re-install NT and informix on DB2 and then Informix on WEB2 and@@NL@@still@@NL@@>seeing this failure. Has anyone seen this before? Can you help?@@NL@@>@@NL@@>TIA@@NL@@>@@NL@@>Keith Fang@@NL@@>DBA@@NL@@>Object Works, Inc.@@NL@@>

We have two customers with the same Problem. Both are running IDS 7.30.TC9 as backend server on NT/SP5 (one is SP4) and are using an ESQL/C 7.20-frontend application. 13:42:22 Assert Failed: No Exception Handler 13:42:22 Informix Dynamic Server Version 7.30.TC9 13:42:22 Who: Session(625, informix@, 0, 0) Thread(9, soctcplst, 0, 1) Exception at Addr: 0x77f8d32f, TOS: 0xdc3555c, FP:0xdc35578, Exc: c0000005 13:42:22 Results: Exception Caught. Type: MT_EX_OS, Context: mem 13:42:22 Action: Please notify Informix Technical Support. 13:42:37 See Also: af.9a1ae, shmem.9a1ae.0 13:42:38 \

Glossary

IDS (Informix Dynamic Server)