This article explains how to set the correct time range and thus avoid the errors observed due to incorrect dates when upgrading a switch.
The following errors are observed while upgrading a switch:
/usr/libexec/ui/package: atexit: not found verify-sig: cannot validate /packages/db/pkginst.3158/manifest.ecerts format error in certificate's notBefore field: /C=US/ST=CA/L=Sunnyvale/O=Juniper Networks/OU=Juniper CA/CN=JuniperRootEcCA/[email protected] ERROR: cannot verify /packages/db/pkginst.3158 ERROR: Failed to add junos-arm-32-15.1X53-D52.tgz
Check the date by using the command: show system uptime
show system uptime
An error occurs if the current system date on the switch is in an invalid range .
Note: In some EX2300/EX3400 switches that are running Junos OS 15.1X53-56 or earlier, the system date might get reset to an invalid date, such as 2038-01-01, when the device is powered on after more than 5-6 days.
Set the current date from the shell as follows:
root@EX3400:RE:0% date 201701261925 Thu Jan 26 19:25:00 PST 2017
In order to enter shell mode from CLI, type the command: root@EX3400> start shell
root@EX3400> start shell
2018-05-30: Updated solution to imply that "date should be set from the shell to resolve the problem and not from CLI." Made other minor modifications (non-technical)