Title: | USG buildhelp questions/answers |
Moderator: | SMURF::FILTER |
Created: | Mon Apr 26 1993 |
Last Modified: | Mon Jan 20 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2763 |
Total number of notes: | 5802 |
Date Of Receipt: 20-MAR-1996 14:54:23.35 From: SMURF::20162::"[email protected]" "20-Mar-1996 1151" To: [email protected] CC: [email protected], [email protected] Subj: Re: exiting workon Your problem is being caused by system problems in zk3. secret and buffer have hosed their routing tables. When that gets fixed you'll be able to exit workon again. The reason it takes longer than it used to is related to the authorization scheme changes we made last release.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2162.1 | exiting workon | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Wed Mar 27 1996 15:58 | 20 |
Date Of Receipt: 20-MAR-1996 14:56:34.81 From: SMURF::FLUME::dlong "David Long OSG 20-Mar-1996 1349" To: odehelp@DEC:.zko.flume CC: dlong@DEC:.zko.flume Subj: exiting workon for a while now it has taken a noticable longner time to exit a workon session. Right now I am finding that I cannot exit the workon. I get the error: ODE CLIENT ERROR: Failed call to: connect() Connection timed out ODE CLIENT: Check with ode admin, the ode_server daemon could be down. ODE CLIENT: DECode client will retry Retrying connection to secret.zk3.dec.com: retry number 1 Retrying connection to secret.zk3.dec.com: retry number 2 Retrying connection to secret.zk3.dec.com: retry number 3 Why does ODE need to do anything when all I am trying to do is exit the workon? -dl | |||||
2162.2 | Re: exiting workon | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Wed Mar 27 1996 16:06 | 41 |
Date Of Receipt: 20-MAR-1996 15:12:04.47 From: SMURF::FLUME::"[email protected]" "Grant Van Dyck 20-Mar-1996 1507" To: [email protected] CC: [email protected] Subj: Re: exiting workon This was caused by: The network problems affecting buffer and secret were caused by a faulty network tap on the orange net. This tap brought down the entire orange net. A new tap has been installed and all systems are back up. | for a while now it has taken a noticable longner time to exit a workon sessio n. | Right now I am finding that I cannot exit the workon. I get the error: | | ODE CLIENT ERROR: Failed call to: connect() Connection timed out | ODE CLIENT: Check with ode admin, the ode_server daemon could be down. | ODE CLIENT: DECode client will retry | Retrying connection to secret.zk3.dec.com: retry number 1 | Retrying connection to secret.zk3.dec.com: retry number 2 | Retrying connection to secret.zk3.dec.com: retry number 3 | | Why does ODE need to do anything when all I am trying to do is exit the worko n? | | -dl -- -Grant |