Weird issue
Aprrentice opened this issue · 17 comments
Hi,
As always a great proxy, been running it for a while on EC2 but few hours ago miners were not connecting.
checked and found the proxy giving attached error.
ran update (though it was updated), restarted, had a green install.
.. but still the same error.
please advise.
thanks.
What's the size of your EC2 instance? For small ones (e.g. t2.micro) you need a swap cause they have not enough RAM for compiler stage... So binding are not compiled thus missing...
um... well I don't know. me zero in those stuff, I just follow the online tutorials. manage so far to have it running for like 6 month, but now got this.
how can check this? I use the free tier.
thanks.
this?
Size
8 GiB
In case it's in free tier i'm pretty sure it's T2.micro. You have to follow THIS guide. It's almost at the end...
this is the guide that I have followed.
I have started using it since mid of march 2020. running only XNP
managed to get this.
does it make any sense?
what's the physical size of your partitions? above screenshot showing inodes...
use df -h plz
was gogoling and ran those commands:
sudo apt-get autoremove --purge
du -sh /var/cache/apt/archives
sudo apt-get clean
guess it cleared some space
df -h below
okay, you have just 1.3GB free space on '/' so you cannot create 4GB swap file there...
thanks. what should I do?
is there a command to run for clearing up space?
Should this happen? shouldn't it last for a year?
thanks again.
first of all i'll try pm2 flush to remove logs...
du -a -h -d 1 will show you used size of current subdirectories
Swapfile is there but probably not attached. You can try to delete this file and repeat the 'create swap' steps once again. Then run npm i inside proxy folder...
if I know how to do that :)
Umm, i forgot on sometging... Could you run npm i once again and paste output on pastebin? Maybe the compiler fails because of missing dependencies... :/
uum...well been trying to figure it by googling... ran a lot of commands i found online... guess mess up with it... with no luck of reducing that xvda1 size.
thought by deleting the xmr-node-proxy would do something but it didn't.
me don't know about linux, I jsut copy paste commands.
guess i have to create a new account on AWS? or maybe delete or rebuild the whole thing...