No data visible in a monitor dashboard after upgrading Datasync 1.2.5 into Mobility 2.0

  • Document ID:7014256
  • Creation Date:10-Dec-2013
  • Modified Date:12-Jun-2014
    • Micro Focus Products:
      GroupWise
      GroupWise Mobility Service

Environment

Novell Data Synchronizer Mobility Pack 1.2.5.299
Novell GroupWise Mobility Server 2.0

Situation

After upgrading existing Datasync 1.2.5 server into new version, GroupWise Mobility Server 2.0, the monitor tool works fine but there no data displayed in a dashboard section. When checking log files in the /var/log/datasync/monitorengine you might find similar complain like in example bellow:
 
INFO [MainThread] [monitorengine_util:26] [userID:] [eventID:] [objectID:] [] Loading DataSync MonitorEngine v2.0.0 429.
INFO [MainThread] [monitorEngine:31] [userID:] [eventID:] [objectID:] [] Creating DataSync Monitor...
INFO [MainThread] [monitorengine:89] [userID:] [eventID:] [objectID:] [] MonitorEngine Initializing ...
ERROR [MainThread] [monitorEngine:71] [userID:] [eventID:] [objectID:] [] MonitorEngine Terminated unexpectedly: FATAL: database "dsmonitor" does not exist
Traceback (most recent call last):
File "monitorengine/sbin/monitorEngine.py", line 64, in <module>
File "monitorengine/lib/monitorengine/monitorengine.py", line 104, in init
File "monitorengine/lib/monitorstorage/basestore.py", line 212, in __init__
File "monitorengine/lib/monitorstorage/basestore.py", line 111, in __init__
File "monitorengine/lib/monitorstorage/basestore.py", line 67, in __init__
File "monitorengine/lib/monitorstorage/basestore.py", line 42, in __init__
File "monitorengine/lib/monitorstorage/basestore.py", line 46, in connect
OperationalError: FATAL: database "dsmonitor" does not exist
 
Update process failed to create new database called "dsmonitor".
GroupWise Mobility Service Dashboard is blank or not populated with any data.

Resolution

In most cases the reason behind this problem is within PSQL database server which failed to stop and start during upgrade process. You can find out if this is your case if you manually stoping the gms services then stop and start PSQL with the following commands:

  1. rcgms stop
  2. rcpostgresql stop
  3. rcpostgresql start
    Note: the typical sign is that the service says it failed to start but when checking a status afterwards, it shows "running."

  4. The problem is within the pg_hba.conf file (/var/lib/pgsql/data) which has been truncated on your server. Please, make sure that your config file has following info included:
     
    # TYPE DATABASE USER CIDR-ADDRESS METHOD

    # "local" is for Unix domain socket connections only
    local all postgres ident sameuser
    # IPv4 local connections:
    host all postgres 127.0.0.1/32 ident sameuser
    # IPv6 local connections:
    host all postgres ::1/128 ident sameuser
    #DATASYNC MODS
    local datasync all md5
    host datasync all 127.0.0.1/32 md5
    host datasync all ::1/128 md5
    local postgres datasync_user md5
    host postgres datasync_user 127.0.0.1/32 md5
    host postgres datasync_user ::1/128 md5
    #ACTIVESYNC MODS
    local mobility all md5
    host mobility all 127.0.0.1/32 md5
    host mobility all ::1/128 md5
     
    • Your PSQL database server shall stop and start now without complains:: rcpostgresql restart
    • Next, rerun the update.sh script: /opt/novell/datasync/update.sh. This will resolve any missing parts of upgrade process. After starting gms service, the dashboard shall be now populated with a data.