6.0.1CF Crash

I upgraded from 5.0.5 to 6.0.1CF Domino Server.I had no problems with 5.0.5.Every night at 2.04AM my system crashes. It seems to be when STMP housekeeping is done.Any ideas?

The following error message is logged.

INFO (0): Starting Debugger

WARNING (0): all VPool 8150 pools have been allocated

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [49664: 64205]

ERROR (0): Monitor client data is corrupted

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [897: -1]

ERROR (0): Monitor client data is corrupted

ERROR (0): Monitor client data is corrupted

ERROR (0): Monitor client data is corrupted

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [16901: -1]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [17157: -1]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [18693: -1]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [2053: -1]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [517: -1]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [3845: -1]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [32512: 64205]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [55299: 63735]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [4105: 19968]

ERROR (0): Monitor list data is corrupted

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [898: -1]

ERROR (0): Monitor list data is corrupted

ERROR (0): Monitor list data is corrupted

ERROR (0): Monitor list data is corrupted

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [18949: -1]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [773: -1]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [5125: -1]

ERROR (0): Invalid BBLOCK BLK_NSF_MONITOR_POOL [5893: -1]

ERROR (0): TLSDATA buffer is corrupted bsig=0

ERROR (0): TLSDATA buffer is corrupted esig=0

Subject: 6.0.1CF Crash

Bruce:

We are seeing the same errors and have opened an incident with Lotus. They state we have corrupted data. We were told to shutdown our server and run fixup. Has your problem been resolved?

Subject: RE: 6.0.1CF Crash

Any word from Lotus on this yet?

Subject: RE: 6.0.1CF Crash

They told us not to worry about this message. We are running Domino 6.0.1 under Solaris 9. We noticed that when we were collecting information via NSD for Lotus on another problem that we were getting this error message. Up to that point we thought the error was caused by the server crash. We have an identical server that does not produce the error message. Sorry, that I do not have a better answer but that is all Lotus gave us for now. We are having so many other server crashes that we have not had time to investigate this error.

Subject: 6.0.1CF Crash

We have the same problem here. We have upgradedfrom 5.0.8 to 6.0.1 CF. Every night at 2:00 AM the Domino server crashes. The log you put is very similar to our log.

Did you solved the problem?

Many thanks in advance.

Best regards,

Isaac