Skip to main content

This all works correctly with a Linux host of Centos 7 and Rocky Linux 8 but not with Rocky Linux 9.

Host: Rocky Linux 9.4, docker 28.2.0 and MF Visual COBOL 6.0

When /var/microfocuslicensing/bin/startboth.sh is run as the docker image starts, lserv starts correctly and mfcesd seems to start but hangs so mfcesdchk fails to communicate with the license server.  A pstack of mfcesd shows:

On a Rocky Linux 9 docker image:
#0  0x00007fe3acf7c1f7 in close () from /lib64/libc.so.6
#1  0x000000000040ab11 in daemonize ()
#2  0x000000000040e7b5 in main ()

It takes over 10 minutes to actually start so that mfcesdchk returns correctly.

I am just trying to debug if this is a docker on Rocky 9 issue or inside the mfcesd daemonize code. 

Any ideas or trace info that can be turned on while mfcesd is starting up to determine where it is hanging?



------------------------------
Eric Hardesty
Rocket Software Forum Member
------------------------------

This all works correctly with a Linux host of Centos 7 and Rocky Linux 8 but not with Rocky Linux 9.

Host: Rocky Linux 9.4, docker 28.2.0 and MF Visual COBOL 6.0

When /var/microfocuslicensing/bin/startboth.sh is run as the docker image starts, lserv starts correctly and mfcesd seems to start but hangs so mfcesdchk fails to communicate with the license server.  A pstack of mfcesd shows:

On a Rocky Linux 9 docker image:
#0  0x00007fe3acf7c1f7 in close () from /lib64/libc.so.6
#1  0x000000000040ab11 in daemonize ()
#2  0x000000000040e7b5 in main ()

It takes over 10 minutes to actually start so that mfcesdchk returns correctly.

I am just trying to debug if this is a docker on Rocky 9 issue or inside the mfcesd daemonize code. 

Any ideas or trace info that can be turned on while mfcesd is starting up to determine where it is hanging?



------------------------------
Eric Hardesty
Rocket Software Forum Member
------------------------------

The licensing system automatically starts the daemon on demand when in a container environment, so I am unsure why you are trying to start the licensing system.

I could be wrong but my understanding Rocky Linux/Containers/Docker is not a supported scenario with v6.   

I think v9.0 was the first version where we supported containers with rocky linux and it was with podman & autopass.

@James Rowson / @Stephen kennington thoughts?



------------------------------
Stephen Gennard
Distinguished Technologist
Rocket Software Forum Member
------------------------------

The licensing system automatically starts the daemon on demand when in a container environment, so I am unsure why you are trying to start the licensing system.

I could be wrong but my understanding Rocky Linux/Containers/Docker is not a supported scenario with v6.   

I think v9.0 was the first version where we supported containers with rocky linux and it was with podman & autopass.

@James Rowson / @Stephen kennington thoughts?



------------------------------
Stephen Gennard
Distinguished Technologist
Rocket Software Forum Member
------------------------------

According to Project Management, we supported Rocky Linux 9.0 in VC/ED 9.0. As it's Rocky 9.0 it'll be podman.



------------------------------
James Rowson
Rocket Forum Shared Account
------------------------------


According to Project Management, we supported Rocky Linux 9.0 in VC/ED 9.0. As it's Rocky 9.0 it'll be podman.



------------------------------
James Rowson
Rocket Forum Shared Account
------------------------------

Hi Eric,

 

Please note that Rocket Software provides support for running in containers via the Visual COBOL "for Docker" products (these are different than the regular Visual COBOL products). Also as noted in a prior reply, running in containers on Rocky Linux was not supported in Visual COBOL 6.0.

Since you would need to upgrade, please consider moving to the latest version; Visual COBOL Development Hub for Docker/COBOL Server for Docker 10.0; here is a link to a docs page with information about Container support, which lists supported Operating Systems and container tools.



------------------------------
Blair McDonald
Lead Technical Support Specialist, AMC
Rocket Forum Shared Account
------------------------------

Hi Eric,

 

Please note that Rocket Software provides support for running in containers via the Visual COBOL "for Docker" products (these are different than the regular Visual COBOL products). Also as noted in a prior reply, running in containers on Rocky Linux was not supported in Visual COBOL 6.0.

Since you would need to upgrade, please consider moving to the latest version; Visual COBOL Development Hub for Docker/COBOL Server for Docker 10.0; here is a link to a docs page with information about Container support, which lists supported Operating Systems and container tools.



------------------------------
Blair McDonald
Lead Technical Support Specialist, AMC
Rocket Forum Shared Account
------------------------------

I will just continue using Rocky 8 as my host since that works in my Jenkins build environment with multiple docker OS versions.  I was just trying to see if I could figure out why the mfcesd starts after sitting for over 10 minutes as I debugged it but haven't figured out yet what it is waiting for.  I know that MF 6 works fine in my Rocky 9 host even if not officially supported.

I am stuck building/linking my product for the customers that are actually using older MF versions and don't move forward very quickly.

Thanks.



------------------------------
Eric Hardesty
Sr Software Engineer
Rocket Software Forum Member
------------------------------