-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: SDK binary (or cosmovisor?) creates a bunch of spam folders in /tmp #22385
Comments
Not related on cosmovisor, but the binary itself, it creates one directory in /tmp each time that [binary] status is executed. p.s: thought it was related to the sdk version, but happens with .38/.48/.50 as well. |
Might be related to wasm, as all of these newly-created folders are empty and only have wasm files:
Also I have it on two nodes: Neutron testnet (which has CosmWasm) and Osmosis mainnet (which also has CosmWasm) |
Yeah, given what you say it looks like a cosmwasm issue. Could you open this in the wasmd repo? |
Is there an existing issue for this?
What happened?
I have this thing on Neutron testnet node, and I saw people on Discord reporting this as well.
So, somehow, there are hundreds of thousands (for me it was like 1.3m) of folders being created under /tmp, with the same naming pattern:
/tmp/<binary name><some random number, probably block height>
.These folders are never deleted, eventually taking all of the free space of the server, even if the data folder of the node itself is on another volume.
Example on Neutron testnet:
I am not sure if it's related to Cosmovisor or to SDK though.
Cosmos SDK Version
v0.50.9 (on Neutron testnet)
How to reproduce?
This seems to happen somehow, not sure what's the way to reproduce it.
The text was updated successfully, but these errors were encountered: