HCL Notes and Domino 9.0 Social Edition Forum

Oct 12, 2016, 12:26 AM

34 Posts

Adding to what Barry already said

A couple comments on troubleshooting for you.

1: Based on what you've described you do not need to recreate the busytime dB (slides 37 & 38). The issue is seeing and processing requests and not related to bad data in the busytime database.

2: You should set the following INIs on Server B:

DEBUG_RNRMGR=25 (or 89)
CSLogAutoprocess=1
CSReportErrors=1

If Server B is running 8.53 or later then the setting will take effect immediately. If Server B is running pre-8.53 release then you need to restart the task manually for the setting to take effect. The value 25 will cause RnRMgr to do some basic logging and call tracing along with logging as it processes each request it is told about. The value 89 will do the same and include some cluster related logging as well. Either should help. The other 2 INIs enable logging from the core autoprocessing logic that RnRMgr calls.

Now create a test request for both rooms (the one with no owner setting and the one with the owners). Watch the console for output like this:

ProcessRnRDocs> There are 5 entry notices to process this pass
ProcessRnRDocs> Processing notice 0 for UNID OFBF158B43:A68A51B4-ON07258029:00176AD2
ProcessRnRDocs> Processing UNID OFBF158B43:A68A51B4-ON07258029:00176AD2 for room/resource Room A/My Site
[C&S] R&R Blocker doc detected. Allowing to pass
[C&S] Setting AP Mode to 6
[C&S] Attempting to autoprocess NT000EB416
AP Mode: 3 NoticeType: I
[C&S] Autoprocessing is allowed
[C&S AUTOPROCESSING] Total Time -> 89 ms
ProcessRnRDocs> Done processing. bNoKeepDoc=0

See what your system actually logs and if there is any information that can help you figure out why the requests are just sitting idle. If you are not sure, post the trace output to this thread and I can take a look at what is going on.

If you run a test and see no ProcesRnRDocs message on the console but you see the Router delivered the request (or it replicates over from Server A) then restart RnRMgr if you did not earlier and watch for a debug message from SetCalendarEventNotification. That will tell us if RnRMgr has asked Domino for notifications about changes to the R&R dB or not. You should see something like:

CheckDbForCalendarEvents> Checking database Resource.nsf
CheckDbForCalendarEvents> Setting event notification to directory manager for database Resource.nsf
SetCalendarEventNotification> Asking for notification of updates to database Resource.nsf

If you see a message like:

SetCalendarEventNotification> Asking for no notification of updates to database Resource.nsf
or
CheckDbForCalendarEvents> Found no room/resource calendar profiles in database Resource.nsf. Not registering for notifications.

then something made RnRMgr decide the database is not one it should monitor and process requests in. The cause should be logged somewhere after the "Checking database" line.

Bruce
IBM

By Role

Question