cPanel & WHM update failure in upcp script - scripts/updatesigningkey - update to v84.0.5

morrow95

• October 30, 2019 11:48

I initiated an update manually through WHM to v84.0.5 yesterday evening - the gui reported everything was fine and didn't notice any trouble. This morning I get an email that upcp did not exit cleanly when it ran : Maintenance ended; however, it did not exit cleanly (256). The following events were logged: "scripts/updatesigningkey". Review the update logs to determine why the update failed. Update log preview: ... ... [2019-10-30 04:50:21 -0400] E [/usr/local/cpanel/scripts/updatesigningkey] The "/usr/local/cpanel/scripts/updatesigningkey" command (process 63781) reported error number 1 when it ended. ...
What should I check out to make sure everything is good here?

• 

  cPanelLauren

  • October 30, 2019 20:19

  Hello, What's the output when you run the updatesigningkey script on its own? /scripts/updatesigningkey
  

  0
• 

  morrow95

  • October 30, 2019 20:32

  info [updatesigningkey] Retrieved public key from vendor: cpanel, category: development, url: https://securedownloads.cpanel.net/cPanelDevelopmentKey.asc info [updatesigningkey] Retrieved public key from vendor: cpanel, category: release, url: https://securedownloads.cpanel.net/cPanelPublicKey.asc
  

  0
• 

  cPanelLauren

  • October 30, 2019 21:10

  Can you show the full output that you received when you ran that? For example when I run it: [root@server ~]# /scripts/updatesigningkey [root@server ~]#
  That output doesn't show an error specifically - if you run /scripts/upcp
  again does the error still occur?

  0
• 

  garconcn

  • October 30, 2019 21:23

  I got the same error from multiple servers this morning. It doesn't look like the error occur after run upcp(I only test on one server).

  0
• 

  cPanelLauren

  • October 30, 2019 21:41

  I wonder if there was a connectivity issue with the licensing servers during the time of the update. I'd suggest allowing the automatic maintenance to run tonight and checking if the issue persists. If so I'd open a ticket, so we can look into it further. If you do choose that route, please update this thread with the ticket ID and we'll follow up here with the outcome. Thanks!

  0
• 

  morrow95

  • October 30, 2019 23:32

  I did show you the full output of when I ran /scripts/updatesigningkey - the output is what I put in the reply. I just ran it again and there is no output - just a new prompt like you showed. I will see what happens in the morning and whether upcp ran correctly or not.

  0

Please sign in to leave a comment.