syed_17 Super Contributor.
Super Contributor.
1846 views

Sles12sp3 server with Mobility18 crashed

Dears..
I have recently installed fresh GMS18.0.1p1 on top of a newly installed SLES12sp3 server after facing several failures upon trying to do inplace upgrade of gms2014r2hp2 from sles11sp4 to sles12sp2/sp3. It installed successfully and able to sync messages on mobile etc. Installed commercial wildcard certificate too for web administration and mobile device access. Everything appeared to be running fine for a few days with a couple of test users , that the sles12sp3 suddenly appeared to be crashed with out of memory errors.

I have no idea how to attach a screenshot here in the thread(would appreciate if guided thru), however, trying to list down some error messages from the crash window:

Out of Memory: kill process 413 (systemd-udevd) score31 or sacrifice child

Out of Memory: kill process 463 (haveged) score 32 or sacrifice child
.
.
.
Would highly appreciate all useful ideas.

Server Specs:
OS: sles12sp3 fully patched with online update
CPU: 2x2
Memory:6GB RAM
HDD:60GB root + 200Gb /var



I
Labels (1)
0 Likes
11 Replies
greiner Honored Contributor.
Honored Contributor.

Re: Sles12sp3 server with Mobility18 crashed

The newest Version of gms is 18.1.0 Build 308

we have no Problem with the actual sles12sp3 with all patches and the latest gms18.1.0 build 308 Version

Do you have enough ram Memory on the Server?
Do you have enough disk places on the Server?

Please install the newest Version of gms and test again! It will works correctly

Cg
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Sles12sp3 server with Mobility18 crashed

Cgreiner;2488467 wrote:
The newest Version of gms is 18.1.0 Build 308

we have no Problem with the actual sles12sp3 with all patches and the latest gms18.1.0 build 308 Version

Do you have enough ram Memory on the Server?
Do you have enough disk places on the Server?

Please install the newest Version of gms and test again! It will works correctly

Cg


I have got gms18.0.1 build 280 installed and it appears as latest patch on microfocus portal with release date June 2018.
patchfiles/groupwise-mobility-service-18.0.1p1-x86_64-280-SLES12.iso

Can you share the link for the build you mentioned as latest... thanks
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Sles12sp3 server with Mobility18 crashed

Hi,

18.0.1 Build 280 is the latest publically released version of GMS. What CG is referring to is only available via an SR. 18.1 has not been officially launched yet.

What you report in your crash I've not personally encountered. What file system are you running for /var ?

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
Knowledge Partner
Knowledge Partner

Re: Sles12sp3 server with Mobility18 crashed

Also have a look at this TID: https://www.suse.com/support/kb/doc/?id=7022353

Thomas
0 Likes
data5248 Absent Member.
Absent Member.

Re: Sles12sp3 server with Mobility18 crashed

I'm having the same problem and have SR open with both SLES and GroupWise. They are not sure on who's end is the problem.
0 Likes
data5248 Absent Member.
Absent Member.

Re: Sles12sp3 server with Mobility18 crashed

They got back with me with this link to VMware (I am on vmware 6.5) https://kb.vmware.com/s/article/2151480
I did option 2 and waiting to see what happens, so far been up for 3 hours. I did update another SLES sp3 to the latest patches and then it started crashing.
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Sles12sp3 server with Mobility18 crashed

laurabuckley;2488481 wrote:
Hi,

18.0.1 Build 280 is the latest publically released version of GMS. What CG is referring to is only available via an SR. 18.1 has not been officially launched yet.

What you report in your crash I've not personally encountered. What file system are you running for /var ?

Cheers,


I have xfs filesystem on /var whereas / is ext4
0 Likes
syed_17 Super Contributor.
Super Contributor.

Re: Sles12sp3 server with Mobility18 crashed

I appreciate all you guys feedback so far. After reboot the system hasn't crashed for last few days but still couldn't reach a satisfactory solution yet. I havent moved the existing production mobility(gms14) users to this freshly installed gms18 box. Can someone suggest a smooth transition steps so that Users don't feel the change by pointing the Old DNS entry to map to the new IP address. Are there any caveats to be taken care off.
I am using commercial wildcard certificate for device connection and mobility web administration.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Sles12sp3 server with Mobility18 crashed

In article <squadri.8oyz5z@no-mx.forums.microfocus.com>, Squadri wrote:
> Can someone suggest a smooth
> transition steps so that Users don't feel the change by pointing the Old
> DNS entry to map to the new IP address. Are there any caveats to be
> taken care off.
> I am using commercial wildcard certificate for device connection and
> mobility web administration.


As long as the new system's host name is in the certs, it should go
smoothly without users noticing.
Have done a couple going from self minted certs SLES11 based systems to
Lets Encrypt certs on SLES12 without user grumbles. Made the switch
overnight when we know the most sensitive users were going to be all where
we would be available the next morning and only saw them for other
reasons.


Andy of
http://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!
GMS troubleshooting tips at https://www.konecnyad.ca/andyk/gwmobility.htm


___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
booktrunk1 Absent Member.
Absent Member.

Re: Sles12sp3 server with Mobility18 crashed

I just have to say that this thread and especially this post is awsome!!

We upgraded a GMS server to 18.1 and SLES to sp3 Monday night. It died in a horrible heap, and we couldn't fix it Finally gave up wednesday and built a new one.... spend all yesterday fighting like hell with it dying from oom errors non stop... Pretty much ran out of ideas until i found this thread....

Did the fix been up for the last 7 hours. I could hug you!!

data5248;2488614 wrote:
They got back with me with this link to VMware (I am on vmware 6.5) https://kb.vmware.com/s/article/2151480
I did option 2 and waiting to see what happens, so far been up for 3 hours. I did update another SLES sp3 to the latest patches and then it started crashing.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Sles12sp3 server with Mobility18 crashed

In article <booktrunk.8qfdu0@no-mx.forums.microfocus.com>, Booktrunk
wrote:
> Did the fix been up for the last 7 hours. I could hug you!!


In lieu of hugs (given the distances), clicking on the Star below for
those who helped you the most would be appreciated.
After all, we do have a race on there:
https://forums.novell.com/memberlist.php?
order=desc&sort=reputation&pp=30
were we futilely attempt to catch up to our super sweet Laura


Andy of
http://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!
GMS troubleshooting tips at
https://www.konecnyad.ca/andyk/gwmobility.htm


___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
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.