Problems with NSD in version 6.5

HCL Domino Domino Forum
1

Hi all!

We have over 500 domino servers (W2000) in all our branches throughout Spain and 100 of them are updated to 6.5 version from 5.0.10.

Daily we stop/start all servers to make a backup at 5:30am. Randomly some servers in 6.5 don’t restart after the backup process and a

nsd*.txt is generated. Inside the file the next appears:

------ Open Databases -------

ERROR (0): exception(0): thread 3e90 got system exception: ACCESS_VIOLATION (3221225477)

ERROR (0): failed while checking type 0x8252 memory

ERROR (0): exception(0): thread 3e90 got system exception: ACCESS_VIOLATION (3221225477)

ERROR (0): failed while checking type 0x8291 memory

Generated Messages:

INFO (0): Using PSAPI DLL

INFO (0): Using NSD profile C:\WINNT\notesnsd.ini

INFO (0): Found 2 Notes processes, matched 1

INFO (0): Using NSD profile nsd.ini

INFO (0): failed to match all of the Notes processes

INFO (0): Starting Debugger

INFO (0): Walk mem for process nservice (3e98)

INFO (0): terminated process [nservice:3e98]

INFO (0): Deleting pid.nbf

WARNING (0): Debugger still attached to 1 processes

ERROR (0): exception(0): thread 3e90 got system exception: ACCESS_VIOLATION (3221225477)

ERROR (0): failed while checking type 0x8252 memory

ERROR (0): exception(0): thread 3e90 got system exception: ACCESS_VIOLATION (3221225477)

ERROR (0): failed while checking type 0x8291 memory

ERROR (0): exception(0): thread 3e90 got system exception: ACCESS_VIOLATION (3221225477)

ERROR (0): failed while checking type 0x831e memory

ERROR (0): exception(0): thread 3e90 got system exception: ACCESS_VIOLATION (3221225477)

ERROR (0): failed while checking type 0x8311 memory

ERROR (0): exception(0): thread 3e90 got system exception: ACCESS_VIOLATION (3221225477)

ERROR (0): failed while checking type 0x8311 memory

Thread 3e90 is owned by nsd.exe.

Threre is no problem with this shutdown and restart in 5.0.10 servers.

In each server we have ScanMail and the Control Manager Agent, both from TrendMicro.

By the moment, our workaround is to kill all processes we see in taskmanager (nsd.exe, nserver and nservice) with pskill and restart the domino service again. After this we can stop/start the service many times perfectly and we can’t reproduce the problem again.

Any solution or idea??

Thanks in advance.

2

Subject: Problems with NSD in version 6.5

Did you update your ScanMail to the version that supports 6.5?

3

Subject: RE: Problems with NSD in version 6.5

We have ScanMail for Lotus Notes 2.6patch1, that supports R6 (http://kb.trendmicro.com/solutions/solutionDetail.asp?solutionID=13524)

4

Subject: For Jim Rouleau - Problems with NSD in version 6.5 -

Jim,any idea??

5

Subject: Not many ideas

I suspect that this might the source of your problem: In each server we have ScanMail and the Control Manager Agent, both from TrendMicro

When the servers are terminated you are probably not terminating the TrendMicro products. This will prevent the shared memory that Domino uses from being released by Windows, so when Domino restarts it is not getting a clean restart … it is using shared memory that is still leftover from the previous session. That shared memory problem is causing Domino to crash and also NSD crashes later trying to analyze the memory.

That is my suspicion anyway. Take a look at the NSD log file. Near the top of the log there is a process table. Look for the process ids for ScanMail and/or Control Manager Agent. In the Handle Table section of the log file look for these process ids in the 1st column. One of the entries will probably have an entry IRIS$MEM$MM which will confirm my suspicion.

The only answer that I can suggest is that these processes must also be terminated. The fact that the crashes are random also indicates this type of problem.

6

Subject: RE: Not many ideas

Jim,you are right in all yuor suspictions.

We have changed the scheduled process that makes the backup to follow this steps:

1- Stop the Domino server

2- Stop/Start Trend Micro Management Infrastructure service

3- Backup nsf files

4- kill any existing nsd.exe in memory

5- Start the Domino Server

Now all 100 servers in R6.5 restart dayly perfectly.

7

Subject: Resolution confirmed by IBM crash team.

We had to remove and reinstall both Trend Scanmail and Domino to resolve this crash. Scan mail datbases didn’t bode well upgrading from 5.011 to 6.5. OK now.

8

Subject: Problems with NSD in version 6.5

Hi,

We have upgraded our domino server 5.0.6a to 6.0.1. After that we can not backup pur databases with third party backup unit. So I think this problem same as our’s. You should search for your backup software for “Support Release 6”.

Regards