search

jpillora / overseer

Monitorable, gracefully restarting, self-upgrading binaries in Go (golang)
MIT License
2.33k stars 209 forks source link

Sanity check failed due to message output #14

Open icoris opened 8 years ago

icoris commented 8 years ago

Hi,

I've been testing the fetcher on my program and I always get a Sanity check fail in fetch(). I've added additional debug messaging to show tokenIn and tokenOut, and this is returned: 2016/09/20 08:02:18 [overseer master] sanity check failed:d57f1402568b9d42, 2016/09/20 08:02:18 INFO:EcomRate.bdb-ConfigLoad - Retry - 5

It seems that the first message that is returned on stdOUT from my code is a database load INFO message, instead of the token. This is most likely occuring due to my import load order and my defined init.

For a quick fix I'm going to comment out the tokenIn/tokenOut check. But for a longer term fix I think Overseer needs to have a init function defined that outputs the token.

jpillora commented 8 years ago

It needs to be documented though, before you print anything to stdout, at the top of main run overseer.SanityCheck().

yangyuan6 commented 3 years ago

image image I also encountered this problem and found the error by modifying the code debug. So, you should remove the output before starting

yangyuan6 commented 3 years ago

image image

Delete output before overseer.Run(overseer.Config !

yangyuan6 commented 3 years ago

See pull-request https://github.com/jpillora/overseer/pull/72