Second time it's happened now, where the server side has failed over a weekend. A simple "tarantella restart" is all that it needs to get going again, but I'd like to prevent the problem from happening at all. The error log from that time period is below... Any ideas?
Check the Proxy Server logs for client reconnect. 2007/08/16 16:19:13.278 (pid 4489) pem/launch #184 Sun Secure Global Desktop Software(4.2) ERROR: Client reconnect timeout has expired. Killing dox001:1187294953271:5068550969694320526:Li4uL191c2VyL2RveC1rbm9i. The current launch has failed. Check the Proxy Server logs for client reconnect. 2007/08/16 16:19:13.304 (pid 4489) pem/circuit #186 Sun Secure Global Desktop Software(4.2) ERROR: An error occurred writing on circuit ttacpe_pid:643_25. Reason: write(25,<address>,134): (32) Broken pipe. The current operation has failed. If persistent, restart the server. 2007/08/16 16:19:13.304 (pid 4489) pem/circuit #188 Sun Secure Global Desktop Software(4.2) ERROR: The connection to Protocol Engine ttacpe_pid:643_25 has been lost. The Protocol Engine will continue to service existing sessions, but will not accept any more. A new Protocol Engine will be launched when needed. 2007/08/17 09:54:59.672 (pid 4489) pem/launch #190 Sun Secure Global Desktop Software(4.2) ERROR: Client reconnect timeout has expired. Killing dox001:1187358299665:8988220368628247921:Li4uL191c2VyL2RveC1rbm9i. The current launch has failed. Check the Proxy Server logs for client reconnect. -- Brian Knoblauch, ITSS DoX Systems, LLC 3454 Oak Alley Ct. Toledo, OH 43606-1354 419-654-1607 http://www.doxsystems.com _______________________________________________ SGD-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sgd-users
