-
Notifications
You must be signed in to change notification settings - Fork 324
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
Bug: Bitbucket 5.15.0 error 500x on a few pages #349
Comments
That one should already be fixed by #345 Could you try the latest snapshot to see if it works for you? |
I did. First I used the install guide from Kibana. Then I got to github and tried the latest snapshot on the main page. I got the same error in both cases. |
Update: With the latest version available 1.2.0 I am not able to start bitbucket
|
Are you getting the same error like in the beginning? Did it work in the mean time? |
No it didn't work. The error is:
And in the logs:
I cannot find anything relevant that might help. I have also disabled the prometheus Exporter for this last test to ensure it is not interfering. |
Can you please check if any of the configuration options from the |
@eyalkoren sorry for the late response. I am also using the JRE and Springboot packaged by Atlassian Bitbucket. With that in mind I am a bit lost by your request. |
Yes, you can pass it this way and see what happens. If another problem arises, please try |
I have passed the argument as suggested. The error is exactly the same. Furthermore I have searched for the What has changed between version updates is that the Proxy in front of the APM server has been configured to work on HTTPS only, with HTTP returning a xkcd comic for the users that try to get there. But this setting has been tested and it's not the cause of the possible error as we have also reverted back to HTTP only and it still crashed. I do not believe the error is caused by Bitbucket and I would not comfortably change the system settings of the application when it is not recommended by Atlassian. The initial version which was bellow 1.0 has worked as intended, with the exception that the specific administration page mentioned didn't function (I do not have any evidence of the version number used at that date). I'll try again with the next version hopefully the agent will be more stable by then. |
OK, thanks for assisting with analysis. I added that to our backlog so hopefully we can schedule some more time to look into this, maybe reproduce. |
Received the same error and I have resolved it by adding the below line in "_start-webapp.sh" .
After adding the above line..
Please refer this link for more information. |
We do add |
Somewhat related: #436 |
Hey. When is this version going to release? Or how can I test it right now? We have upgraded the test instances of Bitbucket to 5.16.0 on which I noticed they have changed something internally on how they work with the Java Agents because now the Prometheus Exporter stopped working as well. I'll have to dig more into it but for now I want to focus on the Elastic APM agent to get it working. The issue described now might affect the APM agent as well. |
You can try a snapshot from master: https://github.com/elastic/apm-agent-java/blob/master/README.md#snapshots Let me know how it goes :) |
I have great news! When can we expect a stable release of this version? |
Describe the bug
Http Error 500 when accessing Bitbucket User Directories.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Get the User Directories page without any error
Debug logs
Attach your debug logs.
See the documentation
about how to enable debug logging.
Click to expand
The first error repeats itself around 15times.
The text was updated successfully, but these errors were encountered: