Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autoupdate failed #32

Closed
flplv opened this issue Aug 11, 2020 · 2 comments
Closed

Autoupdate failed #32

flplv opened this issue Aug 11, 2020 · 2 comments

Comments

@flplv
Copy link

flplv commented Aug 11, 2020

I think it did not wait for the 10seconds shutdown of the server? Exit code was not clear.

Aug 11 19:16:05 instance-2 sudo[113858]: pam_unix(sudo:session): session closed for user root
Aug 11 19:16:05 instance-2 systemd[1]: mcbe-autoupdate@MCBE.service: Found left-over process 113843 (bash) in control group while starting unit. Ignoring.
Aug 11 19:16:05 instance-2 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Aug 11 19:16:05 instance-2 systemd[1]: mcbe-autoupdate@MCBE.service: Found left-over process 114794 (sudo) in control group while starting unit. Ignoring.
Aug 11 19:16:05 instance-2 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Aug 11 19:16:05 instance-2 systemd[1]: Starting Automatically update Minecraft Bedrock Edition server @ MCBE...
Aug 11 19:16:05 instance-2 systemd[1]: Starting Automatically remove Minecraft Bedrock Edition server world backups more than 2-weeks-old @ MCBE...
Aug 11 19:16:05 instance-2 sudo[114794]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl stop mcbe@MCBE
Aug 11 19:16:05 instance-2 sudo[114794]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 11 19:16:05 instance-2 systemd[1]: Stopping Minecraft Bedrock Edition server @ MCBE...
Aug 11 19:16:05 instance-2 bash[74243]: Changes to the level are resumed.
Aug 11 19:16:05 instance-2 MCBEautoUpdate.sh[114795]: Service mcbe@MCBE not active
Aug 11 19:16:05 instance-2 systemd[1]: mcbe-autoupdate@MCBE.service: Main process exited, code=exited, status=1/FAILURE
Aug 11 19:16:05 instance-2 systemd[1]: mcbe-autoupdate@MCBE.service: Failed with result 'exit-code'.
Aug 11 19:16:05 instance-2 systemd[1]: Failed to start Automatically update Minecraft Bedrock Edition server @ MCBE.
Aug 11 19:16:05 instance-2 MCstop.sh[114817]: Server stopping in 10 seconds
Aug 11 19:16:05 instance-2 systemd[1]: mcbe-rmbackup@MCBE.service: Succeeded.
Aug 11 19:16:05 instance-2 systemd[1]: Finished Automatically remove Minecraft Bedrock Edition server world backups more than 2-weeks-old @ MCBE.
Aug 11 19:16:12 instance-2 MCstop.sh[114817]: Server stopping in 3 seconds
Aug 11 19:16:13 instance-2 MCstop.sh[114817]: Server stopping in 2 seconds
Aug 11 19:16:14 instance-2 MCstop.sh[114817]: Server stopping in 1 seconds
Aug 11 19:16:15 instance-2 bash[74243]: [2020-08-11 19:16:15 INFO] Server stop requested.
Aug 11 19:16:15 instance-2 bash[74243]: [2020-08-11 19:16:15 INFO] Stopping server...

[1]   Exit 1                  sudo systemctl restart mcbe-autoupdate@MCBE
Job for mcbe-autoupdate@MCBE.service failed because the control process exited with error code.
See "systemctl status mcbe-autoupdate@MCBE.service" and "journalctl -xe" for details.
@flplv
Copy link
Author

flplv commented Aug 11, 2020

Nevermind, I think I run the command when it was already running in the background. I will test better next time.

@flplv flplv closed this as completed Aug 11, 2020
@TapeWerm
Copy link
Owner

Aug 11 19:16:05 instance-2 MCBEautoUpdate.sh[114795]: Service mcbe@MCBE not active

That is an error message MCBEautoUpdate gives. I'm not sure how the service mcbe-autoupdate@MCBE started a 2nd time while the service is already running. The only way I know is if you ran the script before systemd like you said you think you did.

I just want to make sure because older versions of MCscripts had some bugs where MCstop would fail to stop the server, which makes MCBEautoUpdate fail. I'm pretty sure I fixed it, I just looked at the code again and it worked on my system this morning. Update MCscripts if you aren't on the latest commit.

And since MCBEautoUpdate failed, you may get this error message from MCBEautoUpdate next time: Previous update failed, rm "$server_dir/version" and try again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants