Highlighted
Absent Member.
Absent Member.
1709 views

Datasync.Write:return code from activesync_setup_5.pyc:1

Hi all,
I am testing Mobility Service 2.0.
Test server is a sles11sp3 with nothing else running. Placed in dmz with GroupWise server on lan.

Log snip:
Wed Feb 12 22:22:56 CET 2014: Datasync.Write:executing: MUSER='datasync_user' MUSERPASS='******' /opt/novell/datasync/syncengine/connectors/mobility/cli/postgres_setup_1.sh
Wed Feb 12 22:23:43 CET 2014: Datasync.Write:return code from postgress_setup_1.sh:0
Wed Feb 12 22:23:43 CET 2014: Datasync.Write:executing: python /opt/novell/datasync/syncengine/connectors/mobility/cli/odbc_setup_2.pyc
Wed Feb 12 22:23:43 CET 2014: Datasync.Write:return code from odbc_setup_2:0
Wed Feb 12 22:23:43 CET 2014: Datasync.Write:executing: python /opt/novell/datasync/syncengine/connectors/mobility/cli/mobility_setup_3.pyc ...
Wed Feb 12 22:23:44 CET 2014: Datasync.Write:return code from mobility_setup_3.pyc:0
Wed Feb 12 22:23:44 CET 2014: Datasync.Write:executing: /opt/novell/datasync/syncengine/connectors/mobility/cli/enable_setup_4.sh
Wed Feb 12 22:24:07 CET 2014: Datasync.Write:return code from enable_setup_4.sh:0
Wed Feb 12 22:24:08 CET 2014: Datasync.Write:executing: python /opt/novell/datasync/syncengine/connectors/mobility/cli/mobility_setup_5.pyc --provision 'ldap' --galuser 'claus' --block false --selfsigned true --path '' --lport '443' --secure true
Wed Feb 12 22:24:13 CET 2014: Datasync.Write:return code from activesync_setup_5.pyc:1
Wed Feb 12 22:24:13 CET 2014: Datasync.Write:stdout on error:
Wed Feb 12 22:24:21 CET 2014: Datasync.GetAllStaticInterfaces:static IP info: ["eth0"]
Wed Feb 12 22:24:21 CET 2014: Datasync.GetAllipInterfaces:ip is 172.16.0.80
Wed Feb 12 22:24:22 CET 2014: Datasync.GetAllStaticInterfaces:Mapping of IP addresses and network devices: $["172.16.0.80":"eth0"]
Wed Feb 12 22:24:22 CET 2014: Datasync.GetIPAddr:First IP address 172.16.0.80
Wed Feb 12 22:24:22 CET 2014: Datasync.Write:executing: python /opt/novell/datasync/syncengine/connectors/mobility/cli/groupwise_setup_6.pyc --keypath '*****' --lport '4500' --lip '172.16.0.80' --version '802' --soap 192.168.0.4 --key '*****' --sport 7191 --psecure 'no'
Wed Feb 12 22:24:26 CET 2014: Datasync.Write:return code from groupwise_setup_6.pyc:1
Wed Feb 12 22:24:26 CET 2014: Datasync.Write:stdout on error:
Wed Feb 12 22:24:28 CET 2014: Datasync.Write:executing: python /opt/novell/datasync/syncengine/connectors/mobility/cli/start_mobility.pyc
Wed Feb 12 22:24:41 CET 2014: Datasync.Write:return code from start_mobility.pyc:1
Wed Feb 12 22:24:41 CET 2014: Datasync.Write:stdout on error:
Wed Feb 12 22:24:46 CET 2014: Skipping Customer Center Configuration.

Any ideas?

Best regards Claus, DK
Labels (1)
0 Likes
12 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Hi Patrick,

At the bottom of each TID page is the option to provide feedback on the TID. Have you done so with your updated information? This is the best way to alert Novell that a TID is outdated or needs amendment. Remember that Novell don't officially monitor these forums for such feedback.

Secondly, are you in a position to open an SR to get this logged, officially, as a bug? Let us know. If you are not in such a position perhaps I could do so on your behalf.

Thanks for posting your information as we all learn from it.

Looking forward to hearing back from you.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.