Link
click to show
click to show
https://github.com/monero-project/monero/releases/tag/v0.18.5.0
Monero v0.18.5.0 Available from the terminal update menu.
Did my update this morning on my RockPi 4A, all working ok.
M here it stopped working again after a power outage also, manually restarted again and said it was running but wallet couldn't connect to it, now I've done yet another fresh install with Armbian (Ubuntu 26.04) and as usual it doesn't work. Tor node doesn't even start, clearly PiNodeXMR is broken somewhereD Link
click to showIn order, we need to get things running and prove where the issue is. What Wallet software do you use? The Monero GUI/Monerujo wallet app etc? 1) Get Monero running as per the (sorry for length of it - but I'm always here to help). We need an Active-running status. 2) Prove the wallet works. There are 3 common connection methods in levels of complexity (but all manageable): a) A Local Connection | Connecting Your PiNodeXMR node to a wallet that is WITHIN your home network. SO Monero GUI on another PC/laptop connected to your WiFi, or Mobile wallet on your WiFi. Your node will commonly have a hostname of pinodexmr.local and a port of 18081 - or rather than hostname you can specify the local IP of the node which at home commonly looks 192.168.X.XXX Once you're happy the node can connect locally, test externally: b) This will require port forwarding: https://github.com/shermand100/PiNodeXMR/wiki/Manual#connecting-a-wallet---external-connections Once ports are forwarded (for wallet use just 18081) enter you external IP address or configure dynamic DNS to follow your IP and get a hostname. Try and connect. In my case I connect remotely from my mobile wallet using my free hostname of pinodexmr.hopto.org and port 18081, try it if you want. c) Tor connection - This is why I use Monerujo, because it comes with it's own tor wrapper. A clearnet connected wallet cannot see tor nodes. ...
Thats not ideal and is often a corrupted blockchain.
The way to check is to look at the logs, but if thats not clear you can rename the blockchain which will mean the node will try to sync from scratch, proving monero is ok, and you can go from there.
Pop packs is an option from the terminal menu but it very rarely works but can be worth a try
Pinned - Troubleshooting help
So the "activating (auto-restart)" Only serves to show you there is a problem which needs investigating.
Simply put it can be only really be 1 of 2 common things, but each of those things has a couple of sub categories.
As I get this question alot I'll do a lengthy trouble shoot here and I'll post it elsewhere for others to reference:
The best way to find the actual issue to to look at monerod.log from the web-ui logs page. If for some reason (usually a permission problem) you can't download it, it can be found at /home/pinodexmr/.bitmonero/bitmonero.log
When Monero fails to start, a feature called systemd will try and auto-restart the failed service every 30seconds. For that reason your log file may look massive, but in reality it will be a lot of the same information repeated every 30seconds.
To help you, the mad numbers in the left column are the time-stamp of the entry. Likely many hundreds of entries will be made in those 30seconds but you are nterested in those that specify 'ERROR' in capitals and that preceed something to the effect 'stopping service'.
If it's too confusing, that's fine, just send me the log file and I'm happy to help, often the solution is simple once the cause is found. At the core of it, it can be either (1) Monerod as an Application or (2) The blockchain.
I order of most likely for each category...
Possible cause:
(1)a: Monerod failed to build correctly on last update or initial install and so cannot start.
(1)b: Monerod fails to start due to a parameter not loading correctly (ie: you've specified it to use an unavailable or impossible RPC port number).
(2)a: Blockchain corrupted due to sudden power outage.
(2)b: Blockchain stopped syncing/fails to start due to insufficient storage space.
Solutions:
Monero:
(1)a: The monerod.log file would likely have an entry similar to '/home/pinodexmr/monero/build/release/bin/monerod' file or path not found.
To fix this, simply go to the terminal menu and re-select
Link
click to show
click to show
Blockchain:
(2)a: By far the most commonm issue, which is frustrating because Monero uses a bespoke database design specifically designed to mitigate this risk ( Worth a read for the slightly technical ) - https://en.wikipedia.org/wiki/Lightning_Memory-Mapped_Database - You'll notice it's designed by Howard Chu, who is a long time contributer to the Monero codebase and workgroups.
Anyway, despite best efforts corruption still unfortunately happens.
In the Monerod.log file confirm Monero is running (meaning it can only really be the blockchain), and look for ERRORs in capitals regarding invalid blocks or transactions.
Option 1) Pop blocks - Select the node to stop. Go to the terminal menu and select option '4' Node Tools, then option '3' Pop BLocks. This will use a tool to select a number of blocks to remove from your blockchain. The thinking here is that if you have corruption at the end of the blockchain you can 'pop' it off the end and resync with good data. In theory that is, but I've never had much luck myself with this tool - just saying this to manage expectations.
Option 2) Confirm it is indeed a bad blockchain before deleting to re-sync. Unfortunatly there arn't many other options available, so what we do is re-name the /.bitmonero/lmdb directory to anything other than it's current name so that Monero cannot find it. This will make Monero sync from block 0 again.
Outcome 1) Monero starts ok and begins to sync from block 0. This proves Monero is fine and the old blockchain was corrupt. Delete the old blockchain.
Outcome 2) Monero still doesn't start, meaning the blockchain actually may be fine, we can restore it my giving it back it's old name. Troubleshoot above for suspected bad Monero.
Relevent commands:
Re-name lmdb folder for 'Option 2':
mv /home/pinodexmr/.bitmonero/lmdb/ /home/pinodexmr/.bitmonero/lmdb_old/
Revert lmdb file name in cse of 'Option 2', 'Outcome 2'
mv /home/pinodexmr/.bitmonero/lmdb_old/ /home/pinodexmr/.bitmonero/lmdb/
Delete old '
Link
click to show
click to show
P2Pool v4.16 released 10 minutes ago, I'm fortunate today to be able to catch this as it came out so PiNodeXMR P2Pool update is available via the terminal menu as usual.
This is a mandatory update for P2pool to mitigate a found vulnerability.
https://github.com/SChernykh/p2pool/releases/tag/v4.16
https://github.com/shermand100/PiNodeXMR/commit/948cb9a7492f4cb2288fc82922b80261cb8ef066
Link
click to show
click to show
🔵 jahway603: According to the PiNode-XMR manual, https://github.com/shermand100/PiNodeXMR/wiki/Manual, it shows that Ubuntu LTS 22.04 is used, but it may be using a newer version than that now - I'm not sure. What versions of Ubuntu are others running?
Recently noticed that my node was down. A week ago everything was running smoothly with access to the Web-UI from other computers on the network. RockPro64 with PiNodeXMR running on a USB drive and the blockchain on a SSD. Connected a monitor and keyboard, reflashed the USB drive with Armbian and built PiNodeXMR from the install script. Ran all the updates from the settings screen and everything appeared to be working. Was getting ready to start up the node, but unfortunately I’ve been unable to access the web-UI. Anyone have any ideas what the problem may be?