error: stat of /root/.chia/farmr/log*txt failed: No such file or directory #507
Replies: 1 comment 4 replies
-
|
Hi, please use the Log issue fixed there already. Sorry,! |
Beta Was this translation helpful? Give feedback.
-
|
I think I changed to :test but the problem persists. Here's my log file: File "/chia-blockchain/venv/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 1532, in _connection_for_bind During handling of the above exception, another exception occurred: Traceback (most recent call last): Message: 'Failed to delete old partials.' Arguments: () Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): Arguments: () Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): Arguments: () Traceback (most recent call last): --- Logging error --- Traceback (most recent call last): |
Beta Was this translation helpful? Give feedback.
-
|
Hi, looks like the Unraid cache disk is running out of space. This might be a run-away Farmr.net log. Please look to delete However, this could just be the Chia blockchain and other fork blockchains. For context, running ~10 blockchains, I'm using about 183 GB total. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again for your reply. My 2TB cache drive has repeatedly filled with .tmp plotting files, which I have deleted on 2-3 occasions. It currently has 1.7TB free. I restarted the docker and it's currently using 13% of the CPU (was 56% initially, then 38%). Log: File "/chia-blockchain/venv/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 207, in raise_ During handling of the above exception, another exception occurred: Traceback (most recent call last): Message: 'Failed to delete old partials.' Arguments: () Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): Arguments: () Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): Arguments: () Traceback (most recent call last): --- Logging error --- Traceback (most recent call last): |
Beta Was this translation helpful? Give feedback.
-
|
Hi, starting at the top of this Issue, we're working onward from a spurious log rotation warning, to disk full error, on to the root cause of failed plotting. Let's see what we can find. What we're looking in these Plotman logs is a message that explains why it may be failing to successfully plot. Maybe there is a broken binary or library, possibly bad memory if attempting to use madmax/bladebit in RAM? Let's see what the logs tell us. Stale tmp files is indicative of a failed plotting job (i.e. crash). FYI, thanks for your patience, as I am travelling with my family on holidays now, so I am only replying within a day, rather than within a couple of hours as I often do. |
Beta Was this translation helpful? Give feedback.
-
I have two machines set up similarly. One keeps putting this error in the log (like 9 times, in one block) and it stops using CPU. The other machine has port 8444 forward to it and seems to run fine.
Any advice please?
Beta Was this translation helpful? Give feedback.
All reactions