regischapman Trusted Contributor.
Trusted Contributor.

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution
Yes, I keep inheriting neglected servers and have to spend a long time upgrading them from ancient versions to newer ones.

Even so, at some point, people had to get instructions on upgrading from 230 to a newer version. I keep wondering where those instructions are?

The link you sent assumes I'm already at 9.4 PostgreSQL. I'm just trying to get to that point, so I can start that process.

I'm also not upgrading to GMS 18.1.1, unless that allows me to continue running Groupwise 2014r2. I need to upgrade about 11 servers to SLES 12, and eventually to GW 2018 also, but right now I'm on the very first server.

Right now, I'm VERY concerned about upgrading things out of order. So, should I do this one server last and GW 2014 r2 first, then the CalDAV, then the GWIA then reload and then retain?
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution

First, GMS 14.2.x will not run on either SLES12SP3 or SP4.  In order to continue to run GMS 14.2.x you will need to stop with SLES12SP2. 

https://www.novell.com/documentation/groupwisemobility2014r2/gwmob2014r2_guide_install/data/inst_req_server.html

Also rather than continue to fight this one, why don't you just spin up a new SLES12SP2 server, install GMS 14.2.1 HP5 and then retire the current Datasync server?  The migration from Datasync 2.x to GMS 14.2.x was never tested.

Pam

0 Likes
regischapman Trusted Contributor.
Trusted Contributor.

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution
I would do that, if I knew how to connect that server to the existing Groupwise server. It's been suggested before, but since this is very first time I'm doing any of this on inherited servers neglected for years... I would like to do anything that gets me unstuck.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution

To get GMS talking to GW, you will set that up in the installation process.  Check out the install documentation - https://www.novell.com/documentation/groupwise2014r2/gw2014_guide_install/data/inst_front.html

Pam

0 Likes
regischapman Trusted Contributor.
Trusted Contributor.

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution
I did all that, and installed the GMS as you advised. I'm following this:
https://www.novell.com/documentation/groupwisemobility2014r2/gwmob2014r2_guide_install/data/inst_install_service.html#inst_install_service_status_service
And the web admin doesn't seem to start after rebooting, and if I restart those services, it breaks those services.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution

The server is running SLES12SP2 and not SP3 or SP4?

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution
Did you by chance grab the wrong ISO? There are separate ones for SLES11 and SLES12, respectively. Assuming you’re attempting a fresh install, which OS are you trying on?

0 Likes
Knowledge Partner
Knowledge Partner

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution

@probello wrote:

First, GMS 14.2.x will not run on either SLES12SP3 or SP4.  In order to continue to run GMS 14.2.x you will need to stop with SLES12SP2. 

That's not quite correct, mobilty 2014r2sp2hp5 is supported on SLES12SP3, see:

https://download.microfocus.com/Download?buildid=TGm6C98sh2E~

"

To upgrade the server from SLES 12 SP2 to SLES 12 SP3, do the following:

  • Run /opt/novell/datasync/tools/pgUpdate94to96.sh to update postgresql. This can be done at any time before upgrading the OS.

Upgrade the OS to SLES 12 SP3."

BUT:

1. You must first install onto SLES12SP2, then update to SLES12SP3 as per above.

2. SLES12SP3 itself is EOL too by now, so this is all very unfortunate. We can't urge the need to move on to 18.1 enough. That's the only supported path at this point in time.

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
regischapman Trusted Contributor.
Trusted Contributor.

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution
No, I specifically downloaded and installed SLES 12 SP2 per the documentation for the specific ISO in question: novell-groupwise-mobility-service-14.2.1hp1-x86_64-270-SLES12 I also downloaded.

It runs through, looks like it installs, installs the database, then asks me a TON of questions (some of which I was unsure about the answers to) and then does not allow me to login.

When I checked why this was so, the web admin process says unused. If I restart them, using the rcgms restart, it says redirecting to gms.restart

Now, I revived my old GMS and started taking screenshots of the various settings there, and I have to say they look quite different than what I am being asked about.
0 Likes
regischapman Trusted Contributor.
Trusted Contributor.

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution
Yes, well, this is a rabbit hole I didn't know I was going down. My only real goal was to upgrade all my GW servers (starting with this one) in preparation for doing the remaining upgrades on the software behind it.

Now I'm finding an interlaced lattice of dependencies, matched step versions of OSes that are required for just this one product, and I have GWIA, Groupwise main server, CalDAV, and so on for a total of 11 servers.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution

While this is not the reason for webadmin not starting: please make sure NOT to use BTRFS (which is the default with SLES12) for the gms box, at least not for the area where the database resides.

As for the webadmin part: do you get relevant info in /var/log/datasync/webadmin/server.log?

 

