Thank you very much for your suggestion. *Best Regards！* *Chao Yan--------------**My twitter：Andy Yan @yanchao727 <https://twitter.com/yanchao727>* *My Weibo：http://weibo.com/herewearenow <http://weibo.com/herewearenow>--------------* 2014-08-14 8:56 GMT+08:00 James Polley <jp at jamezpolley.com>: > Hi Chao Yan, > > On Thu, Aug 14, 2014 at 9:07 AM, 严超 <yanchao727 at gmail.com> wrote: > >> *Verification failure* >> *3074320060 <3074320060>:error:2E099064:CMS >> routines:CMS_SIGNERINFO_VERIFY_CERT:certificate verify >> error:cms_smime.c:304:Verify error:certificate is not yet valid* >> > > Usually when I've seen errors like this, it was caused by machines not > having their clocks in sync. If the CA generating the cert has its clock a > little bit in the future it will generate a cert that isn't valid yet > > I'd suggest taking a look the cert, and checking the clocks on your > machines to make sure they're all correct - maybe one of them lost its > hardware RTC and ended up back in 1970 after a reboot, or something > peculiar like that. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140814/a8d986c1/attachment.html>