starting testnet: consider using the --genesis-timestamp

[eosio]

starting testnet: consider using the --genesis-timestamp

[nathanielhourt]

Does this happen even if you point config.ini to the dummy genesis.json as described in the README?

[shuke0327]

@nathanhourt I meet the same problem as described in this issue. and, I pointed the config.ini to the genesis.json as decribed in the README, but, still get the warning.

[nathanielhourt]

Please show me the exact output, and also the contents of your config.ini file

[pmesnier]

The "warning" comes from producer_plugin, and is triggered when eosd is started with a pristine data directory. There is a genesis timestamp in the default genesis.json file, of March 30, so that's considered way old, hence the error message. Currently none of the plugins associated with eosd process --genesis_timestamp. Note that the timestamp in the json file is GMT.

[nathanielhourt]

Ahh, OK, so this will get worked out when people care more about eosd. :)

[pmesnier]

Support for --genesis-timestamp added in PR#77, merger pending

[nathanielhourt]

Is this issue now resolved?

[pmesnier]

yes.

…

On Wed, Jul 26, 2017 at 11:47 AM, Nathan Hourt ***@***.***> wrote: Is this issue now resolved? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2wCfdCWJxQdzj8O5fKmAOSkCIRSaj-ks5sR22YgaJpZM4OELT9> .

-- Phil Mesnier Principal Engineer & Partner OCI | WE ARE SOFTWARE ENGINEERS. tel [phone] x225 <(314)%20579-0066> ObjectComputing.com <http://objectcomputing.com/>

[Justin-ye]

I also come up with the same issue today, and can not produce a block