Hey I have a windows pc running nodeODX, the webodm is working fine but the nodeNodx keeps filling a 500gb ssd and then crashing whenever I try to do a bunch of maps.
The only fix I have found so far is to keep deleting the .vhdx file each time.
Gpu version or regular.
Any recommendations on how to make it get rid of the old cache data from each map when finished?
You can run NodeODX by passing the --cleanup_tasks_after <minutes> option. By default it's 2 days, but you can lower it so that results get deleted sooner.
OP
new problem... yay, since i had to close it last time there appear to be a spinning loop where it wont delete a task since it thinks the nods running it but refuses to put a new one in the que
the sending images one was uploaded 2h ago, according to webodm it can reach the node no problem but is not making progress.
Something looks stuck; I would try restarting the software
OP
fixed it sort of
OP
" "70df6839-5862-48d8-9f38-72a64ffffdce | 40 | A470 - 13/09/2026 | 1
4b58ea13-867b-45f5-95ee-de051a1d5dd5 | 40 | Mountain Pass 01 - 16/09/2026 |
2e129a0e-c029-4484-9513-5d95171a3933 | | jens+2 07,08,2026 | 1
95a5cfeb-12cd-441b-aaa3-80cc1a897541 | | jens+ 2 07,08,2026 | 2
e96a5f6e-32f2-45cb-ab94-e9ba8f3a2aac | | Yard - 21/09/2026 | 1
(150 rows) last number meaning the pending action""
OP
the status was 0 so apprently that means an endless loop of waiting?
OP
no idea what i did to cause that
if the computer ran out of memory, some unpredictable stuff can happen
This discussion happened in the WebODM community Discord. Join and ask your own question.
Join View Original ThreadThis page mirrors a public discussion from the WebODM Discord. How to request a removal.