[BUILT FROM SOURCE] Are you running the docker image or did you built from source?
[x] Did you check the README.md for steps to run?
[x] Did you check logs? (either in console or in _logs directory)
For more information, see the CONTRIBUTING guide.
Description
If you run from source using forever then forever log the console output to a file by default. If you do this then you have a log of over 950MB after some hours.
Steps to Reproduce
Run latest version of the miner
Expected behavior: The output should not contain the same warning so many times
Actual behavior:WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
In the log of 7851022 lines I have 7010225 lines of this warning. 89.29% of the output is the same warning.
If you check the timestamps then you see that many entries are written in the same second.
Versions
(0.5.5/b320107)
Application (required)
You can get this information:
Built from source
Run the miner using forever:
forever start ./bin/cli start --miner-key CryptoSmileee --node --ui --ws
2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.601Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.601Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
2018-05-08T06:01:43.601Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it
Prerequisites
_logsdirectory)For more information, see the
CONTRIBUTINGguide.Description
If you run from source using forever then forever log the console output to a file by default. If you do this then you have a log of over 950MB after some hours.
Steps to Reproduce
Expected behavior: The output should not contain the same warning so many times
Actual behavior:
WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() itIn the log of 7851022 lines I have 7010225 lines of this warning. 89.29% of the output is the same warning.
If you check the timestamps then you see that many entries are written in the same second.
Versions
(0.5.5/b320107)
Application (required)
You can get this information:
forever start ./bin/cli start --miner-key CryptoSmileee --node --ui --wsEnvironment (optional but helpful)
Logs
Download full log: http://telobot.com/_iv_.log
2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.599Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.600Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.601Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.601Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it 2018-05-08T06:01:43.601Z WARN utils.time TimeService did not sync at least once, either there is error while syncing or you have to start() it