Unsolved
This post is more than 5 years old
11 Posts
0
2427
July 3rd, 2006 08:00
GSS Legato authentication messages
Hi all,
I've read prior posts enough to know there are "some glitches" with the new authentication mecahanism. With NW server 7.3 running on Solaris 2.8 I found a bunch of GSS Legato authentication messages in the daemon.log file today:
07/03/06 03:31:17 nsrexecd: GSS Legato authentication user session entry (warning): "User authentication session timed out and is now invalid.". Session number = 1e14a:2657, domain = NT AUTHORITY, user name = SYSTEM, NetWorker Instance Name = windozclt1.d2d.com
07/03/06 03:31:17 nsrexecd: GSS Legato authentication user session entry (warning): "User authentication session timed out and is now invalid.". Session number = 1e1a0:2e4, domain = NT AUTHORITY, user name = SYSTEM, NetWorker Instance Name = windozclt2.d2d.com
These continue about a half dozen times until 5 minutes later the message changes to have the NW server as the NW Instance Name. The messages continue about every 10 minutes or so. Meanwhile, the save group that should have been running since the messages started has never completed and nsr_shutdown is ineffective in stopping the nsr binaries on the server.
Anyone seen similar behavior before?
Thank you.
I've read prior posts enough to know there are "some glitches" with the new authentication mecahanism. With NW server 7.3 running on Solaris 2.8 I found a bunch of GSS Legato authentication messages in the daemon.log file today:
07/03/06 03:31:17 nsrexecd: GSS Legato authentication user session entry (warning): "User authentication session timed out and is now invalid.". Session number = 1e14a:2657, domain = NT AUTHORITY, user name = SYSTEM, NetWorker Instance Name = windozclt1.d2d.com
07/03/06 03:31:17 nsrexecd: GSS Legato authentication user session entry (warning): "User authentication session timed out and is now invalid.". Session number = 1e1a0:2e4, domain = NT AUTHORITY, user name = SYSTEM, NetWorker Instance Name = windozclt2.d2d.com
These continue about a half dozen times until 5 minutes later the message changes to have the NW server as the NW Instance Name. The messages continue about every 10 minutes or so. Meanwhile, the save group that should have been running since the messages started has never completed and nsr_shutdown is ineffective in stopping the nsr binaries on the server.
Anyone seen similar behavior before?
Thank you.
No Events found!
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
July 3rd, 2006 08:00
kdonate
11 Posts
0
July 3rd, 2006 08:00
I'm in the process of manually killing the nsr* server processes. ick!
cfowler2
14 Posts
0
September 19th, 2006 11:00
message:
09/19/06 10:20:50 nsrexecd: GSS Legato authentication user session entry (warning): "User authentication session timed out and is now invalid.". Session number = 0:2db, domain = NT AUTHORITY, user name = SYSTEM, NetWorker Instance Name = server.domain
Server: Windows Server 2003 SP1
NW Version: 7.3.2
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 19th, 2006 12:00
These messages are rather noisy, but most of the time, at least myself, I could not see them causing problems. They are part of new auth method towards session handshake system introduced by 7.3.x and given message should be rather informative. It might be that in future releases there will be switch (or it will be done by design) to suppress them.