Has anyone seen this? Bitbucket UI comes up and I can click around for hours. Git fetch is also fine. But the moment I “git push” anything against the built-in “rep_1” repository, Bitbucket immediately shuts down.
There is nothing interesting in the logs and nothing interesting in dmesg. I even ran with all logging set to DEBUG - still nothing.
I’m on Ubuntu 18.04. 24GB of ram on my laptop. No OOM-killer in sight! Disk is 83% used up (37GB available).
ls -alh /usr/bin/atlas-run
lrwxrwxrwx 1 500 500 51 Dec 19 2017 /usr/bin/atlas-run -> /usr/share/atlassian-plugin-sdk-6.3.6/bin/atlas-run
This is happening against versions of “Control Freak” and “Commit Graph” that we know to be fine, and with every version of Bitbucket I’ve tried so far (4.13.0, 5.0.2, 5.5.1, and 6.0.0). I don’t think it’s related to our apps at all.
Normally I’m pretty handy around Bitbucket - for example I just pushed out our newest version of “Commit Graph for Bitbucket Server” (1150 install-count), and I’m proud to say we made a single version of our app that’s compatible from Bitbucket 4.0.0 to 6.0.0. Unfortunately I had to develop against a standard installation of Bitbucket instead of atlas-run to work around this problem.
But this “git push” issue causing an immediate shutdown in atlas-run has me completely stumped!
Here’s what the stdout console looks like in atlas-run when it happens (4.13.0 in this example):
[INFO] [talledLocalContainer] 2019-02-17 22:58:15,306 INFO [Caesium-1-2] c.a.b.s.i.i.jobs.StartupChecksJob Running startup jobs for search
[INFO] bitbucket: Shutting down
[INFO] using codehaus cargo v1.4.7
[INFO] [talledLocalContainer] Tomcat 8.x is stopping…
[INFO] [talledLocalContainer] Feb 17, 2019 10:59:56 PM org.apache.catalina.startup.ClassLoaderFactory validateFile