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

Spigot does not start, Exited too quickly (process log may have details). #55

Open
whyareallthegoodnamestaken opened this issue Jan 7, 2022 · 3 comments

Comments

@whyareallthegoodnamestaken

Hey

I am running:

  • Fedora Linux 35
  • Docker 20.10.11

Container created using:
docker run -e SPIGOT_VER=1.18 -e EULA=TRUE -d -p 25565:25565 -v /home/minecraft/spigot-server-1.18:/minecraft --name spigot-mc nimmis/spigot

Which builds fine but ends up throwing the following:

2022-01-07T17:33:03.084380545Z *** open logfile
2022-01-07T17:33:03.084612188Z *** Run files in /etc/my_runonce/
2022-01-07T17:33:03.084897275Z *** Run files in /etc/my_runalways/
2022-01-07T17:33:03.085343613Z *** Running /etc/my_runalways/00_minecraft_owner...
2022-01-07T17:33:05.092976502Z *** Running /etc/my_runalways/10_set_mc_version...
2022-01-07T17:33:07.099947032Z *** Running /etc/my_runalways/50_do_build_spigot...
2022-01-07T17:33:07.106328442Z checking 1.18
2022-01-07T17:33:07.108096634Z Setting version to 1.18
2022-01-07T17:33:07.112329769Z Current running version is 1.18
2022-01-07T17:33:07.112357581Z Alredy running 1.18, aborting update
2022-01-07T17:33:07.114592697Z set java version to 17
2022-01-07T17:33:09.110869424Z *** Running /etc/my_runalways/85_fix_startsh...
2022-01-07T17:33:11.120437742Z *** Running /etc/my_runalways/90_eula...
2022-01-07T17:33:13.128175172Z *** Booting supervisor daemon...
2022-01-07T17:33:13.128478043Z *** Supervisor started as PID 41
2022-01-07T17:33:18.332753897Z *** Started processes via Supervisor......
2022-01-07T17:33:18.332775544Z crond                            RUNNING   pid 43, uptime 0:00:04
2022-01-07T17:33:18.332778497Z spigot                           BACKOFF   Exited too quickly (process log may have details)
2022-01-07T17:33:18.332782697Z syslog-ng                        RUNNING   pid 45, uptime 0:00:04

I thought my issue was related to #25 since etc/init.d/minecraft_server still uses

getPID() {
  local PID
  PID=$( ps -f -u $MC_USER | grep "$MC_PROC" | grep -v "sh -c" |  grep -v grep | awk '{print $2}' )
  printf "%d\n" $PID
}

I changed grep "$MC_PROC" to grep "/usr/bin/java" but unfortunately this does not fix it for me.

Running the container doesn't create anything besides:

[root@oasis spigot-server-1.18]# ls -ltr
total 65972
lrwxrwxrwx. 1 root root       23 Jan  7 17:33 start.sh -> /usr/local/bin/mc_start
-rw-r--r--. 1 root root 67548672 Jan  7 18:09 spigot-1.18.jar
lrwxrwxrwx. 1 root 1000       26 Jan  7 18:19 spigot.jar -> /minecraft/spigot-1.18.jar
-rw-r--r--. 1 root root       10 Jan  7 18:19 eula.txt

Hope you can help me, thanks in advance.

@iapetos163
Copy link

I had the same issue. Turns out the EULA variable must be lowercase true, not TRUE.

The "process log" mentioned by the error is in the directory /var/log/supervisor in the container.

@ssshake
Copy link

ssshake commented Jul 14, 2022

I am having this issue trying to upgrade from 1.16.5 to anything 1.17.1 and above.

EULA=true for me.

I believe this could be a clue cp: cannot stat '/build-mc/Spigot/Spigot-Server/target/spigot-*.jar': No such file or directory , because every version that works does not throw this line, but version 1.17.1, 1.18.2 and latest do throw this line. All of them also show the Exited too quickly line.

@ssshake
Copy link

ssshake commented Jul 14, 2022

I found this closed issue which tipped me off that my docker image was outdated. #12

I did a docker pull nimmis/spigot and things were good.

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

3 participants