Unable to start DataSync services after upgrading the mobility Server to SLES 11 SP2

  • 7012365
  • 04-May-2013
  • 10-Dec-2013

Environment

Novell Data Synchronizer Mobility Pack
SUSE Linux Enterprise Server 11 Service Pack 2

Situation

Symptoms
rcdatasync status command does not give any output
rcdatasync status comes back on the prompt without displaying anything
Unable to start mobility services after upgrading to SLES 11 SP2
WebAdmin displays: Error: Please verify that the Connector Manager is running and that the connectors.xml is correctly configured.
Datasync engine dead after upgrade
Syncengine does not start

Changes
Upraded SLES 11 to SLES 11 SP2 

Resolution

Make sure all the RPMs are installed by following the steps listed below

  1. Launch YaST
  2. Click Software Management | Patterns
  3. Highlight "Novell Data Synchronizer Mobility Pack" on the left
  4. On the right hand side, select all the Packages that are not selected except the Postgresql ones. Do not uncheck Postgresql if it is already selected. However if the Postgresql packages are not selected, do not select it.
  5. Select Package | All in This List | Update if newer version available.
  6. Click Accept and Continue - wait for the package installation to finish

    OR

    If the Patterns cannot be seen follow the steps below
  1. Download the ISO version of Novell Data Synchronizer Mobility Pack that is installed on the server
  2. Copy it to /tmp
  3. Type mkdir /tmp/loop and press Enter
  4. Type mount -t iso9660 -o loop /tmp/novell-data-synchronizer-mobility-pack-1.2.5-x86_64-2xx.iso /tmp/loop/
  5. Type cd /tmp/loop/suse/x86_64 and press Enter
  6. Type rpm -Uvh `find . -name "*.rpm"` --force and press Enter
 
Fix the Configuration files by following the steps listed below
  1. Once the installation is finished, browse to /etc/datasync/webadmin directory and check if there is a file called server.xml.rpmsave. If the file exists
    • rename server.xml to server.new
    •  rename server.xml.rpmsave to server.xml
  2. Browse to /etc/datasync/syncengine directory and check if there is a file called connectors.xml.rpmsave. If the file exists,
    • rename connectors.xml to connectors.new
    •  rename connectors.xml.rpmsave to connectors.xml
  3. Check if the engine.xml.rpmsave exists in /etc/datasync/syncengine. If the file exists
    • rename engine.xml to engine.new
    • rename engine.xml.rpmsave to engine.xml
  4. Browse to /etc/datasync/configengine and check if there is a file called configengine.xml.rpmsave. If the file exists,
    • rename configengine.xml to configengine.new
    • rename configengine.xml.rpmsave to configengine.xml
  5. Browse to /etc/datasync/configengine/engines/default and check if there is a file called engine.xml.rpmsave. If the file exists,
    • rename engine.xml to engine.new
    • rename engine.xml.rpmsave to engine.xml
  6. Browse to /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/groupwise and check if there is a file called connectors.xml.rpmsave. If the file exists
    • rename connectors.xml to connectors.new
    • rename connectors.xml.rpmsave to connectors.xml
  7. Browse to /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/mobility and check if there is a file called connectors.xml.rpmsave. If the file exists
    • rename connectors.xml to connectors.new
    • rename connectors.xml.rpmsave to connectors.xml
  8. Type "killall -9 python" and press Enter
  9. Type "rcpostgresql restart" and press Enter
  10. Type "rcdatasync start" and press Enter

Cause

TID 7007012 was not followed while upgrading SLES11 to SLES 11 SP2