Protip: check your debug.log regularly

I’ve never used PowerShell, but from a quick google search looks like “-notMatch” would achieve what I described (trim out all INFO lines to see if any serious problems or warning are occurring):

select-string -path "*.log*" -notMatch "INFO"

But I don’t have a windows environment handy to test this… this is pure speculation based on documentation on my part.

1 Like

Is there a way to do this in bash on my mac as I don’t have Powershell?

Thanks!

Well yeah you’d use the standard Linux way grep wouldn’t you, since Mac is basically Unix?

My log folder is empty!
~/.chia/mainnet/log

Where can i find my logs?

I don’t know, that looks like the correct path. Is it under a different user? Because ~/ means current user, that may not be where it is…

When I set the server up, I entered a single user account, which is what I SSH in with. It’s also what I installed chia with and where I plot.

Im a quick learner but am fairly new to Unix still. I can see my plotter plotting when I SSH in and recal the screen. I’m lost. Can you tell?

Do you have your log level set to INFO and did you restart the Chia software after changing the log level?

That is the default location for your logs although you can check the config file to make sure. Any chance you installed as a different user?

1 Like

I have a lot of these in the log:

Err.DOUBLE_SPEND
WARNING: Wasn't able to add transaction with id
Consensus error 124, not disconnecting

Please don’t post pictures of console output. Google can’t index those and nobody can search for them. Try searching for those phrases here in the forum; there are already topics for them.

TL;DR I think that’s related to the negative amount bug they fixed in earlier versions, but searching is key and will give you the answers you require.

1 Like

Sorry about that, what I learned from the web is that nothing needs to be done about it…just ignore it…

1 Like

I’ve just checked config.yaml and logging was set to WARNING but the location was correct.

~/.chia/mainnet/logs

I’ve just changed the level to INFO.

Can i list the users on the server. As far as I am aware there’s only one user, and maybe root but I only setup one password when I installed it.

Thanks.

W

On Linux, the software doesn’t seem to pickup the log level change until it is restarted.

It sounds like you’ve done everything under one user account so my question about having switched users shouldn’t be an issue.

I didn’t need to recycle the server, theres now a log file and it has ALOT of info in it. Ive set this back to WARNING at the moment and will check it again in a while. What would you normally set your logfile to be?

I DIDN’T see any lines starting Farming plot plot-0-30.xxxxx.dat of size 30

My blockchain is still syncing, is that normal?

A post was split to a new topic: What do pre validate transaction and add_spendbundle mean in the logs?

I read most the comments here but I don’t understand what I am seeing in my logs

2021-05-19T12:31:23.132 full_node full_node_server        : INFO     <- new_compact_vdf from peer 16cd7b0a3dec4648927d93588daa408c55667e10929d47aef72c719119a053f6 98.230.192.221
2021-05-19T12:31:23.159 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory E:\System Volume Information, subdirectories not added by default
2021-05-19T12:31:23.160 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory G:\$RECYCLE.BIN, subdirectories not added by default
2021-05-19T12:31:23.162 harvester chia.plotting.plot_tools: INFO     Not checking subdirectory G:\System Volume Information, subdirectories not added by default
2021-05-19T12:31:23.198 harvester chia.plotting.plot_tools: INFO     Loaded a total of 42 plots of size 4.157430211775136 TiB, in 0.09208321571350098 seconds

2021-05-19T12:31:23.199 harvester harvester_server        : INFO     <- new_signage_point_harvester from peer fba31c2491be6288eaa41fe2aac5193723f2b8588c0e80a894ad423a429004b0 127.0.0.1
2021-05-19T12:31:23.200 harvester harvester_server        : INFO     <- new_signage_point_harvester from peer fba31c2491be6288eaa41fe2aac5193723f2b8588c0e80a894ad423a429004b0 127.0.0.1
2021-05-19T12:31:23.201 harvester harvester_server        : INFO     <- new_signage_point_harvester from peer fba31c2491be6288eaa41fe2aac5193723f2b8588c0e80a894ad423a429004b0 127.0.0.1
2021-05-19T12:31:23.204 harvester chia.harvester.harvester: INFO     0 plots were eligible for farming aea0b9b0ac... Found 0 proofs. Time: 0.00300 s. Total 42 plots
2021-05-19T12:31:23.208 harvester chia.harvester.harvester: INFO     0 plots were eligible for farming aea0b9b0ac... Found 0 proofs. Time: 0.00300 s. Total 42 plots
2021-05-19T12:31:23.212 harvester chia.harvester.harvester: INFO     0 plots were eligible for farming aea0b9b0ac... Found 0 proofs. Time: 0.00300 s. Total 42 plots

@codinghorror
hey dude, i thought id reach out, as i’ve just checked my debug log, and I have quite a few warning and error messages.

could you share some light on :

" 2021-05-26T13:30:37.866 full_node full_node_server        : ERROR    Exception:  <class 'concurrent.futures._base.CancelledError'>, closing connection {'host': '127.0.0.1', 'port': 8449}. Traceback (most recent call last):
  File "chia\server\server.py", line 536, in api_call
  File "asyncio\tasks.py", line 435, in wait_for
concurrent.futures._base.CancelledError

2021-05-26T13:30:37.866 wallet chia.wallet.wallet_node    : ERROR    Error while trying to fetch from peer:Peer returned no response Traceback (most recent call last):
  File "chia\wallet\wallet_node.py", line 605, in _sync
  File "chia\wallet\wallet_node.py", line 643, in fetch_blocks_and_validate
ValueError: Peer returned no response

2021-05-26T13:30:38.882 wallet chia.wallet.wallet_node    : ERROR    Loop exception in sync Was not able to add blocks 800-832. Traceback (most recent call last):
  File "chia\wallet\wallet_node.py", line 515, in sync_job
  File "chia\wallet\wallet_node.py", line 614, in _sync
RuntimeError: Was not able to add blocks 800-832

2021-05-26T13:30:58.835 full_node full_node_server        : ERROR    Exception:  <class 'concurrent.futures._base.CancelledError'>, closing connection {'host': '127.0.0.1', 'port': 8449}. Traceback (most recent call last):
  File "chia\server\server.py", line 536, in api_call
  File "asyncio\tasks.py", line 435, in wait_for
concurrent.futures._base.CancelledError

2021-05-26T13:31:02.139 full_node full_node_server        : ERROR    Exception:  <class 'concurrent.futures._base.CancelledError'>, closing connection {'host': '127.0.0.1', 'port': 8449}. Traceback (most recent call last):
  File "chia\server\server.py", line 536, in api_call
  File "asyncio\tasks.py", line 435, in wait_for
concurrent.futures._base.CancelledError "

Not really – but you could type those unique words into search and see what comes up!

I’ve got tonnes of these sorts of things too - I assume it’s just part of being a peer-to-peer network and some parts being ahead of others or something. Came up blank on searches and it’s not all that reassuring is it!

mine has alot of warning and error > HELP please

