Utility Server Patching on AVP

[watkil]

Hi All


Have done plenty of S8300e with AVP 7.1 with Utility server 7.1 but i have two S8300e server that will not patch getting error see below. i have used the same patch on all other servers that i have built anyone got a fix or are the S8300e broke

Avaya utility patch certificate in the patch file has not been correctly signed by avaya

[mlombardi1]

Can you post the full CLI output of the patch attempt including your command syntax?

[watkil]

[admin@Utility-Services ~]$ cd /tmp
[admin@Utility-Services tmp]$ /opt/avaya/common_services/update -i util_patch_7.1.2.0.0.07.zip
Installing/Uninstalling patches will stop and start tomcat/postgresql services
Do you want to continue? y or n

y
Archive: util_patch_7.1.2.0.0.07.zip
inflating: Util_Patch_7.1.2-0.0-07.noarch.rpm
inflating: RootSA.txt
extracting: signature.bin
inflating: util_patch.mf
extracting: Utility_Server_ID.txt
inflating: Utility_Server_Details.txt
RootSA.txt: C = US, O = Avaya Inc., OU = Avaya Product PKI, CN = Avaya File Signing Authority 2013
error 9 at 0 depth lookup:certificate is not yet valid
The certificate in the patch file has not been correctly signed by Avaya

[watkil]

Can you post the full CLI output of the patch attempt including your command syntax?

[admin@Utility-Services ~]$ cd /tmp
[admin@Utility-Services tmp]$ /opt/avaya/common_services/update -i util_patch_7.1.2.0.0.07.zip
Installing/Uninstalling patches will stop and start tomcat/postgresql services
Do you want to continue? y or n

y
Archive: util_patch_7.1.2.0.0.07.zip
inflating: Util_Patch_7.1.2-0.0-07.noarch.rpm
inflating: RootSA.txt
extracting: signature.bin
inflating: util_patch.mf
extracting: Utility_Server_ID.txt
inflating: Utility_Server_Details.txt
RootSA.txt: C = US, O = Avaya Inc., OU = Avaya Product PKI, CN = Avaya File Signing Authority 2013
error 9 at 0 depth lookup:certificate is not yet valid
The certificate in the patch file has not been correctly signed by Avaya

[mlombardi1]

"Certificate is not yet valid" could mean the time is wrong on your Utility Server. Try using an NTP source.