Consistency check make domino crasch

HCL Domino Domino Forum
1

Just upgrade from 8.0.2 to 8.5 on win 2008 64bit OS. Got some problem after the installation and had to reset the server. Now it seems that some databases did take some damage so Domino wants to run a “consistency check” on all databases and that makes domino crash.

I have to log on to the server and manually start the domino service after crach. After like 30sek-1min the server crach again…

What should I do? Delete all databases and replicate all of it from the other server that we have? We have all of the databases there to.

2

Subject: Post Fatal callstack from NSD

Open the NSD created by the crash and search for “Fatal.” Please post the associated callstack.

3

Subject: For the benefits of others, can you …

Hi,

For the benefits of others, can you post the FATAL THREAD section of the NSD files with the few lines under it

For example:

############################################################

FATAL THREAD 1/2 [ domdsm:107a8:67076]

FP=0x0012a34c, PC=0x60069a86, SP=0x0012a2f0, stksize=92

EAX=0x01a3088c, EBX=0x01a48650, ECX=0x0000bffe, EDX=0x01a325e6

ESI=0x00004000, EDI=0x0032ff78, CS=0x0000001b, SS=0x00000023

DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010206

Exception code: c0000005 (ACCESS_VIOLATION)

############################################################

@[ 1] 0x60069a86 nnotes._fdDelete@4+118 (4000,12a368,608770ef,4000)

@[ 2] 0x60069a0c nnotes._OSFileClose@4+12 (4000,12adc0,12a380,60872ea7)

@[ 3] 0x608770ef nnotes._sqloclose+15 (4000,12b59c,5010,0)

@[ 4] 0x60872ea7 nnotes._sqlpgclf+71 (12adc0,1aaa2cb,70,1aaa2f3)

@[ 5] 0x60885458 nnotes._sqlpgfdl+616 (12b9a4,1aaa2cb,41,12be44)

@[ 6] 0x60876a6f nnotes._sqlpgcdl+927 (12bf44,12b9a4,0,12be44).

Date

Topic

Frequently asked question - How to analyze Notes/Domino NSDs? (Jean-Yves Riverin)

JYR

4

Subject: nrouter

thread 3/41: [ nrouter: 0fd8: 12e8

one of them…

5

Subject: a little bit more details…

Hi,

You need to post a little bit more details like this example. Search for FATAL THREAD in your NSD.

############################################################

FATAL THREAD 1/2 [ domdsm:107a8:67076]

FP=0x0012a34c, PC=0x60069a86, SP=0x0012a2f0, stksize=92

EAX=0x01a3088c, EBX=0x01a48650, ECX=0x0000bffe, EDX=0x01a325e6

ESI=0x00004000, EDI=0x0032ff78, CS=0x0000001b, SS=0x00000023

DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010206

Exception code: c0000005 (ACCESS_VIOLATION)

############################################################

@[ 1] 0x60069a86 nnotes._fdDelete@4+118 (4000,12a368,608770ef,4000)

@[ 2] 0x60069a0c nnotes._OSFileClose@4+12 (4000,12adc0,12a380,60872ea7)

@[ 3] 0x608770ef nnotes._sqloclose+15 (4000,12b59c,5010,0)

@[ 4] 0x60872ea7 nnotes._sqlpgclf+71 (12adc0,1aaa2cb,70,1aaa2f3)

@[ 5] 0x60885458 nnotes._sqlpgfdl+616 (12b9a4,1aaa2cb,41,12be44)

@[ 6] 0x60876a6f nnotes._sqlpgcdl+927 (12bf44,12b9a4,0,12be44).

6

Subject: Open a PMR but also send me the NSD so I can look at the Crash…

jpaganet@us.ibm.com

7

Subject: Run fixup with the server down

Open a CMD prompt, cd to the executables directory e.g c:\program files\ibm\lotus\dominoand enter nfixup

This should run a consistency check on all databases without the server running and it should complete without failing.

8

Subject: platform_statistics

Thanks for all responses. Seemed to be OS related. IBM wonder if I had this entry below and I didn’t;“SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009”

Then I used PLATFORM_STATISTICS_DISABLED=1 to ignore that reg entry. The server worked much longer but finished with a crash again. I reinstalled the OS and the domino server.

Now it works fine.