Thursday, March 29, 2012

SnTT- When log.nsf gets snagged

Sometimes what we know doesn't always work.

Take this situation. Client running an R5 server suddenly gets errors on the console that the log file can not be found or unable to write to it.

It seems the server crashed or had something happen to it and the log.nsf may have become corrupted.

The simple response is to move the bad log.nsf out of the Domino directory entirely so you can review it for what caused the problem. You do this by shutting down the server and physically moving the file, cut and paste style. Domino will start a new log.nsf file on startup if one does not exist and you are good to go.

Not so fast. What if, as it did in this case, the errors persist? Now what do you do?

The answer, in this case, was after reviewing the template was okay and all else looked good was to reboot the server. In this case the client did not want to do this as it was a remote box and no coverage at the time.

You can run, even on old R5 servers, nsd.exe -kill. Yes it was around then. And this will clear any open threads from Notes or Domino and sure enough afer running it and starting up Domino all was good again in the world.

More than one way to solve this but sometimes you need to think about the repercussions before committing to a resolution. What would have happenned if the server never came back online from the reboot? What would you do? What do you tell your client if it didn't work? There are always options.