> A more accurate way of saying what he *might* have meant was that there > was an application "hung" on a port...
I had the same thought initially, except that the error caused the box to fall flat on it's face. I had to bring the box down as easily as I could (not very easily considering it's hobbled state), and after rebooting I had the vendor check the db/app. That's when they came up with their...uh...diagnosis. My experience with this vendor tells me that John Broome's suggestion is close, but I just wanted run it through the TriLUG sanity check. MPF P.S. <Tribot> Your excuse is: The server threw a rod. -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
