Absent Member.
Absent Member.
1711 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
Absent Member.
Absent Member.

Any ideas, anyone?

Best regards Claus, DK
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

In article <clausbc.69jglz@no-mx.forums.novell.com>, Clausbc wrote:
> Any ideas, anyone?
>

What is the problem?
Return codes are a normal thing, they are just a status update of some
sort and all look OK to me. Normally seeing a hunk of such a log file
without an actual problem results in eyes glazing over for many of us.


Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Highlighted
Absent Member.
Absent Member.

konecnya;2306491 wrote:
In article <clausbc.69jglz@no-mx.forums.novell.com>, Clausbc wrote:
> Any ideas, anyone?
>

What is the problem?
Return codes are a normal thing, they are just a status update of some
sort and all look OK to me. Normally seeing a hunk of such a log file
without an actual problem results in eyes glazing over for many of us.


Hi,
thanks for replying.
Surely - return codes are normal, but normally on these installs, pop-ups during installation with return code and function name is unexpected. The others, return 0, does not show pop-ups.
Symptom:
On the web-interface (:8120) GroupWise Sync Agent never leaves status Starting
Clicking the GroupWise and Device tabs shows: "Illegal Server Error
An error has occurred and your request could not be completed.

If the error persists, contact your system administrator."

So basically I don't expect install to be complete/functional (I admit - I am new to Mobility service)

Best regards Claus, DK
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

In article <clausbc.69l8hz@no-mx.forums.novell.com>, Clausbc wrote:
> but normally on these installs,
> pop-ups during installation with return code and function name is
> unexpected.
>

Ahhh, this is a fresh install then I take it and not something that
was working before. 32 or 64 bit server? How much RAM?
Understanding the contents of logs works so much more when we know the
context of them.

There a whole bunch of logs, so which one is that from?
/Var/log/datasync/ has a bunch of separate logs for each piece of the
datasync puzzle
/var/log/messages contains the system log that may have some indication
of what happened at install time.

Have you ensured that the SOAP port is open to your POA? You can telnet
to it from your GMS server to do this


Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Highlighted
Absent Member.
Absent Member.

konecnya;2306962 wrote:
In article <clausbc.69l8hz@no-mx.forums.novell.com>, Clausbc wrote:
> but normally on these installs,
> pop-ups during installation with return code and function name is
> unexpected.
>

Ahhh, this is a fresh install then I take it and not something that
was working before. 32 or 64 bit server? How much RAM?
Understanding the contents of logs works so much more when we know the
context of them.

There a whole bunch of logs, so which one is that from?
/Var/log/datasync/ has a bunch of separate logs for each piece of the
datasync puzzle
/var/log/messages contains the system log that may have some indication
of what happened at install time.

Have you ensured that the SOAP port is open to your POA? You can telnet
to it from your GMS server to do this


Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!


Hi,
sorry for being unclear:
- New install on sles11sp3 x64 virtual guest, 1G og ram
- Log snip is from install.log in the /var/log/datasync/
- GMS never worked on this test install
- Haven't found any clues myself in messages
- Yes SOAP connection is opened, has been verified during wizard at the trusted application step

Best regards Claus, DK
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

In article <clausbc.69rymn@no-mx.forums.novell.com>, Clausbc wrote:
> Hi,
> sorry for being unclear:

A trick I learned that helps me get better support response as well as
reducing the number of times I need to use support, is to think through
what will support (of any kind) need to know to help. Just doing that
exercise speeds the whole process up.

> - New install on sles11sp3 x64 virtual guest, 1G of ram

ouch, that is rather tight and might be low enough to cause you some
grief. 2GB has worked well enough for small deployments for me, though I
have had to push up to the official minimum of 4GB once some real load
got placed on it.
I would recommend getting that box up to 2GB and try the install again.

> - Log snip is from install.log in the /var/log/datasync/
> - GMS never worked on this test install
> - Haven't found any clues myself in messages

OK, that helps put a context on things.

> - Yes SOAP connection is opened, has been verified during wizard at the
> trusted application step

Was this run on this Mobility server? If not then do test from this
Mobility VM. A to make sure the DMZ to LAN route lets it through as well
as the SLES firewall on the Mobility server.


Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi,
returning to this.
Since last:
- Got 2.0.1 iso: No change
- Tried increasing ram: No change
- Test installed on an alternative vm guest on same subnet as GroupWise server: Succes

So I guess it must some kind of networking issue:
- I am installing on a dmz vm guest
- Checked my firewalls: No packets seems to get blocked
- Checked the soap interface from my mobility test server http://<groupwise-ip>:7191/soap, which returns POA response as expected

From install.log:
Wed Mar 26 21:48:14 CET 2014: Datasync.Write:executing: python /opt/novell/datasync/syncengine/connectors/mobility/cli/mobility_setup_5.pyc --provision 'groupwise' --galuser 'admin' --block false --selfsigned true --path '' --lport '443' --secure true
Wed Mar 26 21:48:16 CET 2014: Datasync.Write:return code from activesync_setup_5.pyc:1


Any suggestions?
What is done is this step 5?


konecnya;2307233 wrote:
In article <clausbc.69rymn@no-mx.forums.novell.com>, Clausbc wrote:
> Hi,
> sorry for being unclear:

A trick I learned that helps me get better support response as well as
reducing the number of times I need to use support, is to think through
what will support (of any kind) need to know to help. Just doing that
exercise speeds the whole process up.

> - New install on sles11sp3 x64 virtual guest, 1G of ram

ouch, that is rather tight and might be low enough to cause you some
grief. 2GB has worked well enough for small deployments for me, though I
have had to push up to the official minimum of 4GB once some real load
got placed on it.
I would recommend getting that box up to 2GB and try the install again.

> - Log snip is from install.log in the /var/log/datasync/
> - GMS never worked on this test install
> - Haven't found any clues myself in messages

OK, that helps put a context on things.

> - Yes SOAP connection is opened, has been verified during wizard at the
> trusted application step

Was this run on this Mobility server? If not then do test from this
Mobility VM. A to make sure the DMZ to LAN route lets it through as well
as the SLES firewall on the Mobility server.


Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

Best regards Claus, DK
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

In article <clausbc.6bltgn@no-mx.forums.novell.com>, Clausbc wrote:
> So I guess it must some kind of networking issue:
> ....
> - Checked my firewalls: No packets seems to get blocked
>

yes that certainly points very strongly to a networking issue with it
being something with the firewall.

There have been instances where a firewall messes up some packets going
through it that stops things from working. I've hit is directly and on
of they other Knowledge Partners recently hit it with a very similar
situation you are dealing with (GMS SOAP communication).

Running a packet capture on both sides of the firewall was how it was
proven that the firewall was modifying the packets in ways it shouldn't
have. The Cause was a corruption of the firewall database that needed
cleaning up of an old rule that was supposed to have been deleted and
hadn't cleanly been taken out.


Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Highlighted
Absent Member.
Absent Member.

Did you find out what caused this error and how you fixed this?

I'm experiencing same stuff when upgrading a GMS 2.0.1 to 2.1. Everything worked fine in 2.0.1. Upgraded GW POA to 2014 and GMS to 2.1. Both running in VMware and on SLES11 SP3.

I also tried a reinstall SLES, but always same problems during installation of GMS. GW and GMS servers are on same subnet and no firewall running on neither. Both VMs are running on the same VM host on the same network connection....
Telnet to GW SOAP port works fine

After installation, GMS is having problems login into Postgresql:
2015-04-03 10:56:14 CEST datasync datasync_user FATAL: password authentication failed for user "datasync_user"

And ..syncengine\engine.log (and others) show errors like this:
>>> [objectID:] [] EXCEPTION: File
>> "syncengine/lib/syncengine/engine.py",
>>> line 311, in __init__
>>> 2015-04-03 10:59:50.440 ERROR [MainThread] [util:258] [userID:]
>> [eventID:]


Been trying out several things for days now and always same results 😞
- not good for my reputation, nor for GroupWise which may suffer more after 2014 Upgrade... 😕

Patrick Frontéri # GroupWiseR of Norway # Active part of the OpenHorizons and NetworkPartners.no Collaboration
0 Likes
Highlighted
Absent Member.
Absent Member.

Hello again,

I finally found of my problem!!

As suspected it had to do with GMS login to Postgresql, but what would be the problem!?!
Worked fine with GMS 2.0.1, PG itself didn't have problems and I could log into db with pgsql command....

Found this old forum entry ( https://forums.novell.com/showthread.php/406908-SyncEngine-won-t-start
) that put me in the right direction but was hard to find it. Maybe Novell should create a TID on this - I think it would be easier to find the solution that way.
- Problem for us was so called special characters in pg password 😕

Semms to me the culpit is GMS 2.1 engine not interpreting the characters correctly. Customer had + in the datasync_use pg password. Without it GMS 2.1 engine is now working fine.

Novell may have some fixing to do?!?
Would be great if Novell at least could add this problem/solution in a TID 😉 Maybe also update http://www.novell.com/support/kb/doc.php?id=7008764 that the PG password itself could be a problem for GMS....

Patrick Frontéri # GroupWiseR of Norway # Active part of the OpenHorizons and NetworkPartners.no Collaboration
0 Likes
Highlighted
Absent Member.
Absent Member.

Great to know - and thank you for the update.
I never found the issue, so I had to abandon GMS at the time. I will do new attempt with this information/suggestion in mind.

pfronteri;2351956 wrote:
Hello again,

I finally found of my problem!!

As suspected it had to do with GMS login to Postgresql, but what would be the problem!?!
Worked fine with GMS 2.0.1, PG itself didn't have problems and I could log into db with pgsql command....

Found this old forum entry ( https://forums.novell.com/showthread.php/406908-SyncEngine-won-t-start
) that put me in the right direction but was hard to find it. Maybe Novell should create a TID on this - I think it would be easier to find the solution that way.
- Problem for us was so called special characters in pg password 😕

Semms to me the culpit is GMS 2.1 engine not interpreting the characters correctly. Customer had + in the datasync_use pg password. Without it GMS 2.1 engine is now working fine.

Novell may have some fixing to do?!?
Would be great if Novell at least could add this problem/solution in a TID 😉 Maybe also update http://www.novell.com/support/kb/doc.php?id=7008764 that the PG password itself could be a problem for GMS....

Best regards Claus, DK
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.