Claude, i.e. did you check if some agents are still active after a stop ("ps ax | grep gwpoa"). Sometimes agents run outside of your rcgrpwise control ...

rcgrpwise is the old way of doing things (so rc* not as trustworthy as it used to be), whose effective support is diminishing, and we are migrating to the systemctl methodologies whether we like it or not (like UMC/IC for OES)  <sigh>

and to see ALL the GroupWise agents that may be running  "ps ax | grep gw"   gets you more that just the POA(s)  (all that thread spawning, reminds me of the Salmon, and bears catching them ;)

That's my preferred method since some time. But systemctl status grpwise does work well, too - and the corresponding start, stop, restart options are the actual methods to start and stop groupwise with all runnning agents.

rgrpwise did show some information about the state of the agents before showing the same information as "systemctl status grpwise", but that information was not always trustworthy. E.g. , if you had German characters in your configuration files, which are encoded in UTF-8 to allow systemctl to deal with them, the agents could not be found by rcgrpwise, because rc... typically expects files with 437 or 850 encoding, depending on codepage settings.

I just tested rcgrpwise status on my groupwise servers and it does not hang, but - as indicated above - does not show the correct status in the first lines for all agents.

Thanks, Diethmar, i will send you a mail, i have open a case with crtical prio

Take care if you want to upgrade on a actual oes24.3 server and gw24.3 build 145994.

we was able to duplicate this situation on a fresh installation.

With gw24.3 build 145961 there was ok and with the actual build groupwise will not start!

ATTENTION ! TAKE CARE!

a case is open, but for monday they will be no response!

May be that this is not trouble on a sles15sp5 server!

Andy, are you serious for you affirmation? When yes, please post for all you commands and the results for grpwise and not rcgrpwise!

i speak only from a new situation for gw24.3 build 145994 on a oes24.3 server with all actual patches. It is not only my trouble, we was able to duplicate this and can only say "take care" for all active members in this community

we have a good working network in Europe and we share information between us to help the latest groupwise administrators/integratoris/multiplicators!

Only in that I see the winds blowing that the underpinnings of rc* are being moved away, and may well start breaking before too long, if not outright cut out of the distros we use.  So we would be better equipped for figuring out this 'new' systemctl methodology to better get a handle on such problems as we move forward and the old init.d that rc* methods use, is deprecated.

I don't yet have those particular commands figured out for GroupWise yet. Part that I don't have an up-to-date GW system to readily test them on (too hot for the lab right now) and I suspect the dev team is more focused on getting the GW agents containerized instead of making sure that are fully systemd, and they clearly are not yet there from what I can see.

I can confirm that there are no troubles with Sles15SP5. I have upgraded some more environments without issues ...

I have the same build as you and the groupwise agents are running on 2 OES 24.3 servers with the POs and domains on nss-volumes and the system files are on ext4 or brtfs with eDir on xfs without problem.

You should have a service definition under /usr/lib/systemd/system/grpwise.service and of course this should be enabled (you can check that via yast).

To start the agents you could run "/opt/novell/groupwise/agents/bin/systemd/grpwised start" directly or via "systemctl start grpwise". But in fact the grpwised file under /opt/novell/groupwise/agents/bin/systemd/ should be the same as the grpwise file under /opt/novell/groupwise/agents/bin/ or under /etc/init.d .

I do not have docker containers enabled for groupwise  - as the server does only act as a groupwise server. So I have no idea, what happens, if groupwise runs in a container.

i had install a new groupwise testserver and had install the same build and this evening i had compare the files on the 2 servers.

And i had found a suspect file in /etc/opt/novell/groupwise/gwadminservice.conf

i had replace this file and after this, i can see the the command rcgrpwise start/status/stop/restart give response

we have seen with strace that anythink must be defect, but don't find the reason. OT-Support had become all screenshots!

After replacing this file, my groupwise system will work correctly on a oes24.3 server

see tomorrow if there are any troubles to see!

we was sure that gwdata was all ok!

i repeat: we must have a tool as umsServiceHealth for the GW-System.

Why is there not a clear message, when a conf, cfg or other file is corrupt? --> PAM: can you see if there is a possibility?

Thank all fro help!