I support a handful of Domino environments and I have not seen (or noticed) this on any other server in the past… EVERY 30 seconds I get this on my Server1/Acme Domino console: Opened session for Server1/Acme. It is as if the Domino server either (1) cannot resolve it’s own name and/or (2) is attempting to connect to itself. It is a Windows 2003 box running all the latest SPs and patches… we just built it a few weeks ago. It is also running BES 5.
I have searched the Notes 6 and 7 forum and this forum as well… did not find anything useful so far. I know I can make the error go away (set config Log_Sessions=0) but I will not be satisfied with that.
Here is what I have done so far…
-
I logged on to no less than 4 others servers (one of which is running BES) and turned on session logging (set config Log_Sessions=1) on all of them. I watched the console and checked the log.nsf file. None of the servers (including the one with BES) exibited this behavior.
-
I searched the ini, Server document and Configuration document for the string ‘30’ (without the ‘’ characters) and found nothing useful.
-
I looked at the ini file and did a show tasks to figure out what tasks were running under Domino. I then shut each one down to see if I could isolate the one that would make the problem go away (i.e. shut down task1… wait… continue to see Opened session for Server1/Acme… shut down task2… wait… etc). I literally shut down everything (amgr, replica, upate, sched, calconn, http, smtp, router, adminp, rnrmgr) and still, the message persisted. I then reloaded all of the tasks.
-
I read the post in the 6/7 forum and verified that all of my server name fields match (basics tab, location section, ports tab, etc).
-
I read the post in the 6/7 forum about this being normal with amgr running. Not so… at least not so in 8.5.1 as I shut that task down (see above).
I do not think it is a big deal; but, it really bugs me. I want my servers to run clean and this just does not seem normal.
Hoping someone can help…
Chad DeMeyers