2021-05-29T07:47:22.327 full_node full_node_server : WARNING Banning 178.250.89.242 for 10 seconds
2021-05-29T07:47:22.807 full_node full_node_server : WARNING Banning 5.76.51.60 for 10 seconds
2021-05-29T10:34:23.432 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd3/plot-k32-2021-05-27-11-54-a8ae6f3b634ccd13e450958b7801d7c66884727658048f0ce146ea4950ee5bb3.plot took: 15.058499813079834. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T12:24:45.803 full_node full_node_server : WARNING Cannot write to closing transport 95.103.197.240
2021-05-29T13:02:12.148 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd5/plot-k32-2021-05-26-23-51-36981e747dfdf80fba4b69db9a0e21e13c0b0dca8be44b7006602896fc4d914d.plot took: 11.619502305984497. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T13:02:17.185 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd5/plot-k32-2021-05-25-08-36-ea5d8102ccaf558c256e226b76b7505eb5ec344cb2412215288157afe1b1156b.plot took: 7.254225254058838. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T13:53:38.422 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd1/plot-k32-2021-05-27-09-12-7eff3b54ed730c1411faf49b824feae3db3ebb1fd33e39f0afa6c84ea9d45cbf.plot took: 8.63490343093872. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T13:55:08.425 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd1/plot-k32-2021-05-28-12-11-9adea919f77bf91cb70056417f2b9ae193b2d1479b84286ca7cbed3aa0b8d564.plot took: 6.7464540004730225. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T13:57:03.277 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd1/plot-k32-2021-05-27-15-56-ce2e0d74740d88c736d0e3b7923d43577c0ab070ced7b4e64adde4230abeca5c.plot took: 6.013360500335693. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T13:57:48.403 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd1/plot-k32-2021-05-28-21-16-c8e1c9591ad3280056b8c2a9884fa8cf7bda4b170da38ebf68fbb027fd0cfc9b.plot took: 11.147310495376587. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T13:58:03.749 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd1/plot-k32-2021-05-24-22-14-e50c09357d62d9612d8966f5eb76c816fefd88c3faec7cb4bff2df378a1e1270.plot took: 6.3105127811431885. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T15:39:11.772 full_node full_node_server : WARNING Cannot write to closing transport 167.86.76.48
2021-05-29T16:57:44.118 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd3/plot-k32-2021-05-27-18-40-e8902d95d8e2f7304f60d11b6f6af5b191db962a0daa8a6c2b17c00fb4618742.plot took: 27.136685371398926. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T18:41:09.862 full_node full_node_server : WARNING Cannot write to closing transport 188.243.105.81
2021-05-29T21:47:42.674 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd7/plot-k32-2021-05-27-02-17-a518f30c58bff6ab6f51ab0054cf75cf2b571f04009328be4de0bc312b6b7134.plot took: 10.468794822692871. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T21:56:40.503 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd2/plot-k32-2021-05-27-03-38-e30ab52cf2f01de37d3f8c06c9d231bef303477db13eb8303faaf30c230f5a1e.plot took: 20.619661331176758. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T23:24:11.362 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd3/plot-k32-2021-05-27-05-08-2814a06c1917364074317bb720c0fa6df2cbf1949578a5369ad01eeca5405459.plot took: 23.313737869262695. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-29T23:27:37.637 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd3/plot-k32-2021-05-25-06-26-bfea47ff79e2e57902cdff99ef29f5b2dee4310b2299e8b9f06a90b516c3d2f5.plot took: 10.493980646133423. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-30T00:15:55.985 full_node full_node_server : WARNING Cannot write to closing transport 135.180.77.169
2021-05-30T00:37:23.198 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd4/plot-k32-2021-05-26-23-25-97ffe702bbfa7da94eeb17d870ba0318f3eb3d6a4c3f9fc49e7d5a5c5f7889ba.plot took: 16.94581937789917. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-30T01:51:42.939 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd5/plot-k32-2021-05-28-02-32-724822a308fa5edbe40b8255253697b643f2c98ed0c6ca899980b3488de1d752.plot took: 10.66405200958252. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-30T02:48:43.636 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd1/plot-k32-2021-05-26-19-49-71a938f8404a73bc061106775729dff4fa91803e0ac23c1fdd5aa07577b411c0.plot took: 39.4823260307312. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-30T04:14:57.323 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd2/plot-k32-2021-05-26-14-12-563a6a9e0d1f0770b9bd9e5add5611be3483b94cf20075be9e7bdbe563cfc435.plot took: 5.724911451339722. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-30T04:16:15.496 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd2/plot-k32-2021-05-24-23-14-77017232cd0187558495351bc4de915b94a22fbe15691042a5dc7db02a650593.plot took: 20.780689001083374. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-30T04:19:35.162 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd2/plot-k32-2021-05-26-14-12-563a6a9e0d1f0770b9bd9e5add5611be3483b94cf20075be9e7bdbe563cfc435.plot took: 48.733540296554565. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-30T05:47:31.726 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd3/plot-k32-2021-05-25-00-14-441402167a009ccf7e3020a24f2e2327abf450f8601d835d4635624e72bbc9d4.plot took: 15.460599660873413. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-30T05:48:25.301 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/hdd3/plot-k32-2021-05-26-15-46-6899e45c1abc128a945f627a2e435a92dcb406bc089a331bd1d1c69cc8f9d5e6.plot took: 23.583261251449585. This should be below 5 seconds to minimize risk of losing rewards.
2021-05-30T06:21:23.936 full_node full_node_server : ERROR Exception: Failed to fetch block 355881 from {‘host’: ‘67.180.198.160’, ‘port’: 8444}, timed out, {‘host’: ‘67.180.198.160’, ‘port’: 8444}. Traceback (most recent call last):
File “/home/rig2x570/chia-blockchain/chia/server/server.py”, line 526, in wrapped_coroutine
result = await coroutine
File “/home/rig2x570/chia-blockchain/chia/full_node/full_node_api.py”, line 104, in new_peak
return await self.full_node.new_peak(request, peer)
File “/home/rig2x570/chia-blockchain/chia/full_node/full_node.py”, line 372, in new_peak
if await self.short_sync_backtrack(
File “/home/rig2x570/chia-blockchain/chia/full_node/full_node.py”, line 322, in short_sync_backtrack
raise e
File “/home/rig2x570/chia-blockchain/chia/full_node/full_node.py”, line 307, in short_sync_backtrack
raise ValueError(f"Failed to fetch block {curr_height} from {peer.get_peer_info()}, timed out")
ValueError: Failed to fetch block 355881 from {‘host’: ‘67.180.198.160’, ‘port’: 8444}, timed out

1 Like

I have these on my second harvester (only) all over the place / in the debug.log. The “problem” (?) is: those plots are valid and they are contributing with partial-proof to SpacePool.

  • using chia check plots -n 100 -g (those plots) they are reported as 100% valid
  • SpacePool reports found partials from those plots as valid

And: if i bring those plots over to my primary full-node+harvester, the error isn´t displayed in the log file.

What can that mean? I generated them using MadMaxPlotter (latest version). Since chia reports them as “error” i´m irritated. Or are the MadMax plots different in size, but still 100% valid so i can ignore this error message?