Euh no we didn't do any change EXCEPT for the POP3/SMTP TCP check were we "changed" the protocol. Did you define a new TCP protocol for it or are you using the port connector? Try defining a TCP protocol (ctrl-P) for it, then you can "quit" correctly.
dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Roland Gaspar Sent: Wed Jun 25 1:57 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [SA-list] TCP-Port check I've Crashed Tivoli's TSM server (previously known IBM's ADSM) by doing a port connector check on 1580 (default TSM port)... Tivoli said "well then, don't do that anymore" (a la "Doctor, it hurts when I do this; then don't do that") kinda sad as a response buy hey.. 'Least you know... ________________________ Roland Gaspar Tel.: (514) 398-7880 xt 8603 >>> [EMAIL PROTECTED] 06/24/03 07:08PM >>> Dirk, I upgraded last week to v 4.0.1438 Two of my checks performed a TCP Port Connection check of a vendor supplied application running on a Solaris server. Prior to upgrading there were no problems and I'd been running the checks since march. After the upgrade, the client overloaded the server and caused all kinds of problems for better than 2 days before I identified SA as the cause and killed those two checks. Any changes to the TCP Port connection check recently? Might others see adverse effects? Hope I can help head off a problem for someone else. Robert To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
