Visual Cobol 7 Patch Update 05 - Licensing error | Rocket Forum

Hi everyone,

we recently tried upgrading one of our dev environments from VC 7 pu 04 to VC 7 pu 05.

("setup_visualcobol_devhub_7.0_patchupdate04_290113_suse_x64" -> "setup_visualcobol_devhub_7.0_patchupdate05_290480_suse_x64")

We use the option "4. Manual License Installation." as license activation mechanism from /var/microfocuslicensing/bin/cesadmintool.sh

Unfortunately we ran into some licensing issues regarding the MFSafeNet.service, after installing the newest VC 7 pu 05 Version. We get a licensing error, when running cobol programs, eventhough the license still is registered. We had no similiar problems with VC 7 pu 04.

Execution error : file ''
error code: 247, pc=0, call=1, seg=0
247 Licensing error (Error[5]: Cannot talk to the license server on host "127.0.0.1". Server may not be running.)

Apparently the systemd service "MFSafeNet.service" only starts the "lserv" now, but not the "mfcesd" process anymore:

VC 7 pu 04: systemctl status MFSafeNet.service (when active)
   CGroup: /system.slice/MFSafeNet.service
           |-2200 /var/microfocuslicensing/bin/lserv
           `-4180 /var/microfocuslicensing/bin/mfcesd

VC 7 pu 05: systemctl status MFSafenet.service (when active)

CGroup: /system.slice/MFSafeNet.service
`-11869 /var/microfocuslicensing/bin/lserv

When comparing the systemd-files (/usr/lib/systemd/system/MFSafeNet.service), we can see the following difference:

VC 7 pu 04:

[Service]
Type=forking
ExecStart=/var/microfocuslicensing/bin/startboth.sh
ExecStop=/var/microfocuslicensing/bin/stopboth.sh
Restart=no

VC 7 pu 05:
[Service]
Type=forking
ExecStart=/var/microfocuslicensing/bin/startlserv.sh
ExecStop=/var/microfocuslicensing/bin/stoplserv.sh
Restart=no

Why is only "lserv" started anymore in the newest VC 7 patch update 05 and not both "lserv" and "mfcesd". The problem is resolved when calling startboth.sh manually, but this can not be the right solution, because you'd have to call the startboth.sh script after each reboot ?

Yours sincerely

Martin

#license
#VisualCobol7
#MicroFocus
#COBOL
#PatchUpdate05
#LicenseServer
#VisualCOBOL
#VisualCobol7PatchUpdate05

Page 1 / 1

Hi everyone,

we recently tried upgrading one of our dev environments from VC 7 pu 04 to VC 7 pu 05.

("setup_visualcobol_devhub_7.0_patchupdate04_290113_suse_x64" -> "setup_visualcobol_devhub_7.0_patchupdate05_290480_suse_x64")

We use the option "4. Manual License Installation." as license activation mechanism from /var/microfocuslicensing/bin/cesadmintool.sh

Unfortunately we ran into some licensing issues regarding the MFSafeNet.service, after installing the newest VC 7 pu 05 Version. We get a licensing error, when running cobol programs, eventhough the license still is registered. We had no similiar problems with VC 7 pu 04.

Execution error : file ''
error code: 247, pc=0, call=1, seg=0
247 Licensing error (Error[5]: Cannot talk to the license server on host "127.0.0.1". Server may not be running.)

Apparently the systemd service "MFSafeNet.service" only starts the "lserv" now, but not the "mfcesd" process anymore:

VC 7 pu 04: systemctl status MFSafeNet.service (when active)
   CGroup: /system.slice/MFSafeNet.service
           |-2200 /var/microfocuslicensing/bin/lserv
           `-4180 /var/microfocuslicensing/bin/mfcesd

VC 7 pu 05: systemctl status MFSafenet.service (when active)

CGroup: /system.slice/MFSafeNet.service
`-11869 /var/microfocuslicensing/bin/lserv

When comparing the systemd-files (/usr/lib/systemd/system/MFSafeNet.service), we can see the following difference:

VC 7 pu 04:

[Service]
Type=forking
ExecStart=/var/microfocuslicensing/bin/startboth.sh
ExecStop=/var/microfocuslicensing/bin/stopboth.sh
Restart=no

VC 7 pu 05:
[Service]
Type=forking
ExecStart=/var/microfocuslicensing/bin/startlserv.sh
ExecStop=/var/microfocuslicensing/bin/stoplserv.sh
Restart=no

Why is only "lserv" started anymore in the newest VC 7 patch update 05 and not both "lserv" and "mfcesd". The problem is resolved when calling startboth.sh manually, but this can not be the right solution, because you'd have to call the startboth.sh script after each reboot ?

Yours sincerely

Martin

#license
#VisualCobol7
#MicroFocus
#COBOL
#PatchUpdate05
#LicenseServer
#VisualCOBOL
#VisualCobol7PatchUpdate05

Hi Martin,

Welcome to the Micro Focus Community Site. I'm sorry to hear about the issue you've encountered with SafeNet licensing after upgrading to Visual COBOL 7.0 Patch Update 5. Thank you for providing such complete information about the problem.

I will investigate the issue and report back what I learn. In the meantime, I'm glad that you've identified the workaround of using the startboth.sh script.

Blair

Hi everyone,

we recently tried upgrading one of our dev environments from VC 7 pu 04 to VC 7 pu 05.

("setup_visualcobol_devhub_7.0_patchupdate04_290113_suse_x64" -> "setup_visualcobol_devhub_7.0_patchupdate05_290480_suse_x64")

We use the option "4. Manual License Installation." as license activation mechanism from /var/microfocuslicensing/bin/cesadmintool.sh

