Hey. Was just curious about the reason given in asgs log after alleg shut down suddenly.
Invalid session didn't sound like one of the more regular crash reasons that show up. So I thought I'd post:
• Last Check-in: 9/18/2006 9:21:59 AM
• Checking In
• Return Code: 5
• Invalid session
• Beginning Logout
• Closing processes
• Sending Logout Request
• Logged Out
'invalid session' crash?
That error means your current login session has been ruined somehow.
If you crashed hard, it's quite possible that the ASGS server still thought you were logged in. When you attempted to log in a 2nd time (and create a new session), ASGS saw that you already had a session open so it invalidated it and logged you out.
I'm sure once you logged in again everything worked fine.
Don't worry about the error, you're all good!
--TE
If you crashed hard, it's quite possible that the ASGS server still thought you were logged in. When you attempted to log in a 2nd time (and create a new session), ASGS saw that you already had a session open so it invalidated it and logged you out.
I'm sure once you logged in again everything worked fine.
Don't worry about the error, you're all good!
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.