Error Ip not found for ElasticWebA0 : Ip null : Try increasing ProvisionPingIpSeconds in VMmark3.properties

[rhiancross01]

Getting the below issues. Most of the tile VMs deploy in

Have tried increasing the ping timeout setting and run again - same issue

2020-04-02T13:53:35.108 [pool-3-thread-7] INFO  COMM : AuctionMSQ0 : Scanning for IP

2020-04-02T13:54:27.959 [pool-3-thread-8] ERROR COMM : Error Ip not found for ElasticWebA0 : Ip null : Try increasing ProvisionPingIpSeconds in VMmark3.properties : Continuing

[RebeccaG]

Hi Rhian,

Thank you for uploading your logs as it's really helpful.

When you provisioned the first VMmark tile, it appears that most of your VMmark VMs were created and pinged successfully, but some failed. (Privately, you mentioned that if you reran the deploy, the same failure occurred but on a different VM each time) To me, this implies you are seeing intermittent network issues in your environment.

Please check this forum post which had the same error: VMmark ERROR and config help

There are some recommendations there of how to check your network setup as well as how the user resolved the issue.

Thank you,

Rebecca