Technical Helpweb

- more articles

GCEMS processes fail to start

Symptom:

The Dialogic® Gate Control Element Management System (GCEMS) processes (CommManager, GateManager, DataManager and BackupFileManager) fail to start when running StartGCEMS script: 
[excelsw@rhel507 bin]$ ./StartGCEMS
================================================================

Starting IMG to begin a new configuration...

CommManager: ....Failed to start!
GateManager: ....Failed to start!
DataManager: ....Failed to start!
AdminManager: ....Started.
BackupFileManager: ....Failed to start!

Error: StartGCEMS did not start all processes!

================================================================

Diagnosis
When running Dialogic® GCEMS's CommManager process, the message "error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory" is displayed.
[excelsw@rhel507 bin]$ ./CommManager
./CommManager: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

Check /usr/lib, file libstdc++.so.5 does not exist:
[excelsw@rhel507 bin]$ ls /usr/lib/libstdc++*
/usr/lib/libstdc++.so.6 /usr/lib/libstdc++.so.6.0.8

Reason for the issue:
The Dialogic® GCEMS processes require libstdc++.so.5 which is only standard on RHEL3. If you are using RHEL4 or 5, you need to install the optional backwards compatibility 'compat' package. Since this is an optional package, you need to select it manually.
 
Fix / Solution:
Install the compat-libstdc++-33 package, which can usually be found on the RHEL installation Disc 2:
[root@rhel507 ftpBuilds]# rpm -Uvh compat-libstdc++-33*
warning: compat-libstdc++-33-3.2.3-61.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing... ########################################### [100%]
1:compat-libstdc++-33 ########################################### [100%]

Check /usr/lib, file libstdc++.so.5 exists:
[root@rhel507 ftpBuilds]# ls /usr/lib/libstdc++*
/usr/lib/libstdc++.so.5 /usr/lib/libstdc++.so.6
/usr/lib/libstdc++.so.5.0.7 /usr/lib/libstdc++.so.6.0.8
[root@rhel507 ftpBuilds]# 

Restart GCEMS and check that all GCEMS processes are running: 
[excelsw@rhel507 bin]$ ./StartGCEMS
================================================================

Starting IMG to begin a new configuration...

CommManager: ....Started.
GateManager: ....Started.
DataManager: ....Started.
AdminManager: ....Started.
BackupFileManager: ....Started.

Success: StartGCEMS completed.

================================================================


================================================================


[excelsw@rhel507 bin]$ ps -ef | grep Man
excelsw 4459 1 0 10:37 pts/1 00:00:00 ./CommManager
excelsw 4469 1 0 10:37 pts/1 00:00:00 ./GateManager -q
excelsw 4479 1 0 10:37 pts/1 00:00:00 ./DataManager
excelsw 4558 1 1 10:37 pts/1 00:00:00 /opt/dialogic/installs/IMG_10.5.1.122/jre/bin/java com.zerog.lax.LAX /opt/dialogic/IMG/GateControlEMS/bin/./AdminManager.lax /tmp/env.properties.4558
excelsw 4638 1 0 10:37 pts/1 00:00:00 ./BackupFileManager

Product List
Dialogic® IMG 1010 Integrated Media Gateway
Dialogic® Gate Control Element Management System (GCEMS)
Dialogic® ClientView
 



Feedback

Please rate the usefulness of this page:  
0 - not useful at all
1 - potentially useful
2 - quite useful
3 - very useful
4 - exactly the information I needed     

Please enter a comment about this page:

First published: 10-Jun-2009
Open access: Product rule: ; Page rule: Auto

Service Center Logon