Okay, we'll schedule the outage and rebuild for after the break. On Dec 22, 2010, at 2:27 PM, David E. Martin wrote:
In talking with Dan, it seems like the work-around is the best way to go. With Jini checking tickets and Dan available for backup, users will only be minimally affected by the problem. The 45 minute outage isn't a huge problem, but I'm not comfortable starting to poke deeply into Crypto-Server right before the break.
-David
On 12/22/10 11:41 AM, Dan Olson wrote:
Update:
Cryptocard is sending me some troubleshooting steps to perform. One of them is to restart replication using their method which will require an outage of about 45 minutes.
I'm implementing a workaround for the current situation as follows: The crypto server will send mail to a mailing list consisting of the crypto server operators when it disables any corrupt token. The monitor script will start a validation process when a token is detected as corrupt which will correct the checksum so the token will be visible in the console, marked disabled. When we receive the mails we can mark the token enabled, which should allow the user to successfully logon without reinitializing the token.
The best window for the downtime before the break would be late this evening, if we can't get the downtime this evening, I recommend using the workaround until the new year. In its current state our exposure to this issue appears to be limited to less than 10 users per week. I will be checking the disabled token emails at least daily over the break. Also, if anyone has any issues over the break I will be local, and I can be reached directly at 630-324-0000.
---- Daniel Murphy-Olson Systems Administrator Mathematics& Computer Science Division Argonne National Laboratory 630-252-0055
----- Original Message ----- From: "Dan Olson"<[email protected]> To: "core-admins"<[email protected]> Cc: "Jini Ramprakash"<[email protected]>, "Robert R. Scott"<[email protected]> Sent: Wednesday, December 22, 2010 9:59:36 AM Subject: Crypto server status
I've been on the phone working with cryptocard support all morning.
The server has been detecting tokens as corrupt, it affected 4 users yesterday, also per the logs it appears these four users will have problems today. An overnight validation process disabled them again. The rest of the users should be functional.
The users are: cdaley gjordan fischer eholohan
I will send updates as soon as I have any.
---- Daniel Murphy-Olson Systems Administrator Mathematics& Computer Science Division Argonne National Laboratory 630-252-0055