You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was running a node for several days, and then noticed my status -f window had crashed with the write EPIPE error.
That terminal window was hung. I had to Ctrl-C out (windows 11) to be able to re-run ironfish status -f
The node appeared to continue to run for the 2 days since the status command crashed.
I got the database locked error below when I did ironfish debug, plus the actual debug info.
Plenty of free RAM, no other obvious things wrong on this laptop.
Oddly when I stopped and restarted the node, it showed connected to the Iron Fish Network, but showed no block records for 9 minutes. After that I re-started.
status -f is showing continuously under 1M from head, so maybe "inside" the node was keeping up and I should have waited another minute or 2 for the next 10 blocks to be sync'd.
After a 2nd restart of the node, it's syncing blocks and shows 100%, so maybe just caught it when it had nothing new to display
Version
v0.1.74
Debug output
ironfish debug
Database cannot be opened, skipping output that requires database.
OpenError: IO error: LockFile C:\Users\markt\.ironfish\databases\chain/LOCK: The process cannot access the file because it is being used by another process.
at C:\Users\markt\AppData\Roaming\npm\node_modules\ironfish\node_modules\levelup\lib\levelup.js:119:23
at C:\Users\markt\AppData\Roaming\npm\node_modules\ironfish\node_modules\abstract-leveldown\abstract-leveldown.js:38:14
at C:\Users\markt\AppData\Roaming\npm\node_modules\ironfish\node_modules\deferred-leveldown\deferred-leveldown.js:31:21
at C:\Users\markt\AppData\Roaming\npm\node_modules\ironfish\node_modules\abstract-leveldown\abstract-leveldown.js:38:14
Iron Fish version 0.1.74 @ 41157bf
Iron Fish library 0.0.51 @ 41157bf
Operating system Windows_NT x64
CPU model(s) AMD Athlon Silver 3050U with Radeon Graphics
CPU threads 2
RAM total 5.88 GiB
Heap total 1.99 GiB
Node version v18.14.0
ironfish in PATH true
Garbage Collector Exposed false
Telemetry enabled true
Node name ProductGuy
Block graffiti ProductGuy
Relevant log output
Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at Socket._writeGeneric (node:net:930:11)
at Socket._write (node:net:942:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Writable.write (node:internal/streams/writable:337:10)
at RpcIpcClient.send (C:\Users\markt\AppData\Roaming\npm\node_modules\ironfish\node_modules\@ironfish\sdk\build\src\rpc\clients\socketClient.js:244:21)
at RpcIpcClient.request (C:\Users\markt\AppData\Roaming\npm\node_modules\ironfish\node_modules\@ironfish\sdk\build\src\rpc\clients\socketClient.js:230:14)
at RpcIpcClient.statusStream (C:\Users\markt\AppData\Roaming\npm\node_modules\ironfish\node_modules\@ironfish\sdk\build\src\rpc\clients\client.js:13:21)
Graffiti
ProductGuy
The text was updated successfully, but these errors were encountered:
What happened?
I was running a node for several days, and then noticed my status -f window had crashed with the write EPIPE error.
That terminal window was hung. I had to Ctrl-C out (windows 11) to be able to re-run
ironfish status -f
The node appeared to continue to run for the 2 days since the status command crashed.
I got the database locked error below when I did
ironfish debug
, plus the actual debug info.Plenty of free RAM, no other obvious things wrong on this laptop.
Oddly when I stopped and restarted the node, it showed connected to the Iron Fish Network, but showed no block records for 9 minutes. After that I re-started.
status -f is showing continuously under 1M from head, so maybe "inside" the node was keeping up and I should have waited another minute or 2 for the next 10 blocks to be sync'd.
After a 2nd restart of the node, it's syncing blocks and shows 100%, so maybe just caught it when it had nothing new to display
Version
v0.1.74
Debug output
Relevant log output
Graffiti
ProductGuy
The text was updated successfully, but these errors were encountered: