Openvms vgit push accvio issue

[Harikesh]

Getting accvio error while trying to access
vgit push command

[Harikesh]

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000000008A, PC=FFFFFFFF84B9F280, PS=0000001B

  Improperly handled condition, image exit forced.

    Signal arguments:   Number = 0000000000000005

                        Name   = 000000000000000C

                                 0000000000000000

                                 000000000000008A

                                 FFFFFFFF84B9F280

                                 000000000000001B

    Register dump:

    R0  = 0000000000000000  R1  = 000000007BA9A000  R2  = FFFFFFFF84CEC000

    R3  = 000000000000004E  R4  = 000000007FFCF818  R5  = 000000007FFCF8B0

    R6  = 0000000010000001  R7  = 0000000000000001  R8  = 0000000000000090

    R9  = 000000000000008A  R10 = 000000000000008C  R11 = 000000007ACFD140

    SP  = 000000007ACFD0D0  TP  = 000000007B6EAEC0  R14 = 0000000000000005

    R15 = FFFFFFFF84CEE1B0  R16 = 0000000000000078  R17 = 0000000000000000

    R18 = 000000007ACFD154  R19 = 000000007ACFD160  R20 = 0000000000000073

    R21 = 0000000000000073  R22 = 00000000FFFFFFFF  R23 = 0000000000000005

    R24 = 0000000000001369  R25 = 0000000000000001  R26 = 0000000000000000

    R27 = 0000000000001368  R28 = 0000000000000034  R29 = 0000000000979FDB

    R30 = 0000000000000400  R31 = 0000000000000004  PC  = FFFFFFFF84B9F280

    BSP/STORE = 000007FDBFFD47C0 / 000007FDBFFD4548 PSR = 000010130842E030

    IIPA = FFFFFFFF84B9F270

    B0  = FFFFFFFF84CEE2C0  B6  = FFFFFFFF84CEE1B0  B7  = FFFFFFFF84CEEC50

    Interrupted Frame RSE Backing Store, Size = 9 registers

    R32 = 000000000000008A  R33 = 00000000FFFFFFFF  R34 = 7A7A7A7A7A7A7A7A

    R35 = 0000000000000FA7  R36 = FFFFFFFFA841DA00  R37 = 0000000000000000

    R38 = 0000000000ADA7F8  R39 = 0000000000EBD340  R40 = C000000000000611

[Maurizio De Tommaso_]

Please, provide more information; for example :

1- platform (Alpha?, Integrity?, x86?)

2- OpenVMS release

3- Stack IP release

4- OpenVMS and Stack IP patch level

5- Vgit release you are using

/Maurizio

[Harikesh]

@Maurizio De Tommaso_ 

Hi Maurizio, these are details : openvms I64 ver 8.4 HP _BL860c_ i2  and vgit version 1.4.1 (Mar 2022)

[Maurizio De Tommaso_]

You have not collected all the information I have requested; please post the output of the following dcl command :

$ product show history

/Maurizio

[Harikesh]

@Maurizio De Tommaso_ 

Ok, thanks for suggestios .Please find required information

HP I64VMS TCPIP V5.7-13
HP I64VMS TCPIP V5.7-13ECO5
HP I64VMS VMS84I_UPDATE V15.0

HP I64VMS SSL1 V1.0-2R
VSI I64VMS VGIT V1.4-1

Is it ok , Plz let me know  if you need any further information from my end.

Thanks!

[Maurizio De Tommaso_ · Accepted solution]

Someone from your customer's support team installed Vgit kit V1.4-1 released by VSI on-top of HPE V8.4 VMS environment.

You should never mix VSI and HPE software on the same server (as reported several times by VSI themselves during their webinars; for example, refer to https://vmssoftware.com/docs/w2_Apr2018_Transitioning_to_VSI.pdf pag. 42) because HPE VMS V8.4 is not aligned with the latest OS and TCIP/IP patches, OpenSSL kits and RTL updates developed by VSI engineering for VMS V8.4-1H1 release and later.

Additionally, those who have installed the Vgit V1.4-1 kit may not have read the product release notes (https://vmssoftware.com/openkits/i64opensource/VSI-I64VMS-VGIT-V0104-1-1-RELNOTES. PDF); on p. 2 paragraph 5 states :

"5. Requirements

The kit you are receiving has been compiled, built, and tested using the operating system and compiler versions listed below (or comparable). While it is highly likely that you will have no problems installing and using the kit on systems running higher versions of the products listed here, we cannot say for sure that you will be so lucky if your system is running older versions.

• VSI OpenVMS 8.4-1H1 for I64 or higher
• VSI TCP/IP, HPE TCP/IP Services for OpenVMS, or MultiNet TCP/IP stack for network communication
• The utilities tar and zip must be installed and available to VGIT as foreign commands if you wish to use the archive command, and the GnuPG utility (gpg) must be similarly installed and available in order to sign and verify commits.

It is assumed that the reader has a good knowledge of OpenVMS and software development in the OpenVMS environment. Note that OpenSSL 1.1.1n is statically linked with the VGIT image supplied with this kit and it is therefore not strictly necessary to have VSI SSL111n (or higher) installed on the VSI OpenVMS
systems on which you will be using VGIT."

For the reasons listed above, it is not even possible for you to open a support ticket to VSI because your VMS configuration is unsupported; a solution I see is to update the VMS version to VSI V8.4-2L3 (including all related leyered); If you do not have an active subscription and support contract with VSI, I recommend you send an email to sales@vmssoftware.com and ask for a quote.

/Maurizio

[Harikesh]

@Maurizio De Tommaso_ 

Thanks for valuable responce on issue. Indeed we are aware about min requirement for  vgit 1.4.1 system. But they also mention a line i.e. we cannot say for sure that you will be so lucky if your system is running older versions. So I hope might be run becoz  we can use  vgit commands like: vgit status , vgit branch and vgit pull  etc., but incase of vgit push find issue, so I was confused. It means this issue  is os versioning issue. we can not implement  vsi vgit on HPE OS.

Thanks!

Regards,

Harikesh