# \[EDIT\] Ethereum Cert-verifier, cert-issuer, cert-tools taking too long to execute

**URL:** <https://community.blockcerts.org/t/edit-ethereum-cert-verifier-cert-issuer-cert-tools-taking-too-long-to-execute/1675>\
**Category:** Support\
**Created:** [February 4, 2019, 9:00am UTC](https://community.blockcerts.org/t/edit-ethereum-cert-verifier-cert-issuer-cert-tools-taking-too-long-to-execute/1675 "2019-02-04T09:00:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![yoman](https://avatars.discourse-cdn.com/v4/letter/y/7bcc69/32.png) [@yoman](https://community.blockcerts.org/u/yoman)\
**Post date:** [February 4, 2019, 9:00am UTC](https://community.blockcerts.org/t/edit-ethereum-cert-verifier-cert-issuer-cert-tools-taking-too-long-to-execute/1675/1 "2019-02-04T09:00:59Z")

</div>

Hello there.  
I’ve installed everything just fine and i’ve been issuing and verifying certificates for quite some time now.  
The problem is that it suddenly decide to become the slowest process ever.

While it normally needed like 5 seconds to verify a certificate, the last couple of days it needs about 8 minutes for the verification. The same goes for issuing a certificate.

I’m running this on Ubuntu 18.04.1 on virtualbox. Can anyone help with this?

EDIT : Apparently it probably has something to do with ethereum ropsten. Also when i visit [https://ropsten.etherscan.io/](https://ropsten.etherscan.io/) there is message saying " **Notice:Data reindexing in progress, block data might not be up to date**" and the last transaction seems to be over 2 days ago.

And i get a new error now when trying to verify a certificate although i made no changes. Could Ropsten be the cause of this also? Thank you in advance.

 ![Capture](https://us1.discourse-cdn.com/flex016/uploads/blockcerts/original/1X/74bd5ce5f6275e839038d35fc2b6f8bf90b41609.png)

EDIT 2: Okay, so the verify command now works again although i did not change anything but it is still taking way too long to finish (same goes for cert-issuer,cert-tools), so i’m back at square one. Any help?

---

<div class="post-metadata">

**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\
**Post date:** [February 5, 2019, 4:05pm UTC](https://community.blockcerts.org/t/edit-ethereum-cert-verifier-cert-issuer-cert-tools-taking-too-long-to-execute/1675/2 "2019-02-05T16:05:07Z")

</div>

It’s possible that the etherscan api is to be blamed for it. I am not sure how many connectors we have set up for ropsten but part of the verification process would check the blockchain to see if that transaction exists. I am not sure what kind of logic is in place for this check, maybe there is a bug there that is causing it to be in a loop of continuously checking? or maybe it was getting something back from their api that it didn’t like? All possibilities.

I see that etherscan doesn’t seem to have that warning anymore, and the blocks look up to date. Could you try again?

---

<div class="post-metadata">

**Author:** ![yoman](https://avatars.discourse-cdn.com/v4/letter/y/7bcc69/32.png) [@yoman](https://community.blockcerts.org/u/yoman)\
**Post date:** [February 5, 2019, 5:35pm UTC](https://community.blockcerts.org/t/edit-ethereum-cert-verifier-cert-issuer-cert-tools-taking-too-long-to-execute/1675/3 "2019-02-05T17:35:20Z")

</div>

Yes, i mentioned in my 2nd edit that the verify command is back to normal (fixed when etherscan removed the warning). But the commands (issuing,signing and verifying certificates) still take way too much time to execute. What could be the problem?

---

<div class="post-metadata">

**Author:** ![akodate](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@akodate](https://community.blockcerts.org/u/akodate)\
**Post date:** [February 25, 2019, 11:31pm UTC](https://community.blockcerts.org/t/edit-ethereum-cert-verifier-cert-issuer-cert-tools-taking-too-long-to-execute/1675/4 "2019-02-25T23:31:44Z")

</div>

Hi yoman and aronning. I’ve been having a similar problem on a GCloud Debian VM (1 vCPU, 3.75 GB memory) with the issuing process. Although I can’t imagine why, a delay of up to 5 minutes occurs when I first create a template. After that, the rest of the process finishes relatively quickly.  
Do you think it might be an unexpected side effect of one of the Python libraries on Linux?

---

<div class="post-metadata">

**Author:** ![aronning](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@aronning](https://community.blockcerts.org/u/aronning)\
**Post date:** [February 26, 2019, 3:43pm UTC](https://community.blockcerts.org/t/edit-ethereum-cert-verifier-cert-issuer-cert-tools-taking-too-long-to-execute/1675/5 "2019-02-26T15:43:08Z")

</div>

I’m not sure, it’s possible. I don’t have a linux machine at the moment, and haven’t ran into long processing times on my mac.

---

<div class="post-metadata">

**Author:** ![akodate](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@akodate](https://community.blockcerts.org/u/akodate)\
**Post date:** [March 11, 2019, 10:44pm UTC](https://community.blockcerts.org/t/edit-ethereum-cert-verifier-cert-issuer-cert-tools-taking-too-long-to-execute/1675/6 "2019-03-11T22:44:36Z")

</div>

I’ve fixed this issue by increasing the RNG entropy using rng-tools5 on my VM!