0 Likes
regischapman Trusted Contributor.
Trusted Contributor.

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution
Yes, this is good advice. Thank you. I checked and it is btrfs. I'm going to redo the server now, and then install it again and see if it works. I uninstalled the product so I don't have any logs remaining.
0 Likes
regischapman Trusted Contributor.
Trusted Contributor.

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution
How do I install the database to a different partition? I do have a larger partition where I'd like the database to reside.
0 Likes
regischapman Trusted Contributor.
Trusted Contributor.

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution
I installed this again with EXT3 as a filesystem:
2019-08-21 10:20:19.438 INFO [webadminServer:297] Starting DataSync Web Admin v14.2.1 270.
2019-08-21 10:20:19.452 INFO [webadminServer:330] Loaded django framework 1.0.4.
2019-08-21 10:20:20.611 ERROR [util:256] EXCEPTION: ********************
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: Traceback (most recent call last):
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: File "webadmin/modules/datasync/management_gui/g.py", line 80, in makeSudsClient
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: File "/lib/supersocket.py", line 208, in __init__
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/client.py", line 110, in __init__
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: self.wsdl = Definitions(url, options)
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/wsdl.py", line 171, in __init__
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: d = reader.open(url)
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/reader.py", line 52, in open
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: fp = self.options.transport.open(Request(url))
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/transport/http.py", line 62, in open
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: return self.u2open(u2request)
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/transport/http.py", line 118, in u2open
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: return url.open(u2request, timeout=tm)
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: File "/usr/lib64/python2.7/urllib2.py", line 429, in open
2019-08-21 10:20:20.612 ERROR [util:259] EXCEPTION: response = self._open(req, data)
2019-08-21 10:20:20.613 ERROR [util:259] EXCEPTION: File "/usr/lib64/python2.7/urllib2.py", line 447, in _open
2019-08-21 10:20:20.613 ERROR [util:259] EXCEPTION: '_open', req)
2019-08-21 10:20:20.613 ERROR [util:259] EXCEPTION: File "/usr/lib64/python2.7/urllib2.py", line 407, in _call_chain
2019-08-21 10:20:20.613 ERROR [util:259] EXCEPTION: result = func(*args)
2019-08-21 10:20:20.613 ERROR [util:259] EXCEPTION: File "/lib/supersocket.py", line 296, in https_open
2019-08-21 10:20:20.613 ERROR [util:259] EXCEPTION: File "/usr/lib64/python2.7/urllib2.py", line 1198, in do_open
2019-08-21 10:20:20.613 ERROR [util:259] EXCEPTION: raise URLError(err)
2019-08-21 10:20:20.613 ERROR [util:259] EXCEPTION: URLError: <urlopen error [Errno 111] Connection refused>
2019-08-21 10:20:20.613 ERROR [util:260] EXCEPTION: ********************
2019-08-21 10:20:20.620 INFO [webadminServer:352] SSL listener on 0.0.0.0:8120 (pid 11334)...
2019-08-21 10:20:20.620 INFO [webadminServer:353] Current language for UI is: en-us

Initial rcgms status:
GW-MOBILE2:/ # rcgms status
Checking for gms monitor: running
Checking for gms config: running
Checking for gms engine: running
Checking for gms web admin: running
Checking for gms agent manager: running
● gms.service - LSB: Start datasync services
Loaded: loaded (/etc/init.d/gms; bad; vendor preset: disabled)
Active: active (exited) since Wed 2019-08-21 10:20:19 PDT; 2min 36s ago
Docs: man:systemd-sysv-generator(8)
Process: 10977 ExecStart=/etc/init.d/gms start (code=exited, status=0/SUCCESS)

GW-MOBILE2:/ # rcgms status
Checking for gms monitor: running
Checking for gms config: running
Checking for gms engine: running
Checking for gms web admin: running
Checking for gms agent manager: running
● gms.service - LSB: Start datasync services
Loaded: loaded (/etc/init.d/gms; bad; vendor preset: disabled)
Active: active (exited) since Wed 2019-08-21 10:20:19 PDT; 2min 36s ago
Docs: man:systemd-sysv-generator(8)
Process: 10977 ExecStart=/etc/init.d/gms start (code=exited, status=0/SUCCESS)
0 Likes
regischapman Trusted Contributor.
Trusted Contributor.

Re: Problems Upgrading GW Mobile server to SLES 12

Jump to solution

Initial rcgms status:

GW-MOBILE2:/ # rcgms status
Checking for gms monitor: running
Checking for gms config: running
Checking for gms engine: running
Checking for gms web admin: running
Checking for gms agent manager: running
● gms.service - LSB: Start datasync services
Loaded: loaded (/etc/init.d/gms; bad; vendor preset: disabled)
Active: active (exited) since Wed 2019-08-21 10:20:19 PDT; 2min 36s ago
Docs: man:systemd-sysv-generator(8)
Process: 10977 ExecStart=/etc/init.d/gms start (code=exited, status=0/SUCCESS)

 

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.