Unfortunately we ran into some licensing issues regarding the MFSafeNet.service, after installing the newest VC 7 pu 05 Version. We get a licensing error, when running cobol programs, eventhough the license still is registered. We had no similiar problems with VC 7 pu 04.

Execution error : file ''
error code: 247, pc=0, call=1, seg=0
247 Licensing error (Error[5]: Cannot talk to the license server on host "127.0.0.1". Server may not be running.)

Apparently the systemd service "MFSafeNet.service" only starts the "lserv" now, but not the "mfcesd" process anymore:

VC 7 pu 04: systemctl status MFSafeNet.service (when active)
   CGroup: /system.slice/MFSafeNet.service
           |-2200 /var/microfocuslicensing/bin/lserv
           `-4180 /var/microfocuslicensing/bin/mfcesd

VC 7 pu 05: systemctl status MFSafenet.service (when active)

CGroup: /system.slice/MFSafeNet.service
`-11869 /var/microfocuslicensing/bin/lserv

When comparing the systemd-files (/usr/lib/systemd/system/MFSafeNet.service), we can see the following difference:

VC 7 pu 04:

[Service]
Type=forking
ExecStart=/var/microfocuslicensing/bin/startboth.sh
ExecStop=/var/microfocuslicensing/bin/stopboth.sh
Restart=no

VC 7 pu 05:
[Service]
Type=forking
ExecStart=/var/microfocuslicensing/bin/startlserv.sh
ExecStop=/var/microfocuslicensing/bin/stoplserv.sh
Restart=no

Why is only "lserv" started anymore in the newest VC 7 patch update 05 and not both "lserv" and "mfcesd". The problem is resolved when calling startboth.sh manually, but this can not be the right solution, because you'd have to call the startboth.sh script after each reboot ?

Yours sincerely

Martin

#license
#VisualCobol7
#MicroFocus
#COBOL
#PatchUpdate05
#LicenseServer
#VisualCOBOL
#VisualCobol7PatchUpdate05

Hi.

In the 7.0 PU5 release the some changes were made to give better control over the license services. Two issues were address. The first being that it was found that if lserv or mfcesd died and the restart was enabled in the service file that it would not automatically restart until both process had died. The second issue was with customer moving to the new Autopass licensing running lserv was no longer needed.

To resolve these issues the MFSafeNet.service file was split into two. The current file just running lserv and a new file MFCESD.service running the mfcesd service.

/usr/lib/systemd/system/
MFSafeNet.service
MFCESD.service
MFAutoPass.service

You can see the status of the new services here...

systemctl status MFSafeNet

systemctl status MFCESD

systemctl status MFAutoPass

Hi everyone,

we recently tried upgrading one of our dev environments from VC 7 pu 04 to VC 7 pu 05.

("setup_visualcobol_devhub_7.0_patchupdate04_290113_suse_x64" -> "setup_visualcobol_devhub_7.0_patchupdate05_290480_suse_x64")

We use the option "4. Manual License Installation." as license activation mechanism from /var/microfocuslicensing/bin/cesadmintool.sh

Unfortunately we ran into some licensing issues regarding the MFSafeNet.service, after installing the newest VC 7 pu 05 Version. We get a licensing error, when running cobol programs, eventhough the license still is registered. We had no similiar problems with VC 7 pu 04.

Execution error : file ''
error code: 247, pc=0, call=1, seg=0
247 Licensing error (Error[5]: Cannot talk to the license server on host "127.0.0.1". Server may not be running.)

Apparently the systemd service "MFSafeNet.service" only starts the "lserv" now, but not the "mfcesd" process anymore:

VC 7 pu 04: systemctl status MFSafeNet.service (when active)
   CGroup: /system.slice/MFSafeNet.service
           |-2200 /var/microfocuslicensing/bin/lserv
           `-4180 /var/microfocuslicensing/bin/mfcesd

VC 7 pu 05: systemctl status MFSafenet.service (when active)

CGroup: /system.slice/MFSafeNet.service
`-11869 /var/microfocuslicensing/bin/lserv

When comparing the systemd-files (/usr/lib/systemd/system/MFSafeNet.service), we can see the following difference:

VC 7 pu 04:

[Service]
Type=forking
ExecStart=/var/microfocuslicensing/bin/startboth.sh
ExecStop=/var/microfocuslicensing/bin/stopboth.sh
Restart=no

VC 7 pu 05:
[Service]
Type=forking
ExecStart=/var/microfocuslicensing/bin/startlserv.sh
ExecStop=/var/microfocuslicensing/bin/stoplserv.sh
Restart=no

Why is only "lserv" started anymore in the newest VC 7 patch update 05 and not both "lserv" and "mfcesd". The problem is resolved when calling startboth.sh manually, but this can not be the right solution, because you'd have to call the startboth.sh script after each reboot ?

Yours sincerely

Martin

#license
#VisualCobol7
#MicroFocus
#COBOL
#PatchUpdate05
#LicenseServer
#VisualCOBOL
#VisualCobol7PatchUpdate05

Hi again,

thanks for your fast/detailed responses !

We resolved the issues and successfully updated our dev environments to VC 7 patch update 05. (See answer from @StephanKennington).

I wanted to add that, if you're having trouble starting the systemd services after the installation of VC 7 pu 05, I recommend you to either

- try a clean restart of the machine

- or first make sure that all license servers are stopped (by calling /var/microfocuslicensing/bin/stopboth.sh) and then try to start all license servers:

/var/microfocuslicensing/bin/stopboth.sh

systemctl start MFSafeNet

systemctl start MFCESD

systemctl start MFAutoPass

Thanks again for your help!

Yours sincerely

Martin