Ok, so started as a relay… can u go inside the priv/pool/foldername and check the permision for vrf.skey file?
should be 400
chmod 400 vrf.skey
it’s gLive is showing it as the core node
What? I don’t understand the question… if it was a question 
it’s not started as a relay.
the POOL_NAME line is commented out, but gLive says
> Cardano Node - (Core - Mainnet) : 1.30.1 [0fb43f4e] <
Can u share the glive?
> Cardano Node - (Core - Mainnet) : 1.30.1 [0fb43f4e] <┌────────────────────────────────┬────────────┬────────────────────────┐
│ Uptime: 00:25:37 │ Port: 5551 │ Guild LiveView v1.22.4 │
│--------------------------------└────────────┴────────────────────────┤
│ Epoch 298 [30.4%], 3d 11:34:34 remaining │
│ ▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖ │
│ │
│ Block : 6411389 Tip (ref) : 43503926 Mem (RSS) : 4.3G │
│ Slot : 131123 Tip (node) : 43503923 Mem (Live) : 3.3G │
│ Density : 4.869 Tip (diff) : 3Mem (Heap) : 4.2G │
│ Total Tx : 0 Peers In : 3 GC Minor : 39086 │
│ Pending Tx : 0/0K Peers Out : 2 GC Major : 810 │
├─ CORE ───────────────────────────────────────────────────────────────┤
│ KES current/remaining : 335 / 40 │
│ KES expiration date : 2021-12-22 03:44:51 CST │
│ Missed slot leader checks : 0 (0.0000 %) │
│- BLOCKS -------------------------------------------------------------│
│ Leader : 8 Adopted : 0 Missed : 1 │
│ Ideal : 3.84 Confirmed : 0 Ghosted : 0 │
│ Luck : 208.33% Invalid : 0 Stolen : 0 │
│- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - │
│ 11:42:46 until leader │
│ ▌▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖ │
└──────────────────────────────────────────────────────────────────────┘
TG Announcement/Support channel: Telegram: Contact @guild_operators_official[esc/q] Quit | [i] Info | [p] Peer Analysis
Guild LiveView terminated, cleaning up…
Ok, then it should be fine… now go to config.json and set to true the TraceMempool then restart the node
Check if it will start again… also did u added your relay inside the topology file right?
PS: and inside the env u commented the pool name line? Hmm they must changed something to scripts… I don’t get it…
Ok, then it should be fine… now go to config.json and set to true the TraceMempool then restart the node
done.
Check if it will start again… also did u added your relay i side the topology file right?
yep.
PS: and inside the env u commented the pool name line? Hmm they must changed something to scripts… I don’t get it…
me either. maybe it looks at what key files are in the PRIV folder now?
would it be awful to just set the entire /opt/cardano folder to 700 permissions?
If now is working, you should not modify anything…
make few tests… restart the all server and check if it will start… if yes it meaning the problem is solved
check if u uncomment the pool name inside the env the node will fail to start
OH!! it’s a relay again! what is going on?!
and I thought it was working when I missed that block. I had minted a block just a few hours earlier in the previous epoch.
Ok, then it means u didin’t restarted before after u commented the line
uncomment the pool name again (check if the name match with the folder name … it’s case sensitive)
and restart the node
PS: u will see Relay till the node will start
Ok, then it means u didin’t restarted before after u commented the line
I can see the line in my terminal where I did it though. in the log, too.
uncomment the pool name again (check if the name match with the folder name … it’s case sensitive)
done, and yeah, it matches.
and restart the node
done.
PS: u will see Relay till the node will start
showed as Core almost immediately somehow.
ok, well this start didn’t show any errors in the log, just the usual sockets file not cleaned up warning.
next block is in 11 hours and 30 minutes, and it’s 5:30 AM here. I’ll look at this tomorrow after I get some sleep.
Thanks SO much for your help and patience. Can I send you some Ada or something for your help?
hopefully something we did fixed the problem! I restarted the node again just to test and only saw the socket file warning again. This time gLive took a second to show it as a core node. maybe last time I just took a second to look at it. I am a bit sleep deprived!
1 Like
Go to relax, if u are coonected to the relay and u have tx processed then it should be fine
1 Like
Just minted a block.
Yet after a system reboot earlier today the errors remained. (multiple node restarts, unable to open files, EKG port nonsense, etc.)
I’m going with the theory that none of these errors are affecting the node once it’s actually started successfully, and the missed block was the result of the 50+ GB of logs completely filling the storage.
Maybe I’ll put in a feature request on the cntools GitHub to limit log size/auto-purge anything older than a month or so.
And I think I’m going to just completely rebuild the entire server from scratch, since nothing we do seems to fix these issues. I can just transfer the keys once my network guru assigns the static IP over to the new vm.
Thanks again for your help trying to figure this out!
1 Like