On each first boot, the code to generate server.properties seems to hang. After Ctrl-C of ansible, either local or remote, I find that there are commands to echo stop to the socket hanging and minecraft itself is running, apparently directly from ansible rather than from systemctl. I gather that therefore the named pipe is not running, and therefore minecraft will not exit.
I am able to use the role to achieve infrastructure as code, but not fully automate. Since the server is for my kids, this is adequate.
[vagrant@localhost ~]$ ps -ef | grep java
minecra+ 20326 20325 0 16:28 ? 00:00:00 /bin/sh -c echo "/stop" | java -jar minecraft_server.jar nogui
minecra+ 20328 20326 99 16:28 ? 00:05:55 java -jar minecraft_server.jar nogui
On each first boot, the code to generate
server.propertiesseems to hang. After Ctrl-C of ansible, either local or remote, I find that there are commands to echo stop to the socket hanging and minecraft itself is running, apparently directly from ansible rather than from systemctl. I gather that therefore the named pipe is not running, and therefore minecraft will not exit.I am able to use the role to achieve infrastructure as code, but not fully automate. Since the server is for my kids, this is adequate.