What I saw was that when I stopped the `rvice` either as a limited or sudo user and then restart the service as a limited or sudo user, the service failed to start. For the sake of transparency, I’m not a Minecraft player, and I’m not intimately familiar with the inner workings of Minecraft. One last reboot, and everything returned to normal, including the ability for the limited user to stop/start rvice.ĭescription I attempted to recreate your issue by deploying a minecraft server following the same steps that you indicated and then edited the `~/minecraft/server.properties` file as you did. bak version was also recognized during startup. This caused the server to fail to start and changing the ownership of server.properties alone didn't fix this as the. Mar 22 20:17:50 143-42-138-85.ip. bash: Information! The current user ($user) does not have ownership of the following files: I got confirmation of the issue by viewing systemctl status rvice which gave the following output: Mar 22 20:17:48 143-42-138-85.ip. systemd: Starting mcserver. $user should be your limited user’s name in this example. I changed ownership of the file (while logged in as root) using: sudo chown $user:$user server.properties It sounds like you tried to do this as well, but quite honestly, I ran into some of the same unexpected issues that you did. When changing the server.properties file, it’s really important to check the ownership of the file after and make sure they are both owned by the same user/group as the limited user created for the instance. In an attempt to recreate the issue further I next copied the ~/serverfiles/server.properties file to ~/serverfiles/, deleted the server.properties, and then copied back to the original name with: cp server.properties which caused both files to now have root:root user/group ownership. I suspected that there are other services/dependencies tied to rvice that must be run as the root user that aren’t being seen here or require a reboot for one reason or another. What I saw was that when I stopped the rvice either as a limited or sudo user and then restart the service as a limited or sudo user, the service failed to start. I attempted to recreate your issue by deploying a minecraft server following the same steps that you indicated and then edited the ~/minecraft/server.properties file as you did.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |