proof work timeout

[Mateus224]

Describe the bug
during " Start campain...."
look on screenshot

** Configuration (please complete the following information):**

• Ubuntu 18.04
• 0.2.8

Additional context
See this Error the first time, never before

[alex031029]

proof work timeout is an error from AC (admission control). It can be caused by weak CPU capacity (AC runs a program, to see if the computer can finish it within a time window). Of course it could also be caused by bug.

Do you mind providing us your specs?

[Mateus224]

Hmm its an old i7 CPU but I had never this problem before why i m saying this is because as this error happened there where (yesterday) no transactions on the blockchain so there should be not much to do.

Internet: static IP, 1GB
CPU: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz

[kbaf]

Hi Alex,

If a calculation should be made within a time window, would i see a very high cpu usage of that process when the test is done? Could you tell me how many times in a time window that 'test' is done?

I am watching my CPU usage from my VCPU, but it never exceeds 50% and mostly it is between 0% and 6%

Could this test still impact RPT when the CPU does not exceed these percentages?

[alex031029]

@HKet reported me the same problem here.

For this AC part, we have a parameter difficulty to control how strict of this AC. A higher difficulty value requires RNodes' higher server specs.

During this Beta Test, we deliberately set a very low difficulty, since we know that there will not be many transactions. And this low difficulty value can account for @kbaf 's question.

However, a low difficulty should have very low chance that any user is rejected by AC simply due its low CPU benchmark. Thath's why I keep this issue open at the current stage.

[HKet]

@HKet reported me the same problem here.

For this AC part, we have a parameter difficulty to control how strict of this AC. A higher difficulty value requires RNodes' higher server specs.

During this Beta Test, we deliberately set a very low difficulty, since we know that there will not be many transactions. And this low difficulty value can account for @kbaf 's question.

However, a low difficulty should have very low chance that any user is rejected by AC simply due its low CPU benchmark. Thath's why I keep this issue open at the current stage.

My RNode characteristics are:
centos7

• 6 vCores (CPU usage 7% average)
• 16 GB RAM
• 320 GB SSD
• bandwith 5000GB

And based on these values we would not expect a "proof work timeout" error.
And since this option is decreased for the Betatest it looks like a BUG to me, this should not have happened in the current situation

[brammb]

Getting the same error after updating to 2.10
Haven't sealed a block since update.

Adress: 0x116143Ba590b7a7dc75f276243Da0A4bfC0Ae373
Version: 2.10

Hardware: VPS Windows Server 2019
6 vCPU
16GB RAM

INFO[05-31|11:52:30.957] campaign for proposer committee eleTerm=14784
INFO[05-31|11:52:30.957] Start campaign for dpor proposers committee
INFO[05-31|11:52:31.030] found nonce block hash=0x846acd04437472e873cce7e6418fe50ad47fe4159a73e0fd5de380bb87a273fb difficulty=12 nonce=1964 sender=0x116143Ba590b7a7dc75f276243Da0A4bfC0Ae373 timeCost(s)=0.0360098
INFO[05-31|11:52:36.001] work is not pass ac error is="proof work timeout"

[alex031029]

It seems like this bug still occurs in version 0.2.10. I will keep this issue open.

[HKet]

I suppose you mean 2.11 Grt, Hans Ketelaars Verstuurd vanaf mijn mobiele telefoon

…

Op 3 jun. 2019 om 10:51 heeft Yanchen ***@***.***> het volgende geschreven: It seems like this bug still occurs in version 0.2.10. I will keep this issue open. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[alex031029]

So far no one in 0.2.11 has reported this problem. But we didn't modify any logic related to this problem from 0.2.10 to 0.2.11. Thus, @brammb 's report in 0.2.10 should also exist in 0.2.11.