I just got called to come in and fix what ever was wrong with our
systems. Our staff couldn't get into the platypus database, but the
server was up. At the same time, radiator was too down. I restarted it
many times, but it did not want to auth anybody. Once I commented
out any database references (SessionDatabase, AuthBy EMERALD,
ect...)in the config file, it ran fine off of the flat file. Now that the
database is up, I uncommented those database references and things
are back to normal. Of course it would be helpful to have the trace 4 or
strace output when this is going on, however, I was in a 'bit of a rush to
get the systems up and going again as this affected all staff and all
customers at the same time. Any idea what could have happened? It
might also be good if someone had a good watchdog application that
they wrote that would gather the debug information and log it to a file in
the event that there is a failure of some sort. That way, nobody has to
suffer more than necessary to get that debug information. I'll give a
pseudo code listing of my config file below:
<<Client xxx>
Blah...
<<Client xxx>
<<Handler UserName='test'>
<<AuthBy EMERALD>
login info
<</AuthBy>
<</Handler>
<<Handler DEFAULT>
ContinueWhileReject
<<AuthBy FILE>
<</AuthBy>
<<AuthBy EMERALD>
login info
<</AuthBy>
<</Handler>
<<SessionDatabase SQL>
...
<</SessionDatabase>
Thanks,
John Kicklighter
Internet 2xtreme
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
