Skip to content
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

Closed
1 task done
freak12techno opened this issue Oct 28, 2024 · 3 comments
Closed
1 task done
Labels

Comments

@freak12techno
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

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:

validator@pion-testnet /tmp ❯ ls -laU | head -n 20                                                                                                                                        ✔ PIPE|0 12:04:50
total 2732664
drwxrwxrwt    1 root      root      59850752 Oct 27 12:04 .
drwxr-xr-x   18 root      root          4096 Jun 24 07:23 ..
drwxr-xr-x    4 validator validator     4096 Oct 23 16:40 neutrond553039366
drwxr-xr-x    4 validator validator     4096 Oct 23 14:44 neutrond2004005568
drwxr-xr-x    4 validator validator     4096 Oct 23 02:31 neutrond331565302
drwxr-xr-x    4 validator validator     4096 Oct 23 01:26 neutrond3645941473
drwxr-xr-x    4 validator validator     4096 Oct 24 21:24 neutrond2105281424
drwxr-xr-x    4 validator validator     4096 Oct 21 23:21 neutrond2013767621
drwxr-xr-x    4 validator validator     4096 Oct 23 10:12 neutrond2808888439
drwxr-xr-x    4 validator validator     4096 Oct 24 06:39 neutrond435430921
drwxr-xr-x    4 validator validator     4096 Oct 26 02:01 neutrond1138501452
drwxr-xr-x    4 validator validator     4096 Oct 21 06:02 neutrond2960233487
drwxr-xr-x    4 validator validator     4096 Oct 19 23:40 neutrond1006881956
drwxr-xr-x    4 validator validator     4096 Oct 26 17:16 neutrond2270539921
drwxr-xr-x    4 validator validator     4096 Oct 23 13:47 neutrond626593812
drwxr-xr-x    4 validator validator     4096 Oct 25 17:10 neutrond3787200811
drwxr-xr-x    4 validator validator     4096 Oct 20 20:20 neutrond2127120401
drwxr-xr-x    4 validator validator     4096 Oct 22 10:33 neutrond3242892381
drwxr-xr-x    4 validator validator     4096 Oct 25 12:15 neutrond693181263

validator@pion-testnet /tmp ❯ ls -1q | wc -l                                                                                                                                                       12:03:31
661652

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.

@juankaukian
Copy link

juankaukian commented Oct 28, 2024

Not related on cosmovisor, but the binary itself, it creates one directory in /tmp each time that [binary] status is executed.
Tested with gaia, neutron and osmosis with the same result.

p.s: thought it was related to the sdk version, but happens with .38/.48/.50 as well.

@freak12techno
Copy link
Contributor Author

Might be related to wasm, as all of these newly-created folders are empty and only have wasm files:

|-- neutrond3895874916
|   |-- data
|   `-- wasm
|       `-- wasm
|           |-- cache
|           |   `-- modules
|           |-- exclusive.lock
|           `-- state
|               `-- wasm
|-- neutrond397461145
|   |-- data
|   `-- wasm
|       `-- wasm
|           |-- cache
|           |   `-- modules
|           |-- exclusive.lock
|           `-- state
|               `-- wasm
|-- neutrond4073770021
|   |-- data
|   `-- wasm
|       `-- wasm
|           |-- cache
|           |   `-- modules
|           |-- exclusive.lock
|           `-- state
|               `-- wasm

Also I have it on two nodes: Neutron testnet (which has CosmWasm) and Osmosis mainnet (which also has CosmWasm)

@julienrbrt
Copy link
Member

Yeah, given what you say it looks like a cosmwasm issue. Could you open this in the wasmd repo?

@julienrbrt julienrbrt closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2024
@github-project-automation github-project-automation bot moved this from 📋 Backlog to 🥳 Done in Cosmos-SDK Legacy Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: 🥳 Done
Development

No branches or pull requests

3 participants