Oninit cdi / Archive
Talk to an expert →

Engine blocked - Not allowed connections

Posted in 2013

Summary

A user's IDS 7.31.TD6 test instance on Windows hung in blocked-waiting-for-checkpoint state; onmode -c and onmode -l (switching logs) didn't free it. oncheck -cR with the server down reported many "Log page error: invalid unique ID (pg_next)" messages across most logical logs, plus earlier "Buffer manager internal error" asserts in the online log. Art Kagel diagnosed corrupted logical logs (possibly a damaged/overwritten chunk), noted the logs were being backed up to /dev/null so nothing could be recovered, and advised restoring from an archive, accepting the lost transactions; adding new logs and dropping the old ones might work but probably not if the chunk itself is corrupt. He also suggested the very old version/platform be upgraded. No confirmed resolution is recorded.

Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.

Topics: Server Administration, Logging & Checkpoints, Versions, Editions & End-of-Life

GUSTAVO ECHENIQUE — — source: IIUG Forums & Mailing Lists

Hello people of the forum! Another time me and my problems. I have an Informix IDS 7.31 TD6 for Windows. On Friday stopped working, and I know why. Now let me know which is blocked waiting for a CKPT, but I tested with onmode-c command to block and unblock options and it is not. It takes one or two minutes to make the checkpoint but still in the same state. I also moved the active log logical onmode-l, and then forced the checkpoint with the above options, but did not succeed. Would one has been the same?, If I could help I would be grateful. Greetings! Gustavo Echenique

↪ replying to GUSTAVO ECHENIQUE
Art Kagel — — source: IIUG Forums & Mailing Lists

Did you back up the logical logs? Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Sep 2, 2013 at 5:51 PM, GUSTAVO ECHENIQUE < gustavo.echenique@cemdo.com.ar> wrote: > Hello people of the forum! > > Another time me and my problems. > I have an Informix IDS 7.31 TD6 for Windows. On Friday stopped working, > and I > know why. > Now let me know which is blocked waiting for a CKPT, but I tested with > onmode-c command to block and unblock options and it is not. It takes one > or > two minutes to make the checkpoint but still in the same state. > I also moved the active log logical onmode-l, and then forced the > checkpoint > with the above options, but did not succeed. > > Would one has been the same?, If I could help I would be grateful. > > Greetings! > > Gustavo Echenique > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a11c373e45ec07804e56edf10

↪ replying to Art Kagel
GUSTAVO ECHENIQUE — — source: IIUG Forums & Mailing Lists

Hi Art! If I do a backup in continuous mode the logical logs to a null device. When I ran the oncheck-cR with the engine down, I returned the following: "shared memory not initialized for INFORMIXSERVER 'ol_develop' Validating Informix Dynamic Server reserved pages Validating PAGE_PZERO... Validating PAGE_CONFIG... ONCONFIG config file error on element NUMAIOVPS. Value in reserved page: 1 Value in config file: 16 Validating PAGE_1CKPT & PAGE_2CKPT... Using check point page PAGE_1CKPT. Validating physical log pages ... Validating logical logs ... Log page error: invalid unique ID (pg_next). Log number 1, addr 0xa03235 Log page error: invalid unique ID (pg_next). Log number 2, addr 0xa06435 Log page error: invalid unique ID (pg_next). Log number 5, addr 0xa2c635 Log page error: invalid unique ID (pg_next). Log number 6, addr 0xa2f835 Log page error: invalid unique ID (pg_next). Log number 7, addr 0xa32a35 Log page error: invalid unique ID (pg_next). Log number 8, addr 0xa35c35 Log page error: invalid unique ID (pg_next). Log number 9, addr 0xa38e35 Log page error: invalid unique ID (pg_next). Log number 10, addr 0xa3c035 Log page error: invalid unique ID (pg_next). Log number 11, addr 0xa00035 Log page error: invalid unique ID (pg_next). Log number 12, addr 0xa0a035 Log page error: invalid unique ID (pg_next). Log number 13, addr 0xa0d235 Log page error: invalid unique ID (pg_next). Log number 14, addr 0xa10435 Log page error: invalid unique ID (pg_next). Log number 15, addr 0xa13635 Log page error: invalid unique ID (pg_next). Log number 16, addr 0xa16835 Log page error: invalid unique ID (pg_next). Log number 17, addr 0xa19a35 Log page error: invalid unique ID (pg_next). Log number 18, addr 0xa1cc35 Log page error: invalid unique ID (pg_next). Log number 19, addr 0xa1fe35 Log page error: invalid unique ID (pg_next). Log number 20, addr 0xa23035 Validating PAGE_1DBSP & PAGE_2DBSP... Using DBspace page PAGE_1DBSP. Validating PAGE_1PCHUNK & PAGE_2PCHUNK... Using primary chunk page PAGE_1PCHUNK. Validating PAGE_1ARCH & PAGE_2ARCH... Using archive page PAGE_2ARCH." Greetings! Gustavo

↪ replying to GUSTAVO ECHENIQUE
Art Kagel — — source: IIUG Forums & Mailing Lists

It looks like something corrupted your logical logs! Make sure that no one has done something like build a filesystem over one of your chunk devices. You may have to restore from a recent archive and bite the bullet to lose the transactions on those logical logs! Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Sep 2, 2013 at 6:48 PM, GUSTAVO ECHENIQUE < gustavo.echenique@cemdo.com.ar> wrote: > Hi Art! > > If I do a backup in continuous mode the logical logs to a null device. > > When I ran the oncheck-cR with the engine down, I returned the following: > > "shared memory not initialized for INFORMIXSERVER 'ol_develop' > > Validating Informix Dynamic Server reserved pages > > Validating PAGE_PZERO... > > Validating PAGE_CONFIG... > > ONCONFIG config file error on element NUMAIOVPS. > > Value in reserved page: 1 > > Value in config file: 16 > > Validating PAGE_1CKPT & PAGE_2CKPT... > > Using check point page PAGE_1CKPT. > > Validating physical log pages ... > > Validating logical logs ... > Log page error: invalid unique ID (pg_next). Log number 1, addr 0xa03235 > Log page error: invalid unique ID (pg_next). Log number 2, addr 0xa06435 > Log page error: invalid unique ID (pg_next). Log number 5, addr 0xa2c635 > Log page error: invalid unique ID (pg_next). Log number 6, addr 0xa2f835 > Log page error: invalid unique ID (pg_next). Log number 7, addr 0xa32a35 > Log page error: invalid unique ID (pg_next). Log number 8, addr 0xa35c35 > Log page error: invalid unique ID (pg_next). Log number 9, addr 0xa38e35 > Log page error: invalid unique ID (pg_next). Log number 10, addr 0xa3c035 > Log page error: invalid unique ID (pg_next). Log number 11, addr 0xa00035 > Log page error: invalid unique ID (pg_next). Log number 12, addr 0xa0a035 > Log page error: invalid unique ID (pg_next). Log number 13, addr 0xa0d235 > Log page error: invalid unique ID (pg_next). Log number 14, addr 0xa10435 > Log page error: invalid unique ID (pg_next). Log number 15, addr 0xa13635 > Log page error: invalid unique ID (pg_next). Log number 16, addr 0xa16835 > Log page error: invalid unique ID (pg_next). Log number 17, addr 0xa19a35 > Log page error: invalid unique ID (pg_next). Log number 18, addr 0xa1cc35 > Log page error: invalid unique ID (pg_next). Log number 19, addr 0xa1fe35 > Log page error: invalid unique ID (pg_next). Log number 20, addr 0xa23035 > > Validating PAGE_1DBSP & PAGE_2DBSP... > > Using DBspace page PAGE_1DBSP. > > Validating PAGE_1PCHUNK & PAGE_2PCHUNK... > > Using primary chunk page PAGE_1PCHUNK. > > Validating PAGE_1ARCH & PAGE_2ARCH... > > Using archive page PAGE_2ARCH." > > Greetings! > > Gustavo > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a11c3db74f7b87b04e56f5ed9

↪ replying to GUSTAVO ECHENIQUE
Art Kagel — — source: IIUG Forums & Mailing Lists

Especially since you are not backing up the logs to disk or to tape but discarding them! Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Sep 2, 2013 at 6:59 PM, Art Kagel <art.kagel@gmail.com> wrote: > It looks like something corrupted your logical logs! Make sure that no > one has done something like build a filesystem over one of your chunk > devices. > > You may have to restore from a recent archive and bite the bullet to lose > the transactions on those logical logs! > > Art > > > Art S. Kagel > Advanced DataTools (www.advancedatatools.com) > Blog: http://informix-myview.blogspot.com/ > > Disclaimer: Please keep in mind that my own opinions are my own opinions > and do not reflect on my employer, Advanced DataTools, the IIUG, nor any > other organization with which I am associated either explicitly, > implicitly, or by inference. Neither do those opinions reflect those of > other individuals affiliated with any entity with which I am affiliated nor > those of the entities themselves. > > > On Mon, Sep 2, 2013 at 6:48 PM, GUSTAVO ECHENIQUE < > gustavo.echenique@cemdo.com.ar> wrote: > >> Hi Art! >> >> If I do a backup in continuous mode the logical logs to a null device. >> >> When I ran the oncheck-cR with the engine down, I returned the following: >> >> "shared memory not initialized for INFORMIXSERVER 'ol_develop' >> >> Validating Informix Dynamic Server reserved pages >> >> Validating PAGE_PZERO... >> >> Validating PAGE_CONFIG... >> >> ONCONFIG config file error on element NUMAIOVPS. >> >> Value in reserved page: 1 >> >> Value in config file: 16 >> >> Validating PAGE_1CKPT & PAGE_2CKPT... >> >> Using check point page PAGE_1CKPT. >> >> Validating physical log pages ... >> >> Validating logical logs ... >> Log page error: invalid unique ID (pg_next). Log number 1, addr 0xa03235 >> Log page error: invalid unique ID (pg_next). Log number 2, addr 0xa06435 >> Log page error: invalid unique ID (pg_next). Log number 5, addr 0xa2c635 >> Log page error: invalid unique ID (pg_next). Log number 6, addr 0xa2f835 >> Log page error: invalid unique ID (pg_next). Log number 7, addr 0xa32a35 >> Log page error: invalid unique ID (pg_next). Log number 8, addr 0xa35c35 >> Log page error: invalid unique ID (pg_next). Log number 9, addr 0xa38e35 >> Log page error: invalid unique ID (pg_next). Log number 10, addr 0xa3c035 >> Log page error: invalid unique ID (pg_next). Log number 11, addr 0xa00035 >> Log page error: invalid unique ID (pg_next). Log number 12, addr 0xa0a035 >> Log page error: invalid unique ID (pg_next). Log number 13, addr 0xa0d235 >> Log page error: invalid unique ID (pg_next). Log number 14, addr 0xa10435 >> Log page error: invalid unique ID (pg_next). Log number 15, addr 0xa13635 >> Log page error: invalid unique ID (pg_next). Log number 16, addr 0xa16835 >> Log page error: invalid unique ID (pg_next). Log number 17, addr 0xa19a35 >> Log page error: invalid unique ID (pg_next). Log number 18, addr 0xa1cc35 >> Log page error: invalid unique ID (pg_next). Log number 19, addr 0xa1fe35 >> Log page error: invalid unique ID (pg_next). Log number 20, addr 0xa23035 >> >> Validating PAGE_1DBSP & PAGE_2DBSP... >> >> Using DBspace page PAGE_1DBSP. >> >> Validating PAGE_1PCHUNK & PAGE_2PCHUNK... >> >> Using primary chunk page PAGE_1PCHUNK. >> >> Validating PAGE_1ARCH & PAGE_2ARCH... >> >> Using archive page PAGE_2ARCH." >> >> Greetings! >> >> Gustavo >> >> >> >> ******************************************************************************* >> Forum Note: Use "Reply" to post a response in the discussion forum. >> >> > --001a11c264a411cbd004e56f6174

↪ replying to Art Kagel
GUSTAVO ECHENIQUE — — source: IIUG Forums & Mailing Lists

Hi Art! Sorry for the delay in responding, but last night I went home and did not see your last posts. The server in question is a test server, which I use a lot to avoid overloading the production server, so it is important to record the logical logs. But I wonder if I have any way to recover the instance to not have to reinstall the same and import the data with dbimport, since almost 24 hours consuming task. I had thought of creating new logical logs, and go deleting the old ones. Do you think it a good idea? Greetings! Gustavo Echenique

↪ replying to GUSTAVO ECHENIQUE
Art Kagel — — source: IIUG Forums & Mailing Lists

You can try, but if the chunk is corrupt ypu may not be able to drop the logs. Art On Sep 3, 2013 8:27 AM, "GUSTAVO ECHENIQUE" <gustavo.echenique@cemdo.com.ar> wrote: > Hi Art! > Sorry for the delay in responding, but last night I went home and did not > see > your last posts. > The server in question is a test server, which I use a lot to avoid > overloading the production server, so it is important to record the logical > logs. But I wonder if I have any way to recover the instance to not have to > reinstall the same and import the data with dbimport, since almost 24 hours > consuming task. > I had thought of creating new logical logs, and go deleting the old ones. > Do > you think it a good idea? > > Greetings! > > Gustavo Echenique > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a11c352aafe39a304e57c5f12

↪ replying to Art Kagel
GUSTAVO ECHENIQUE — — source: IIUG Forums & Mailing Lists

Hi Art! I was checking the engine log, and the day 31/07/2013 are these errors: "Wed Jul 31 13:05:37 2013 13:05:37 Environment variable CLNT_PAM_CAPABLE is too long (maximum is -1 characters). 13:05:37 File: \\\\tristarm\\\\oslib\\\\osenv.c, line: 1840, status: -5. 13:05:37 Environment variable CLNT_PAM_CAPABLE is too long (maximum is -1 characters). 13:05:37 File: \\\\tristarm\\\\oslib\\\\osenv.c, line: 1840, status: -5." The Last news of the failure, the 30/08/2013 the beginning of the mistakes was this: "Fri Aug 30 00:08:43 2013 00:08:43 Checkpoint Completed: duration was 0 seconds. 00:08:43 Checkpoint loguniq 164, logpos 0x94b018 11:16:43 Checkpoint Completed: duration was 0 seconds. 11:16:43 Checkpoint loguniq 164, logpos 0x9f464c 14:03:43 Assert Failed: Buffer manager internal error 14:03:43 Informix Dynamic Server Version 7.31.TD6 14:03:43 Who: Session(1, informix@PROLIANT.cemdo.com.ar, 0, 0) Thread(6, main_loop(), 0, 1) File: \\\\tristarm\\\\rsam\\\\rsbuff.c Line: 135 14:03:43 Results: 14:03:43 Action: Internally corrected 14:03:47 See Also: af.3eed06f 14:03:47 Buffer manager internal error 14:03:47 Assert Failed: Buffer manager internal error 14:03:47 Informix Dynamic Server Version 7.31.TD6 14:03:47 Who: Session(1, informix@PROLIANT.cemdo.com.ar, 0, 0) Thread(6, main_loop(), 0, 1) File: \\\\tristarm\\\\rsam\\\\rsbuff.c Line: 135 14:03:47 Results: 14:03:47 Action: Internally corrected 14:03:50 See Also: af.3eed06f 14:03:50 Buffer manager internal error 14:03:50 Assert Failed: Buffer manager internal error 14:03:50 Informix Dynamic Server Version 7.31.TD6 14:03:50 Who: Session(1, informix@PROLIANT.cemdo.com.ar, 0, 0) Thread(6, main_loop(), 0, 1) File: \\\\tristarm\\\\rsam\\\\rsbuff.c Line: 135 14:03:50 Results: 14:03:50 Action: Internally corrected 14:03:53 See Also: af.3eed06f" Sent you this information if you can guide to find the error. From already, thank you very much!

