Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
OD 6.0.2 failure after MS patching
lhdavis
W2K SP4, OD 6.0.2
This past Friday we applied the latest MS patches on our development TeamSite/OpenDeploy server. These included the following: 926436, 928090, 890830, 928843, 924667, 927779, 918118.
Upon rebooting the server, the OpenDeploy service starts and then fails with this error code in the event viewer "JVM has exited with a code 28". Thinking this code be related to the DST patch listed in IWOV KB article 57708, we followed the steps to update our server with the MS patch and Sun tzupdater app to correct the DST time. After applying this, rebooting, and confirming the daylight savings time fix for Windows, we are still experiencing the issue.
There is nothing out of the ordinary logged in the od.log and nothing in the od.err log file.
I've included a snippet from the odbase.log as well.
SVR: 2007-02-20 12:04:38 EST GMT-05:00 *** OpenDeploy engine component started. ***
SVR 01020: 2007-02-20 12:04:38 EST GMT-05:00 *** Web service is not configured. It is not enabled. ***
SVR: 2007-02-20 12:04:38 EST GMT-05:00 Initialize OpenDeploy API component.
API: 2007-02-20 12:04:38 EST GMT-05:00 Register OpenDeploy service with RMI registry.
API: 2007-02-20 12:04:38 EST GMT-05:00 Component Version : 6.0.2.0.0 Build 46963 Interwoven 20050402
API: 2007-02-20 12:04:38 EST GMT-05:00 OpenDeploy server host: localhost, RMI registry port: 9173
SVR: 2007-02-20 12:04:40 EST GMT-05:00 *** OpenDeploy API component started. ***
CLT: 2007-02-20 12:04:41 EST GMT-05:00 OpenDeploy CLT proxy startup FAILED.
SVR: 2007-02-20 12:04:41 EST GMT-05:00 ***ERROR - CLT proxy failure
SVR: 2007-02-20 12:04:41 EST GMT-05:00 ***ERROR - Startup of OpenDeploy CLT proxy FAILED.
SVR: 2007-02-20 12:04:41 EST GMT-05:00 Bring up of OpenDeploy server FAILED.
Last time we rebooted this development server, here is what is logged around the OpenDeploy CLT section (removed IP):
SVR: 2007-01-10 21:10:04 EST GMT-05:00 *** OpenDeploy API component started. ***
CLT: 2007-01-10 21:10:04 EST GMT-05:00 Network addrs available on localhost:
XX.XX.XX.XX
xxxxxxxx.vha.med.va.gov
CLT: 2007-01-10 21:10:04 EST GMT-05:00 OpenDeploy CLT proxy bound on [localhost:3434]
SVR: 2007-01-10 21:10:05 EST GMT-05:00 *** OPENDEPLOY SERVER FINISHED STARTUP. ***
So how is OpenDeploy obtaining the network addresses to bind the OD CLT proxy? Maybe that is being blocked by something. How can I test?
I do have a support case open but have yet to hear anything back. Anyone see anything like this before? Suggestions are much appreciated.
Find more posts tagged with
Comments
lhdavis
After several attempt at restarting the service over several days, we retried this past Friday and the OpenDeploy service mysteriously started this time. On both test servers. We did not make any changes to either server between it failing last Thursday and it working on Friday. Insert twilight zone music here.
So we still need to diagnose as much as we can why/how this occurred and what we should do if it occurs again. I've sent the requested log files to Support and they're looking into it. But so far, this is pretty weird.
lhdavis
I heard back from Interwoven Support and their official response is that unfortunately they cannot tell us exactly why this issue happened. Basically they have seen similar issues in the past where another application/process was using the same port (3434) used by the OpenDeploy command line tool proxy. This is the port that OpenDeploy monitors for OpenDeploy command line functionality and uses to retrieve the server network addresses.
If it does occur again, we can do some research to see what other applications may be trying to use that port on the server using a process called netstat and give them a call immediately with the results.
Just wanted to close out this post since we so rarely seem to see the resolution of some of the issues folks experience.