While testing we crashed the server, the buildspec seems defect:
[+] Running 1/1
✔ Container onedev Created 0.1s
Attaching to onedev
onedev | INFO - Launching application from '/app'...
onedev | INFO - Starting server...
onedev | INFO - Successfully checked /onedev
onedev | INFO - Stopping server...
onedev | 22:29:48 INFO i.onedev.commons.bootstrap.Bootstrap - Launching application from '/onedev'...
onedev | 22:29:48 INFO i.onedev.commons.bootstrap.Bootstrap - Cleaning temp directory...
onedev | 22:29:49 INFO io.onedev.commons.loader.AppLoader - Starting server...
onedev | 22:30:10 INFO i.o.s.e.impl.DefaultIssueManager - Caching issue info...
onedev | 22:30:11 INFO i.o.s.e.i.DefaultBuildMetricManager - Caching build metric info...
onedev | 22:30:12 INFO i.o.s.e.impl.DefaultBuildManager - Caching build info...
onedev | 22:30:12 INFO i.o.s.e.impl.DefaultProjectManager - Checking projects...
onedev | 22:30:16 INFO i.o.s.e.i.DefaultBuildParamManager - Caching build param info...
onedev | 22:30:16 INFO i.o.s.e.i.DefaultAgentAttributeManager - Caching agent attribute info...
onedev | 22:30:24 INFO io.onedev.server.OneDev - Server is ready at http://localhost:6610.
onedev | 22:30:29 INFO io.onedev.agent.DockerExecutorUtils - Finding host path mounted to '/onedev'...
onedev | 22:30:29 INFO io.onedev.agent.DockerExecutorUtils - Found host path: /onedev/data
onedev | /root/bin/entrypoint.sh: line 31: 42 Killed java -cp "../boot/*" ${MEM_OPTIONS} ${MOD_OPTIONS} io.onedev.commons.bootstrap.Bootstrap
Is there any option to deactivate building globally to fix the buildspec after starting onedev or to fix the git-code before starting the server again?
Best Regards
Kai
Robin Shen commented 12 months ago
Can you please describe in detail the steps to reproduce this issue? Including example build spec and repo if necessary.
Kai commented 12 months ago
Unfortunately i do not have the buildspec atm, need to get the server up & running again, then you can analyse the buildspec-issue itself.
Johann Wessely commented 12 months ago
I am working with Kai. I could not reproduce the error with the broken buildspec file on another onedev instance, but at the moment I can't say anything for sure. On our main instance more server crashes followed without starting a build process. When my friend Kai is back, we will do more tests.
Robin Shen commented 12 months ago
Never experienced server crash like this before. Obviously OneDev process is killed by some other process for some reason. Let me know if there is more clue.
jbauer commented 12 months ago
Maybe it has been oom-killed by linux? If you configure some resource limits via cgroups (e.g. via Docker resource limits) the kernel will simply kill the process if it requires more memory. So ${MEM_OPTIONS} might contain some large value.
Robin Shenchanged state to 'Closed'11 months ago
Previous Value
Current Value
Open
Closed
Robin Shen commented 11 months ago
Unable to reproduce. Feel free to reopen if there is more clue.
While testing we crashed the server, the buildspec seems defect:
Is there any option to deactivate building globally to fix the buildspec after starting onedev or to fix the git-code before starting the server again?
Best Regards Kai