Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
jgooderham Absent Member.
Absent Member.
749 views

GMS 14 to GMS 18 via new server

Hi All;

After upgrading our existing Groupwise servers to 2018, I am trying to upgrade GMS to 2018 as well. We are running all of our server in VMWare, so I am doing this by 'unplugging' the existing GMS server and standing up a new SLES15 server with the same hostname and IP address as our existing environment. All needed packages are installed as well as the insserv-compat one needed too. The install goes fine, the services start and run, I can get an admin login screen, but when I try to log in with the root account and password, the website just hangs with the 'logging in' message. Anyone else experience that? What would be the best place to look at logs?

TIA;
John
Labels (1)
0 Likes
4 Replies
Knowledge Partner
Knowledge Partner

Re: GMS 14 to GMS 18 via new server

On Thu, 31 Jan 2019 21:46:01 GMT, jgooderham
<jgooderham@no-mx.forums.microfocus.com> wrote:

>
>Hi All;
>
>After upgrading our existing Groupwise servers to 2018, I am trying to
>upgrade GMS to 2018 as well. We are running all of our server in VMWare,
>so I am doing this by 'unplugging' the existing GMS server and standing
>up a new SLES15 server with the same hostname and IP address as our
>existing environment. All needed packages are installed as well as the
>insserv-compat one needed too. The install goes fine, the services start
>and run, I can get an admin login screen, but when I try to log in with
>the root account and password, the website just hangs with the 'logging
>in' message. Anyone else experience that? What would be the best place
>to look at logs?
>
>TIA;
>John


John,
I'm not running SLES 15 yet, so I'll let someone else speak to that
issue. I know there are some extra requirements with it. I do want
to point out though that you could setup your new GMS server in tandem
with your existing. Use a unique ip address. Once it is operating
correctly, get it all synced up with GroupWise and then change
firewall rules and/or DNS as necessary to point to the new server.
This makes the cut-over almost seemless with no downtime. Might ease
the process of setting up the new one if you know all your users still
have access via the existing one.

--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
--
Ken
Knowledge Partner

Create and vote for enhancements!
Idea Exchange sites within this community are now coming online for some of the Collaboration Products!
GroupWise Idea Exchange - https://community.microfocus.com/t5/GroupWise-Idea-Exchange/idb-p/GWideas
SMG Idea Exchange - https://community.microfocus.com/t5/Secure-Messaging-Gateway-Idea/idb-p/SMG_Ideas
Old method is still available for some products here: https://www.microfocus.com/products/enhancement-request.html
0 Likes
jgooderham Absent Member.
Absent Member.

Re: GMS 14 to GMS 18 via new server

Hi Ken;

Thanks for replying. I was looking to reuse my existing SSL cert. That's why I was trying this out. I had found the Mobility admin guide PDF so I know the location of the log files, but when I type the syntax, I don't get any good hits back.


2019-02-01 10:08:17.53 INFO [webadminServer:106] Got TERM signal
2019-02-01 10:09:17.479 INFO [webadminServer:283] Starting DataSync Web Admin v18.1.0 410.
2019-02-01 10:09:17.504 INFO [webadminServer:316] Loaded django framework 1.11.10.
2019-02-01 10:09:18.982 INFO [webadminServer:340] SSL listener on 0.0.0.0:8120 (pid 2150)...
2019-02-01 10:09:18.982 INFO [webadminServer:341] Current language for UI is: en-us
2019-02-01 10:12:30.972 ERROR [util:258] EXCEPTION: ********************
2019-02-01 10:12:30.972 ERROR [util:261] EXCEPTION: Traceback (most recent call last):
2019-02-01 10:12:30.972 ERROR [util:261] EXCEPTION: File "/opt/novell/datasync/common/lib/django/core/handlers/base.py", line 185, in _get_response
2019-02-01 10:12:30.972 ERROR [util:261] EXCEPTION: response = wrapped_callback(request, *callback_args, **callback_kwargs)
2019-02-01 10:12:30.972 ERROR [util:261] EXCEPTION: File "webadmin/modules/datasync/management_gui/view/admin_functions.py", line 717, in authentication_handler
2019-02-01 10:12:30.972 ERROR [util:261] EXCEPTION: File "webadmin/modules/datasync/management_gui/view/admin_functions.py", line 738, in authenticate
2019-02-01 10:12:30.972 ERROR [util:261] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/client.py", line 540, in __call__
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: return client.invoke(args, kwargs)
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/client.py", line 600, in invoke
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: result = self.send(soapenv)
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/client.py", line 662, in send
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: result = self.failed(binding, e)
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/client.py", line 725, in failed
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: r, p = binding.get_fault(reply)
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: File "/opt/novell/datasync/common/lib/suds/bindings/binding.py", line 265, in get_fault
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: raise WebFault(p, faultroot)
2019-02-01 10:12:30.973 ERROR [util:261] EXCEPTION: WebFault: Server raised fault: 'gw_driver instance has no attribute 'logger''
2019-02-01 10:12:30.973 ERROR [util:262] EXCEPTION: ********************

Maybe Python is screwed up?
0 Likes
Knowledge Partner
Knowledge Partner

Re: GMS 14 to GMS 18 via new server

On Fri, 01 Feb 2019 15:54:01 GMT, jgooderham
<jgooderham@no-mx.forums.microfocus.com> wrote:

>
>Hi Ken;
>
>Thanks for replying. I was looking to reuse my existing SSL cert. That's
>why I was trying this out.


A wildcard cert would solve that...that is how I did it.

>Maybe Python is screwed up?


Sorry, not an area I am familiar with.
I assume you did follow the requirements here:
https://www.novell.com/documentation/groupwise18/gwmob18_guide_install/data/inst_requirements.html
There are specific steps that need to be taken to run on SLES 15.


--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
--
Ken
Knowledge Partner

Create and vote for enhancements!
Idea Exchange sites within this community are now coming online for some of the Collaboration Products!
GroupWise Idea Exchange - https://community.microfocus.com/t5/GroupWise-Idea-Exchange/idb-p/GWideas
SMG Idea Exchange - https://community.microfocus.com/t5/Secure-Messaging-Gateway-Idea/idb-p/SMG_Ideas
Old method is still available for some products here: https://www.microfocus.com/products/enhancement-request.html
0 Likes
Highlighted
jgooderham Absent Member.
Absent Member.

Re: GMS 14 to GMS 18 via new server

Hi Ken;

I got with support and come to find out you need to have a web development/tools package installed as well. It was added and after an uninstall and reinstall it's working.

John
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.