/root/backup dir takes up 12G

[jlsam]

Issue description

As per request in Discord, I am reporting that I found /root/backup/AutoGitUpdate taking up 12G I can give access to the server via https://www.teleconsole.com/ I haven't deleted the dir yet, I still have space.

https://cdn.discordapp.com/attachments/520974921896296468/954461226514133052/unknown.png https://media.discordapp.net/attachments/520974921896296468/954461572862992434/unknown.png https://cdn.discordapp.com/attachments/520974921896296468/954461902493351936/unknown.png

Specifications

• Node version: v14.19.0
• Platform: Ubuntu
• Node wallet: 0x244Fe85783E323ccE1c73FE59feB21D04DA40fE6
• Node libp2p identity: QmWJPi9KQEUZaSw1kiBanEKLPhBjbPzAvTpxtkMJb9px3N

Contact details

• Email: [email protected]

[Valcyclovir]

The backup folder basically contains of all data your node holds which is taking up most of the space. Since node runners have been spamming the network, it is normal that the ot-node/data folder is filled quickly. Since update 1.30 new caps have been put to limit the amount of publishing and therefore data in your node will be growing a lot slower.

The problem with this ackup folder is if you want to rebuild your node completely, the backup folder needs to be manually deleted or else it will keep accumulating over time with data from your old node mixed with your new node.

As all backups, it is not absolutely necessary especially in a testnet environment. Unfortunately, the backup process is hardcoded and there are no options to turn that off for now. An easy workaround would be to create a cronjob to schedule a daily/weekly wipe of your backup folder.

For example, you can input the following command to add a cronjob to delete backup folder every Sunday at midnight crontab -l | { cat; echo "0 0 * * 0 rm -rf /root/backup"; } | crontab -

=========================

if you are strugglnig with space, as a sidenode, you can also limit the amount of logs your system keeps with the following command: #reduce your current log size to 50mb journalctl --vacuum-size=50M

#set maximum log size to 50mb sed -i 's|#SystemMaxUse=|SystemMaxUse=50M|' /etc/systemd/journald.conf systemctl restart systemd-journald

[jlsam]

Current disk space is not an issue, but it will be eventually.

I already had the SystemMaxUse setting in place and that helped a lot.

What seems to be taking up space is the git autoupdater, not the mysql or blazegraph... Also this backup dir takes more space than ot-node/. Is this is just a backup, where are the main data being kept?

[Valcyclovir]

the backup dir can be deleted without any repercussions to the functionalities of the node and dependencies. As to why your backup dir is so big specifically, you'd have to look at the files within individually. I suspect it's the AutoGitUpdate/backup/data folder that's taking up all the space, and that's exactly where your node stores its data. If you have done a few reinstalls of your node, this might cause the data in the backup dir to accumulate over time.

[NZT48]

This issue is being closed as inactive due to the date of the last activity on it. If you believe this is still a problem, please create a new issue and confirm that it is reproducible in the current ot-node release version. We are working towards closing open issues that meet specific criteria and ask you to create a new one for those that that are truly bugs in current release. We'll be monitoring those issues so that they are properly managed.

Thank you, OriginTrail Team