GW-Messenger 18.x starts to early when rebooting

[uwelabs]

OES 2018 SP1 with GW 18.2.1 and GW-Messenger 18.2.1

When starting or rebooting the server the parts of GW-Messenger are always trying to start to early. This process is repeating several times and in the end GW-Messenger has started completely and is running.

But it does not look good on the server text console with all those "failed".

In /usr/lib/systemd/system there are the start scripts
gwm-nmma.service, gwm-nmaa.service, gwm-mars@.service 
with the lines
Requires=arangodb3.service
After=arangodb3.service

I tried to change these into e.g.

Requires=arangodb3.service grpwise.service
After=arangodb3.service grpwise.service

but this does not help.

Has anybody an idea how to let GW-Messenger start after Groupwise?

Best regards, Uwe.

[uwelabs]

Really no one has an idea how to do this? 😞

[booktrunk]

Cheat and stick a sleep 30 or 60 second delay in at the top of the script? 

[uwelabs]

Thank you. I will try to find out how to do this if possible in a systemd start script.
Best regards, Uwe.