The cardano-node relay stops running after about 15min, and can no longer SSH into the VM (the serial port log on the VM in GCP says ‘not enough disk space’ or no space left)
My machine is a e2-medium (2 vCPU, 4GB memory) w/ 10GB SSD VM hosted as a compute engine in GCP. I’m following instructions from the Stake Pool Course.
Here’s the log right when it happened:
Debugging & Questions
cardano-node run \ --topology testnet-topology.json \ --database-path db \ --socket-path db/node.socket \ --host-addr 0.0.0.0 \ --port 3001 \ --config testnet-config.json
When I do various
ducommands to check the size of my ~/cardano-node/db directory, its contents don’t look that large (the .dat files), does this imply that maybe it’s a file that’s not in ~/cardano-node/db that is consuming too much disk space? Log file hanging around somewhere?
Here is the output from running
htop, why is cardano-node listed so many times, that normal? 1 instance of it running but using or sharing more more CPU’s?
I run the commands
dfto observe memory and disk consumption, any key metrics to look for when running those? When I ran ‘tree’ I noticed the “available memory” was slowly dropping over time.
I captured this log right after a fresh cardano-node install but before running a node.
Any params I can tweak? Flags passed to
cardano-node run. I’m checking them now.
Need to update the testnet-config.json at all?
I have fresh install backup up via machine image and snapshot so can iterate on any suggestions! Thanks