Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic SYNERGY (steve huntington)
Decrease font size
Increase font size
Topic Title: ESD for CM62 do not start properly ?
Topic Summary:
Created On: 14-Jan-2004 09:23
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 14-Jan-2004 09:23
User is offline View Users Profile Print this message


lyes guerroui

Posts: 21
Joined: 17-Jun-2003

Hi !

I've a problem with a CM Synergy 6.2 SP1 Server on Ultrasparc/Solaris 8 machine. When rebooting the server, a special init.d script do the following actions to stop synergy tools :

echo "Change Synergy on port 8600 Stopping"
su - ccm_root -e "cd /opt/cs42/cs_app ; ./csctl.sh stop"
echo "CM Synergy Stopping"
su - informix -e "cd /opt/ccm62/bin ; ./ccmsrv offline -y -s epsilon61"
su - ccm_root -e "cd /opt/ccm62/bin ; ./ccm_stop_daemons "

This is the part that starts the synergy tools when starting the machine:

echo "CM Synergy Starting"
su - ccm_root -e "cd /opt/ccm62/bin ; ./ccm_start_daemons "
su - informix -e "cd /opt/ccm62/bin ; ./ccmsrv online -y -s epsilon61"
echo "Change Synergy on port 8600 Starting"
su - ccm_root -e "cd /opt/cs42/cs_app ; ./csctl.sh start"

The problem is that the ccm_esd do not work at all. Users can't start sessions and Change Synergy do not work also.

I'm oblliged to kill the process of ccm_esd by getting its pid with "ccm monitor" command, and then restart it by simply typing /opt/ccm62/bin/ccm_esd. After that, all work properly.

Have you any idea about what was wrong with my script or any other thing to avoid kill/restart the esd manualy ?


Thanks in advance,

Lyes GUERROUI
LOTSYS France.
Solaris/Synergy Admin.
Report this to a Moderator Report this to a Moderator
 14-Jan-2004 09:56
User is offline View Users Profile Print this message


Russ Braithwaite

Posts: 41
Joined: 13-Jun-2003

Coincidentally, we have had this problem ourselves on a 6.2 SP1 Solaris 8 server for quite some time & we are testing a fix for it this morning.

Until now we have had to kill & restart the ESD as part of the startup script but as that is unsatisfactory an alternative approach of making sure the Synergy startup script always runs last (stick a few "z"s at the start of its name?) & to put a few minutes sleep into it before it starts the ESD.

The underlying problem seems to be other processes or daemons running at startup interfering with the ESD startup.

Will let you know if this approach works.

Russ Braithwaite

-------------------------
Russ Braithwaite
Software Configuration Management
Friends Provident
Report this to a Moderator Report this to a Moderator
 24-Feb-2004 14:40
User is offline View Users Profile Print this message


Matthias Schwellenberg

Posts: 15
Joined: 12-Jun-2003

Hello,

we have had the same problem on our Solaris 8 Servers.

We solved the problem by *not* starting the ESD by the init-Script but by calling an other script as an 'at' job (e.g. now+5 Minutes) which starts the ESD. It works fine.

A few days ago I read, that there is a new Patch available, which fixes this bug. Perhaps we do not install this patch because our soloution works as well ("never change a running system"), but for you this would be the easiest way to solve this problem instead of writing some confusing scripts.

Greets,
Matthias
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 15:34.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.