In Part 1<\/a> we turned our monero daemon into a service. <\/p>\n\n\n\n Here in Part 2 we will go over how to troubleshoot a service that is not starting.<\/p>\n\n\n\n Finally in Part 3<\/a> we’ll go deeper in security matters, such as using Monero with SELinux and firewalling your service.<\/p>\n\n\n\n Anticipating all of the potential problems would be an impossible task. Instead I will give you some basic ideas about how <\/em>to troubleshoot your new Monero service.<\/p>\n\n\n\n The first step is to determine whether it’s First let’s confirm it’s NOT an SELinux problem. This common enough that it may be worth doing first since there’s a quick workaround that will enable us to go in with checking our service is working.<\/p>\n\n\n\n Is SELinux currently enforcing?<\/p>\n\n\n\n If you see anything other than Warning<\/strong><\/p><\/div> Turn off SELinux at your own risk! Doing so won’t harm the functionality on your system, but it may make your system vulnerable to attacks while it is turned off. If your system is behind a home router or firewall, it’s probably not a big risk. Be more careful with internet-facing systems.<\/p><\/div><\/div>\n\n\n\n Now restart the service and see if we’ve fixed the problem, or uncovered a new one.<\/p>\n\n\n\n The problem with the I can’t predict what you’re going to see, but if it’s not immediately obvious where the problem lies, try checking these gotchas:<\/p>\n\n\n Like for A common gotcha might be passing invalid options to If you need more detail you can also up the Troubleshooting<\/h2>\n\n\n\n
Isolating the Problem<\/h3>\n\n\n\n
systemd<\/code>, monerod<\/code> or some other part of the system that is complaining and preventing start up.<\/p>\n\n\n\nEliminating SELinux<\/h4>\n\n\n\n
> getenforce\nEnforcing<\/pre><\/div>\n\n\n\n
Enforcing<\/code> then SELinux is not the problem and we can move on. If you do see Enforcing<\/code> we need to look at the journal to see exactly why it’s causing the service startup to fail. But we’ll do that in Part 3 – Security<\/a>. For now, let’s just turn SELinux to Permissive<\/code> mode:<\/p>\n\n\n\n> setenforce 0\n> getenforce\nPermissive<\/pre><\/div>\n\n\n\n
systemctl restart monerod\nsystemctl status monerod<\/pre><\/div>\n\n\n\n
Eliminating Systemd<\/h4>\n\n\n\n
status<\/code> command is it only displays the the last 10 or so logs and problem may appear a bit further back in the logs. So let’s switch to our monitoring terminal and turn to journalctl<\/code>:<\/p>\n\n\n\njournalctl -t systemd -e<\/pre><\/div>\n\n\n\n
\n
data-dir<\/code>)<\/li>\nEliminating Monero<\/h4>\n\n\n\n
systemd<\/code>, there’s a whole range of reasons that monerod<\/code> could fail to start. But hopefully the journals are informative.<\/p>\n\n\n\njournalctl -t monerod -e<\/pre><\/div>\n\n\n\n
monerod<\/code> via the configuration file we created. The Monero Project often changes these, so check that one or more of these hasn’t changed in the current version against the help:<\/p>\n\n\n\n\/opt\/crypto\/monero\/monerod --help<\/pre><\/div>\n\n\n\n
log-level<\/code> to 1 or even 2 in the monerod<\/code>.conf and restart.<\/p>\n\n\n\n