marksammon Absent Member.
Absent Member.
628 views

Mobility Service Errors after running low on disk space

This morning my GMS service stopped. The free space dropped from 25% to around 7% in a couple of hours after adding a couple of users.

So I shut down the VM and added 200GB of space to the server. I then followed the tutorial on the Suse site to extend the BTRFS disk using the parted tool and all appeared good.

Once the machine was powered up the GMS service started and all looked OK. However, I am getting one error in the dashboard...

Event Processing: Events From Devices Pending Processing to Groupwise = 24200

I opened the terminal and checked the logs and am getting the following (about 8 per second)....
2019-04-12 16:41:57.374 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - 886282026765667969)
2019-04-12 16:41:57.712 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - 3304404260057603988)
2019-04-12 16:41:59.558 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - -5668517159584889578)
2019-04-12 16:41:59.779 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - 880439604730859532)
2019-04-12 16:41:59.820 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - -8093489671379322391)
2019-04-12 16:42:00.075 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - -5977069958251091536)
2019-04-12 16:42:00.142 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - 41330758311299185)
2019-04-12 16:42:00.164 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - 2502291842679024782)
2019-04-12 16:42:00.186 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - -286591746677863571)
2019-04-12 16:42:00.342 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - -2041026935521657392)
2019-04-12 16:42:00.407 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - -2367303400561871486)
2019-04-12 16:42:00.451 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - -3610524852762701161)
2019-04-12 16:42:00.783 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - 8371489619500930948)
2019-04-12 16:42:01.048 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - 6908484513872827213)
2019-04-12 16:42:01.339 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - -1581238246869786695)
2019-04-12 16:42:01.386 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - 6980947048906432307)
2019-04-12 16:42:01.544 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - -2430781631305994546)
2019-04-12 16:42:01.599 WARNING [DeviceEventMonitor_Thread] [engine:1191] [userID:] [eventID:] [objectID:] [Engine] Source conversion status: DROPPED (default.pipeline1.mobility - 1937613337862337288)


Can somebody point me in the right direction?

Thanks

Mark
Labels (1)
0 Likes
8 Replies
Micro Focus Expert
Micro Focus Expert

Re: Mobility Service Errors after running low on disk space

Hi Mark,

Please be aware that GMS is not supported on a BTRFS file system.

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

Re: Mobility Service Errors after running low on disk space

Hi Laura,

I'm not a linux user really. I'd never heard of the BTRFS file system until I ran out of space. I just installed SUSE with defaults and followed the install instructions for the GMS. This is what I ended up with.

Are you saying I need to re-install it now? :mad:

Thanks

Mark
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Mobility Service Errors after running low on disk space

"Default" contains "fault". Of course you don't necessarily have to wipe the entire box. You rather might want to just move GMS data (or the entire /var tree) to a partition formatted with a filesystem which does better with databases than BTRFS. Basically something like this
https://www.suse.com/de-de/support/kb/doc/?id=7015338
0 Likes
marksammon Absent Member.
Absent Member.

Re: Mobility Service Errors after running low on disk space

mathiasbraun;2498309 wrote:
"Default" contains "fault". Of course you don't necessarily have to wipe the entire box. You rather might want to just move GMS data (or the entire /var tree) to a partition formatted with a filesystem which does better with databases than BTRFS. Basically something like this
https://www.suse.com/de-de/support/kb/doc/?id=7015338


Hi Mathiasbraun,

Thanks for your reply.

In the end I went for re-installing SUSE and setting the partition to EXT4 with no separate /home partition.

Regards

Mark
0 Likes
marksammon Absent Member.
Absent Member.

Re: Mobility Service Errors after running low on disk space

Well that's a day I'll never get back! Thought I would add my experience here in case others have any issue in future.

I built a new machine with Ext4 and no BTRFS, created a new Trusted application, gave the new machine a different IP address but the same name and set it all up again. The machine registered itself with Groupwise and failed to startup the services correctly. After some messing about (and lots of cursing, wishing I could just go and get MS Exchange) I checked the original server and it was now getting errors about licensing and it being unable to contact Groupwise.

Mobile mail had been offline for about 24hrs at this point. I'd tried fumbling around in Linux logs for a while but decided to restore the original machine back to a known point, to then try and get some email flowing temporarily to keep some people happy and give me time to start again on the new machine. However, the restore of the GMS was also displaying the same error. This meant the issue was related to Groupwise and I didn't want to have to restore that as I could lose mails.

After some digging around I found the DSAPP program.

I'd removed the Trusted application I'd created for the new GMS server and shut it down. In the DSAPP was an option to re-register the GMS with Groupwise and this completed and removed the new errors. I ran the vacuum option in DSAPP and this freed a little bit of space on the disk. I hoped some mail would flow briefly as it had yesterday but it didn't. 😞

I wiped the new server and went through the setup again. The only difference this time was that I gave the machine a different hostname. This time it seemed to complete successfully. I'd previously found a reference in the connectors.xml that seemed to have been dynamically generated as a client reference it may use with the trusted application. i'm assuming because I used the same hostname, this broke things.

Following the instructions to put the new .pem certificate in the right folder, this didn't work and in turn broke the mobility service. Thankfully the DSAPP came to the rescue again and created the .pem file and installed it.

I'm hoping this is the end of the problem now. I'm off to get a quote for Exchange!
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Mobility Service Errors after running low on disk space

Cleanest solution for sure...
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Mobility Service Errors after running low on disk space

In article <marksammon.8ygkun@no-mx.forums.microfocus.com>, Marksammon
wrote:
> Well that's a day I'll never get back! Thought I would add my
> experience here in case others have any issue in future.


I've lots such days to other vendors products such as Microsoft's as
well. It is the pain of this industry that no one or vendor is immune
to.

Even before getting this far in the thread, I made sure to tell the doc
writers to point out no BTRFS for GroupWise systems in the
prerequisites section that is the minimum docs we should all be reading
before installing.

Remember that any quote for such a new email system is but a very small
part of the business costs. Is the reduction in your email security
worth it for this one instance of frustration that this other email
system is not immune to? You have lots of resources here to help you
with your GroupWise systems, including some of us who are consultants
available for hire, even if just for reviewing your design before
changes.


Andy of
http://KonecnyConsulting.ca/gw/gwmobility.html 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
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Mobility Service Errors after running low on disk space

In article <mathiasbraun.8yg53z@no-mx.forums.microfocus.com>,
Mathiasbraun wrote:
> "Default" contains "fault".


As someone who never just blindly accepts the defaults, that phrase is
so going into my standard tool kit, especially to reinforce that a
"best practise" is just a deFault starting place in a design that
doesn't necessarily work well in all cases.


Andy of
http://KonecnyConsulting.ca/gw/gwmobility.html 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.