↪ replying to GUSTAVO ECHENIQUE
Art Kagel — — source: IIUG Forums & Mailing Lists

I don't know what the problem is except to say that this is a VERY old version of Informix and it's running on Windows. Consider upgrading and possibly migrating the server to Linux. Art On Sep 3, 2013 12:34 PM, "GUSTAVO ECHENIQUE" < gustavo.echenique@cemdo.com.ar> wrote: > Hi Art! > > I was checking the engine log, and the day 31/07/2013 are these errors: > > "Wed Jul 31 13:05:37 2013 > > 13:05:37 Environment variable CLNT_PAM_CAPABLE is too long (maximum is -1 > characters). > 13:05:37 File: \\\\tristarm\\\\oslib\\\\osenv.c, line: 1840, status: -5. > 13:05:37 Environment variable CLNT_PAM_CAPABLE is too long (maximum is -1 > characters). > 13:05:37 File: \\\\tristarm\\\\oslib\\\\osenv.c, line: 1840, status: -5." > > The Last news of the failure, the 30/08/2013 the beginning of the mistakes > was > this: > > "Fri Aug 30 00:08:43 2013 > > 00:08:43 Checkpoint Completed: duration was 0 seconds. > 00:08:43 Checkpoint loguniq 164, logpos 0x94b018 > > 11:16:43 Checkpoint Completed: duration was 0 seconds. > 11:16:43 Checkpoint loguniq 164, logpos 0x9f464c > > 14:03:43 Assert Failed: Buffer manager internal error > 14:03:43 Informix Dynamic Server Version 7.31.TD6 > 14:03:43 Who: Session(1, informix@PROLIANT.cemdo.com.ar, 0, 0) > > Thread(6, main_loop(), 0, 1) > > File: \\\\tristarm\\\\rsam\\\\rsbuff.c Line: 135 > 14:03:43 Results: > 14:03:43 Action: Internally corrected > 14:03:47 See Also: af.3eed06f > 14:03:47 Buffer manager internal error > 14:03:47 Assert Failed: Buffer manager internal error > 14:03:47 Informix Dynamic Server Version 7.31.TD6 > 14:03:47 Who: Session(1, informix@PROLIANT.cemdo.com.ar, 0, 0) > > Thread(6, main_loop(), 0, 1) > > File: \\\\tristarm\\\\rsam\\\\rsbuff.c Line: 135 > 14:03:47 Results: > 14:03:47 Action: Internally corrected > 14:03:50 See Also: af.3eed06f > 14:03:50 Buffer manager internal error > 14:03:50 Assert Failed: Buffer manager internal error > 14:03:50 Informix Dynamic Server Version 7.31.TD6 > 14:03:50 Who: Session(1, informix@PROLIANT.cemdo.com.ar, 0, 0) > > Thread(6, main_loop(), 0, 1) > > File: \\\\tristarm\\\\rsam\\\\rsbuff.c Line: 135 > 14:03:50 Results: > 14:03:50 Action: Internally corrected > 14:03:53 See Also: af.3eed06f" > > Sent you this information if you can guide to find the error. > > >From already, thank you very much! > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e0158c410b3f9f704e57ef8be

Glossary